Back doing .Net... and I feel like a newbie

D

Denaes

Senior Contributor
Joined
Jun 10, 2003
Messages
956
At work I'm doing .Net. I'm in the begining stages of converting a legacy database product over to VB.Net 2005.

Aside from not really touching .Net for a few months, working in 2005 is really humbling. ADO.Net has really changed. I think it's for the better, it's so much easier than I remember it... though it's still different.

It's sort of frustrating all the bugs I get between Visual Studio 2005 (far and away mostly display corruptions) and SQL CTP 2005 (the damned thing won't install with the same options on any two computers!). But I have SQL CTP 2005 basically running on my machine enough to serve a database (no extra features) and VS2005 can do some of the basic SQL Server functions.

But with how soon 2005 is comming out it would have been silly to go forward with 2003 and then convert again. In fact I'm just hoping they don't change things I'm learning for the final release. I'd think that beta2 means that most of the functionality is there, just needing to fill out error handling and catching bugs and whatnot.
 
The beta 2 of Visual Studio was by far the most stable I'd seen - display problems plagued earlier versions. In fact, one of the earlier versions wouldn't even let me resize controls on a form without causing an Exception within Visual Studio. I had to tweak things manually.

I haven't played much with SQL Server - just downloaded/installed the September CTP at home. But your assumptions are likely right - with a release due out in November, there can't be that many changes.

If this is a big enough project, you can contact MS to get on their "early adopter" program. They have special perks for companies that use their technology early. There are restrictions, the biggest (last I heard) was that you had to "promise" to implement the solution within a year of the official release. So if your product is going to production before November 2006, you may be a candidate.

-ner
 
I know the feeling about going back and forth from .net to another. I do .NET program every so often on newer test programs. But the machines we currently have, uses a Visual Basic created by the manufacturer of the test machine. It is like using VB4 or 5. and actually it is more of a macro application. And every new product I have to make a new one the way the company set it up. And frustrating sometimes. So when I have free time, I am creating 1 program to do all the models we test. It will be a big program when I am done, but worth it.
 
Back
Top