Vs. NET is ready for the enterprise?

LT: What changes in the development environment will have the greatest impact on enterprise developers? MD: Integrating the Lifecycle development tools of Vs.net and ISVs (independent software developers) will make it easier to handle large-scale projects. Visual Studio. NET has been redesigned from the ground up, in a completely new framework that makes it easier to integrate vs.net and ISVs lifecycle development tools such as project management, modeling, versioning, testing, and more. Now, they use all the features like a separate tool. With Vs.net, developers don't have to think, "I'm calling this individual tool." "They will just use another feature of their IDE." How did Lt:microsoft do that? MD: They provide a common framework for ISVs to use-a complete set of technical APIs and Visual Studio integration programs that provide technical assistance, easy access, and market support. Microsoft has always done a good job of facilitating ISVs when it comes to developing a new platform, and it has gained a lot of experience on this road, and it has already applied these experiences to the development area explicitly. Microsoft is certainly more likely to collaborate than most other vendors. Similarly, Microsoft has been able to tightly integrate the development environment with the underlying framework. And because of the common platform, the cost of developing new functionality in this environment for ISVs is lower. As a result, developers can not only gain the current functionality of the platform, but also benefit from the providers that are developed on the framework. LT: It all sounds good, there will be a learning curve. You will bring their teams into the. NET era of IT managers what kind of advice? MD: This technique is great-no doubt about it. So, in fact, more human factors. If not used. NET, training will have a short half-life, a success will bring more success. So you need to learn it in a way that includes it. Put your best people into a real project that is important to your business. Choose one you can use quickly. NET project. A project may be an application or a set of components. While you're doing this, consider the overall architecture of your area. The transaction and the on the architecture. NET has nothing to do with it, but if you don't have an architecture, you want to make the most of it. NET's advantages are difficult. I think some organizations will need to deal with this problem better. LT: Sounds like a developer plan. What about the ready-made code? MD: There are many things that can be postponed, including lifecycle processes, such as configuration management and change management. As far as the current application is concerned, if you are already developing a business model, you have a starting point. Because no matter what you will not transplant, your model will provide the basis.Although there are no silver bullets, I will select about 10 key services and package them as Web services.