Converting a project from 2003 to 2005 differences

[NickP]

Hi there,

I have converted quite a large project from VS.NET 2003 to 2005 (VB.NET)
and one difference I have noticed is that it doesnt automatically put the
automatically generated designer code into a seperate part file.

Is there a quick way that I can scan the project and make these changes?
Will VS.NET automatically then use the correct part file to store the
designer code? I could really do with seperating some code out and getting
that chunk out of the way would really help!

Cheers in advance.

Nick.

 

[Marina Levit [MVP]]

I think the conversion just leaves the designer code where it is. And it
continues to work with that. As far as I know, you would have to manually
make the changes to create the designer file, partial class, etc. Maybe
someone out there wrote a utility to do this, but I'm guessing you would
have to do this by hand if you want it to look just like VS 2005 created the
file.

 

[Cor Ligthert [MVP]]

Nick,

I did this for some, however don't do it nomore. The VB2003 code works very
good as it is converted.

Because it looks not the same as VB2005, I can when I know more about 2005
refactor them easily and don't have to remember which where original 2003.

Just my thought,

Cor

 

[NickP]

Hi Marina,

I think the conversion just leaves the designer code where it is. And it
continues to work with that. As far as I know, you would have to manually
make the changes to create the designer file, partial class, etc. Maybe
someone out there wrote a utility to do this, but I'm guessing you would
have to do this by hand if you want it to look just like VS 2005 created
the file.

Okie dokie, that answers my questions perfectly. It's a shame it
doesn't shift it into a partial class for you. I just feel it will help
remove the bulk from a few forms by quite a considerable ammount of code,
which would be very handy indeed. Anyway, I'll have to have a look at
making a little app to do it.

Cheers for your help.

Nick.

 

[NickP]

Hi Cor,

I did this for some, however don't do it nomore. The VB2003 code works
very good as it is converted.

Did you get any strange exceptions from doing so? I have found that the
designer code can be very stressy if you make a slight error in it and it
can even start destroying itself. I thought I best not try this incase
there was a reason not to.

Because it looks not the same as VB2005, I can when I know more about 2005
refactor them easily and don't have to remember which where original 2003.

That makes sense I suppose, at least you know which modules were
designed in 2003/2005. I've got allot to work through if I do seperate the
designer code in the entire solution, so maybe a tool would be the best
idea.

Cheers for your help and advice Cor.

Nick.