.NET Stand-alone exe's and deployment

[esposito]

But with .NET its more of a RAD development studio then VB 6 ever was. One property setting to make a form "always on top" in .NET vs. in VB 6 having to use an API call, define consts and make the call passing the forms handle to it too.

VB 6 knowledge is not useles as the only real difference in .NET is that if you didnt have any OOP knowledge in VB 6 you will need it now in .NET. Logic and being familiar with controls and databases etc is never useless as it can always be applied to any other programming language or IDE.

I was referring to the tons of VB6 code that every programmer (I bet) has stored in a personal database to be used with a simple copy-and-paste operation. That code must be re-written from scratch. (The migration tool provided by MS is a joke.)

[RobDog888]

I was referring to the tons of VB6 code that every programmer (I bet) has stored in a personal database to be used with a simple copy-and-paste operation. That code must be re-written from scratch. (The migration tool provided by MS is a joke.)

I missed this post.

Well some of your code library will be obsolete as the "always on top" scenerio I presented. No longer will you need a library entry for that as a single property will be even faster then looking it up in a code respoitory.

So I really dont see a need for probably 50% of code libraries as a guestimate.

[esposito]

I missed this post.

Well some of your code library will be obsolete as the "always on top" scenerio I presented. No longer will you need a library entry for that as a single property will be even faster then looking it up in a code respoitory.

So I really dont see a need for probably 50% of code libraries as a guestimate.

I have installed the Express Edition of VB 2005 on my computer and played around with it. The IDE is just great, the tools you have at your disposal are so many that they make you feel strong. I would love to put VB6 on the shelf and develop my new commercial software in VB.NET. I would even be ready to bury my VB6 code repository. Unfortunately, I did a personal survey among my customers (a few hundred users) and I found that the majority of them did not have the Framework v.1.1 on their machines. So, I decided to put off the idea of embracing the .NET technology to a better future. In the meantime, I looked around and I found a free version of Borland Delphi the potential of which is definitely superior to VB6. Right now, I am developing my new software in Delphi, while keeping an eye on the evolution of .NET.