Shulou(Shulou.com)06/02 Report--

This article shares with you what are the key points for upgrading Visual Studio 2010 and .net 4. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

With the upcoming release of Visual Studio 2010 and .net Framework 4, enterprises using Microsoft software should evaluate when it is most appropriate to make the transition. 'i recently had a discussion with my new employees to plan our product development strategy for the rest of 2010, 'said Martin Heller, a strategic developer at Microsoft.

This discussion raises a question we face with every independent software distributor using Microsoft Visual Studio: when to internally switch to Visual Studio 2010, when to internally switch to .net Framework 4, and when to release new versions of products made using these new technologies.

One of our developers has been tracking Visual Studio 2010 beta and release candidates, and has successfully compiled and connected the C++ module at one time. His brief summary was: when we upgraded from Visual C++ 6 to Visual Studio 2005, most of the hard work was done. When we upgraded to Visual Studio 2008, we did some difficult work. Although we still have to make some code adjustments for Visual Studio 2010, the work is not difficult: it's just boring. At the same time, the code is generated faster, albeit a little larger than the products we ship.

As for the internal conversion to Visual Studio 2010, as long as the entire product is made in Visual Studio 2010, we will separate our resource tree for new development. As for external transformations, we will continue to ship existing products that have been compiled using the same method that has been used over the past year. We only use Visual Studio 2010 in the next generation of products.

The developer added that we have a complex product that needs to be tested before shipment. If we use Visual Studio 2010 internally to make a new version of the product, we will find most of the compilation-related flaws when we prepare for beta testing. However, to launch a stable product with the new compiler is just looking for trouble.

How about transitioning to .Net Framework 4? What we are most interested in .net Framework 4 is the dynamic language runtime, because we have a dynamic language (Xbasic) as part of this product. We are already moving some of our features to .net Framework, which will expand our capabilities and reduce the size of our own code base. Again, we will apply it internally soon after it is launched. However, our current product will not adopt it: we need time to try our .NET code internally as we develop it.

Thank you for reading! This is the end of this article on "what are the key points to upgrade Visual Studio 2010 and .net 4". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.