Printable View
Can someone tell me how efficient is the .net2003 to .net2005 converter?
Is it giving any errors for your programs? I tried converting a vb.net program and i had no errors,but I did get errors for an asp.net program....and I was unable to solve it and ultimately i took .net2005 off my comp.But,now,I am again thinking of installing it...but,please tell me if any of you got any errors and how you solved it...Thanks..:)
Well bear in mind the .NET 2.0 Framework is still a Beta Framework. I personally don't like using conversion tools like that, because they're simply converting the code line by line or just as required. They're not providing you with the new features available to you in the new Framework.
yes,but,still,you can use the new features once your old program becomes usable with the new .net ;) or even if thats not the thing,you still get to know the difference in programming in the new .net
I'm interested in this one also. There are features in 2005 that make it look like a good move to me, but I have a fair amount of code in 2003 at this point. I suspect that any information on how this conversion works will be of pretty general interest.
Did your project fail to compile? Were they compilation errors or just warnings about deprecation and the like?
I have made 3 projects and there were no errors in 2 of them.But,on the asp project made with vb,i had errors.But,in every conversion,it showed a lot of warnings :)
Well,but,i would just like to know what kind of errors other people get too.so,please share your .net2005 errors with me if possible :) Thanks :D
A colleague of mine had a datagrid with the 'visual' dataset, dataadapter and connection objects (You know, that silly old drag-drop method). The datagrid was bound to the strongly typed dataset's Customer table.
After conversion, she showed me what happened to the code.
One thing I found funniest, the dataset was declared like this:
Dim DataSet11 as New DataSet1
:ehh:
lol :)