Ten essential .NET Development Gadgets (9 & 10): Version Switching and Conversion Tools
Author: James Avery translation: lucentoff
Source: http://msdn.microsoft.com/msdnmag/issues/04/07/musthavetools/default.aspx declaration: The copyright belongs to the original author, reproduced please indicate the source!
Version switching and conversion tool
In this part, I will introduce two versions of switching and conversion tools, although it is simple, it is extremely useful. The first tool is ASP.NET VERSION SWITCHER, which can switch the ASP.NET version under the virtual directory run. The second tool is Visual Studio Converter, which can convert the project file between Visual Studio .NET 2002 and Visual Studio .NET 2003.
When IIS processing request, first check the extension of the requested file, then based on the Web site or virtual directory extension map, or will be delegated to the ISAPI extension process, or processed by yourself. This is the working principle of ASP.NET, and the extension map registers all ASP.NET extensions and guides them to ASPNET_ISAPI.dll. This will not have any problems, but if you install ASP.NET 1.NET 1.1, you will upgrade the extension map to the new version of ASPNET_ISAPI.dll, when the application is built on the ASP.NET 1.0 attempts to run in version 1.1, Will cause errors. To correct this problem, you can switch all extended mappings back to version 1.0 version of ASPNET_ISAPI.DLL, but manually switching 18 extension mappings are not an interesting thing. At this time, ASP.NET VERSION SWITCHER has used the land. It can switch the .NET Framework version used by any single ASP.NET application.
ASP.NET VERSION SWITCHER is shown in Figure 9. When using, simply select the application, then select the application where the application wants to use. Press the switch button, which will switch the application to the selected .NET Framework version using the ASPNET_REGIIS.exe command line tool to the selected .NET Framework version. This tool will be more useful when ASP.NET and .NET Framework are released.
Figure 9 ASP.NET VERSION SWITCHER
ASP.NET VERSION SWITCHER is written by Denis Bauer: http://www.denisbauer.com/nettools/aspnetversionswitcher.aspx.
Visual Studio .Net Project Converter (see Figure 10) Very similar to the ASP.NET Version Switcher, which is used to convert the version of the Visual Studio project file. Although .NET Framework version 1.0 and 1.1 are only small, but project files are converted from Visual Studio .NET 2002 to Visual Studio .NET 2003, they will not be returned. Although this may not be a problem in most cases (because there is no big change between .NET Framework version 1.0 and 1.1), sometimes you may need to convert the project back. This converter can convert any solution or project file from Visual Studio 7.1 (Visual Studio .NET 2003) to Visual Studio 7.0 (Visual Studio .NET 2002), if you need to convert it back. Figure 10 Visual Studio .NET Project Converter
Visual Studio .NET Project Converter is written by Dacris Software, download URL: http://www.codeproject.com/macro/vsconvert.asp.
Conclusion
The introduction of these tools to the horse will end, but I have tried enough to show enough information to inspire your interest. I believe this article allows you to understand some free tools that can start using it immediately to write better projects. I also promote you to ensure that you have other suitable tools, whether the latest version of Visual Studio, a powerful computer, or a free tool. With a suitable tool, everything will be different.
-------------------------------------------------- ------------------------------
[Author] James Avery, .NET and Microsoft Technical Consultants, published many books and published many articles, the latest books for "ASP.NET SETUP AND Configuration Pocket Reference" (Microsoft Press, 2003). E-mail: javery@infozerk.com, WebLog: http://www.dotavery.com/blog.
