Click here to Skip to main content
15,879,474 members
Please Sign up or sign in to vote.
5.00/5 (2 votes)
See more:
I am having Windows application using remoting, developed in .NET 1.1. Now I want to upgrade the application to .NET 3.5. The way I supposed to do this is by converting the code of 1.1 to 3.5 using Visual Studio 2008 and then compile that code using VS 2008 and deploy the application on .NET 3.5 framework. The questions i am having related to this are:
1. Is there any benefit of conervting the .NET 1.1 application to .NET 3.5
2. Is there any benefit in performance of application
3. Is it going to benefit me, as Microsoft has stopped support for .NET 1.1
or any other benefits.

What are the issues going to face in this activity.

Please suggest.

Thanks & Regards,
Gaurav.
Posted

I don't know whether it is helpful to you or not have a look at this

http://blogs.msdn.com/b/swiss_dpe_team/archive/2008/04/10/migrating-from-net-1-1-to-2-0-3-0-and-3-5.aspx[^]
 
Share this answer
 
1. Is there any benefit of converting the .NET 1.1 application to .NET 3.5
Hopefully VisualStudio will do most of this conversion for you so it isn't that hard.
2. Is there any benefit in performance of application
You hope that your application will run faster? Likely not because it strongly depends on the application itself and how it depends on other elements like a database connection. When a lot of processing is done you could gain performance by using new available features that might help with that but it would be up to you to implement it.
3. Is it going to benefit me, as Microsoft has stopped support for .NET 1.1 or any other benefits.
A strong argument would be that it Enhances Security. Not only is .net 2.0 (and up) more secure but because it has support, new problems are fixed.

So in the long run it could be good to upgrade your .net version, also because it could get harder when new functionality is added. This would mean more conversion and maybe more work. You could also benefit from new features when adding new functionality. If it is a standalone application running for years without any trouble and no further future changes are expected, I would recommend to let it be for now.

Good luck!
 
Share this answer
 
Comments
Sergey Alexandrovich Kryukov 22-Apr-11 22:39pm    
Good points, my 5. Anything prior to 2.0 hardly worth any attention, but 2.0 is already a decent version.
--SA
.NET 1.1 is not officially supported any more. So it won't get updates or security patches. And a future OS may even be incompatible with it (as it had some legaxy API dependencies). The CLR has also considerably improved in efficiency and performance across the .NET versions. So potentially, you "may" see a speed improvement. You will also be able to take advantage of all the 100s of newer classes and features that have been added to .NET.

And as an aside, while many people continue to use remoting and insist it's better performing that WCF, remoting is "officially" obsolete. Microsoft recommends that you move up to and use WCF. So from the "official" Microsoft perspective, using remoting is kinda similar to using classic VB6 or Frontpage.
 
Share this answer
 
Comments
Sergey Alexandrovich Kryukov 22-Apr-11 22:38pm    
That's correct. I think 2.0 is a decent version though (and anything before never was). My 5.
--SA
Nish Nishant 23-Apr-11 9:17am    
Thank you.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900