Visual Studio 6 and Visual Studio .net 
Author Message
 Visual Studio 6 and Visual Studio .net

Are there any issues with running these two packages together on one
machine?

Thanks,

Matt



Mon, 06 Dec 2004 19:42:58 GMT  
 Visual Studio 6 and Visual Studio .net
sorry for squating but i would also like to get some second hand info
(vb.net intermediate code, performance issues, msdn - in fact a quick net
vs. 6 would be much appreciated)


Quote:
> Are there any issues with running these two packages together on one
> machine?

> Thanks,

> Matt



Mon, 06 Dec 2004 20:01:21 GMT  
 Visual Studio 6 and Visual Studio .net
Oi, get yer own thread :)


Mon, 06 Dec 2004 20:18:43 GMT  
 Visual Studio 6 and Visual Studio .net
jerry, jerry


Quote:
> Oi, get yer own thread :)



Mon, 06 Dec 2004 22:20:45 GMT  
 Visual Studio 6 and Visual Studio .net


Quote:
> Are there any issues with running these two packages together on one
> machine?

I've been running both on the same box for quite a while and I haven't had
any problems at all.  I would follow this install order:

1. VB6
2. SP5
3. VS.NET

The only thing that may cause you grief is deployment.  I believe that
VS.NET installs MDAC 2.7, so that would be something to watch out for (I'm
not a data geek so I don't really keep up on that stuff, though I'm starting
to have to use it more - yikes!).  You may want to have a clean
box/partition for creating install packages.  Other than that, I don't know
of any issues.

Tom Shelton



Tue, 07 Dec 2004 00:07:11 GMT  
 Visual Studio 6 and Visual Studio .net


Quote:
> sorry for squating but i would also like to get some second hand info
> (vb.net intermediate code, performance issues, msdn - in fact a quick net
> vs. 6 would be much appreciated)

Performance varies depending on what your discussing.  For example - GUI
performance is slower.  On a new box you probably won't notice to much of a
difference.  On my PII 233 with 128 MB of RAM, the difference was
noticeable, but acceptable.  On my AMD XP 1800+ - well except for a slightly
slower startup - you can't even tell the difference.  My PIII 500 is
somewhere in between.

If your talking about actual code performance here is what I tested - I
don't have any number's handy, so you might want to do your own benchmarks:

1. Object creation - much faster since there is no call to AddRef.  This is
only really noticeable though when creating large numbers of objects.

2. Integer math - this one varied, most of the time it was as fast or
faster.

3. Floating point operations - dog slow.  The VB.NET compiler emits some
pretty funky IL for FP.  If you have to do a lot of FP, your best bet is to
put in a C# class which doesn't have this problem and in fact, I believe is
as fast or slightly faster than VB6 in this area.

To be honest, on a fast box with lots of RAM VB.NET apps perform very well.
The biggest bottle neck with .NET apps in general is the JIT compiler.
Since every method is compiled to native code as they are called - it makes
your initial call slightly slower, but only the first time.  The difference
should narrow over time as 1. the VB.NET compiler is optimized to generate
more efficient IL and 2. the JIT'er is optimized to generate more efficient
native code.

The biggest factor in VB.NET performance is the amount of memory.  The more
the better.  That's because of the size of the runtime.  I have read, though
I haven't actually checked it out, that the memory footprint of a VB.NET
HelloWorld program is about 13/14 MB's.  I know that sounds bad, but it
isn't as bad as it sounds.  The reason is that once the runtime is loaded
(that's the majority of the 13/14 MB's)  most of that is shared with any
other .NET applications that are started.  This means that the memory usage
doesn't go up dramatically as you start more apps.  The overall total usage
only goes up by a small amount.  That's also why you can start a .NET app
and see a slight pause - close it and restart it and it will start almost
immediately.  Once the runtime is loaded, it is cached so warm startups are
much faster.

HTH,
Tom Shelton



Tue, 07 Dec 2004 00:30:15 GMT  
 Visual Studio 6 and Visual Studio .net


Quote:
>The biggest factor in VB.NET performance is the amount of memory.  The more
>the better.  That's because of the size of the runtime.  I have read, though
>I haven't actually checked it out, that the memory footprint of a VB.NET
>HelloWorld program is about 13/14 MB's.  I know that sounds bad, but it

Tom, you make me feel very, very old :-)

When I started programming (mumble) years ago on the PDP8 there were two
I/O instructions for printing. Teleprinter Load Sequence and Skip on
Teleprinter Busy so the program would have been about 20 (12-bit words)
long.

Anyone here remember .RAD50?

Regards.

--
Martin Trump



Tue, 07 Dec 2004 02:26:43 GMT  
 
 [ 7 post ] 

 Relevant Pages 

1. Visual Studio 6 and Visual Studio .NET

2. Visual Studio 6.0, Visual Studio.Net Difference

3. WinXP-Visual Studio 6.0-Studio.Net compatibility

4. WinXP-Visual Studio 6.0-Studio.Net compatibility

5. Visual Studio.NET vs Visual Basic.NET

6. Visual Studio .Net causing Visual Basic 6 problem?

7. VB.NET vs. Visual Studio.NET

8. Event Button in Visual studio net VB.net

9. i am using vb.net and crystal reports for visual studio.net

10. Visual Studio.Net

11. PowerToys for Visual Studio .NET 2003 Project Announcement

12. Visual Studio .NET 2003 and Crystal Report Deploy

 

 
Powered by phpBB® Forum Software