Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have about 5 big projects in 2.0 .NET framework. We are using VS 2008. We are decided to change our framework to 4.0 and upgrading to VS 2012. What are the possible problems in this situation? Which ways or steps should we follow? Any suggestions?
The only thing that can be suggested is: test it. The actual upgrade should be pretty simple. You may get a few warnings or errors where types or methods have been marked
[Obsolete], in which case it usually advises you on the type/method to look at for a replacement, however there can also be implementation changes that impact some (minority of) code. For example, sometimes a bug-fix can lead to your previously working code… not working (if you were inadvertently or deliberately using a behaviour that was not guaranteed).There is no magic wand here; you just need to test it, but it shouldn’t be too painful, especially if you have a test suite.
Also: if you’re doing an upgrade anyway, why not go to 4.5?