Porting to .NET

[Kymera]

Okay, in this thread, I needed help with a decent SLEEP method. Now, I just got my hands on .NET and have been asked to migrate my program over to an ASP environment. Anyway, I ran the automatic convert from VB6 to .NET, and I couldn't even understand my own code. The only thing it seemed to get right were my comments.

Well, I don't know why I'm posting this, because it really looks like I'll have to recode most of my project.

[kingtbone]

Thank god I will be done working with the system I'm doing when we switch over to .NET I don't want to deal with those headaches.

[Kymera]

You lucky dog. It's like a whole different animal, this .NET thing. Oh well. Time to buy some more books.

[MIDIMan]

That very prospect is exactly why a collegue and I got pissed and dropped our 'Journal subscriptions that were preaching the virtues of ".NET" before Microsoft even knew what to do with it.

As far as I'm concerned, Microsoft has handed everybody yet another less efficient solution to a more general set of problems- namely, web.

VB is maturing, and there will be many sacrifices on the way. The first appears to be my favorite aspect of VB- instant protoyping gratification.

Now they might as well call it VB# (sharp).

P.S. -> I still don't know anyone who thoroughly understands the MSDN documentation engine. Can I have my goddamn simple Windows help back for those times when I don't have 4 or 5 hours to get the answer?