Just got VB.net

Hi,

I just got VB.net. The bulk of my programming experience is in VB 6 and geeze .net is a load different. Anyway my question. For some reason .Net seems to be running and compiling programs incredibly slow on my few tests playing around with it getting use to the interface.

It took it about 10 times as long as VB6 to compile and debug a form with a textbox and a command button to put something in the textbox when clicked =P.

Is this normal for VB.net or do I need to change a setting somewhere?

Oh btw I'm runnin on a 1.7 Ghz machine with 768 MB Ram so I normally dont see this type of sluggishness.

Thanks

I'm runing on a 1.6 Ghz with 256MB and haven't noticed any sluggishness...

I have noticed this as well. (800 mhz x 256 MB) Another developer also noticed this in asp.net. However, once it gets started, it runs rather quickly.

From what little I understand about the new compilation process I think it compiles to a common level and then the framework component at the OS level also has to do something to make it work on that OS.

I tend to find the first compile/execution the slowest. It seems like it's loading a lot of backend stuff. Same with the ASP.net though once everything is loaded it seems to run better. And of course, more memory isn't going to hurt.

I got that problem too, it's ok that VB does compile slower... But when I'm editing code, it also goes very slow sometimes.
You type a part of an expression and then you will notice some kinda hang while you type. Afterwards it continues normally.
This happens only in VB.NET
I don't experience that problem in other parts of Visual Studio .NET. I tested it in C#, J# and C++.... not a single problem there of this kind.

I use P3 800 mhz, 256 MB ram... and run Win2k SP3

BTW My programs run perfectly fast !

Will Visual Studio .NET over write 6.0 or can they run concurrently :confused:

You can have both on the same computer, it wont do any harm.

How easy is it to migrate a project done in VB6.0 to VB.Net. Is there backward compatibility or the code has to be redone or converted somehow and with how much ease :(

I've two problems.

When both programs run, one crashs!
And the help only runs on vb.net! :mad:

Leominora - I use both everyday without problems. Have you applied both service paks for .NET and SP5 or VB 6?


Platinum Plus - If you open a VB6 applicaton in the .NET IDE a migration wizard comes up and converts the application to .NET automatically. There are however some things that simply won't convert due to changes. These are marked for you by the wizard and show up in the "ToDo List" window.

My experience has been however it's best to leave VB 6 applications alone and start fresh with .NET stuff simply because of the imcompatiblities and because the .NET "way" is different for a lot of things. Some things that were "easy" in 6 are "hard" in .NET and the opposite is also true. If you know/understand OOP principles, the biggest part of the learning curve is simply where the **** is this function/method or that function/method within the class hierarchies and also getting used to the changes (ie. Labels no longer have Captions, you use the Text property instead, etc.... nice for "consistency" between controls, but takes getting used to, especially when working with both langauges at the same time).

I think VB has some pretty good things in it now.
Within functions for example you simply say: Return x
To return the current value of the function.

Also the classes have improved big time. I agree with DSJ that the biggest part of the learning procedure in VB is the function names. I am still working on that.
For example file I/O has changed a lot. I still can't get the hang of it. But XML is something to consider when you are planning to use file I/O.

Quote:

---

Originally posted by DSJ If you open a VB6 applicaton in the .NET IDE a migration wizard comes up and converts the application to .NET automatically.

---

Is this true for all EXE's, Dll's, OCX's or it applies to EXE's only ?

It's true for all although there isn't such a thing as activeX EXE in .NET., but it will convert the code.

Quote:

---

Originally posted by DSJ I use both everyday without problems.

---

For interests sake, why are you running both 6.0 and .Net and not moving over completely to .Net ?

LOL

Since he has an upgrade?
I also upgraded, but I found out that you don't need VS 6.0 to be installed on your pc to install the upgrade. But you need to have a copy of VS 6.0 at your place :)

First of all, we have a lot of VB 6 stuff to maintain. Secondly, the conversion process isn't what I'd call clean, so we're pretty much maintaining what we have in 6 there until it can be re-written in .NET (not simply converted by a wizard). Also .NET is a version 1 product. Still needs some work, but it's never to early to start learning.