|
About the Author
Anand Narayanaswamy, a Microsoft Most Valuable Professional (MVP) in Visual C# works as an independent consultant based in Trivandrum, India. Anand runs learnxpress.com and dotnetalbum.com. He specializes in ASP, ASP.NET, C#, Visual Basic .NET and Visual Basic 6.0 and in the development of courseware, technical articles, documentation, and reviews of products and books. He is available for writing documentations, help files, product reviews and for other development related projects. Reach him at ananddotnet@yahoo.co.in
|
Microsoft has released the alpha version of Visual Studio “Whidbey” in October 2003 at the PDC. Even though there will be feature changes in the upcoming betas, many developers have installed the development environment. At present, Whidbey is available only for alpha testers, PDC attendees and MSDN Universal Subscribers.
I have observed while testing that some of the features have not yet implemented by Microsoft in the alpha release. In this article, I will explain some of the issues which I faced after the installation of Visual Studio “Whidbey”.
Issue – 1
If you have installed Whidbey along with Visual Studio .NET 2003, you are likely to face certain problems after the installation. All your existing ASP.NET projects will target Whidbey (ASP.NET V2) after its installation. Hence, you will not be able to execute your ASP.NET V1.1 projects as usual. In order to resolve this problem, you have to do some workarounds (See the steps given below) using Internet Information Server (IIS).
1. Right Click your project folder on the IIS
2. Click the Configuration button on the bottom of the properties dialog.
3. Select the extension .aspx and click the Edit button to open the Add/Edit Application Mapping Extension dialog box.
If you observe the version number inside the Executable Textbox it will be v1.2.30703. This is the version number for ASP.NET 2.0. You have to modify the version number to reflect .NET 1.1, which is v1.1.4322. The complete path details are given below for your reference:
ASP.NET 1.1
<Your Drive Letter>:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
ASP.NET 2.0
<Your Drive Letter> F:\WINDOWS\Microsoft.NET\Framework\ v1.2.30703\aspnet_isapi.dll
You have to perform the above mentioned steps for all your existing ASP.NET projects.
Issue – 2
You will experience some difficulty to work with FrontPage 2003. The error message which I got was “Cannot find entry point “?QueryNewMode@@... IN d:\Program~1/common~1/Micros~1/webserv~1/60/bin/fpsrvvf1.dll.
If you get this error message then go to the specified folder and delete all the DLL files. FrontPage will open as usual after a series of progress bars. Sometimes, you may have to perform Detect and Repair from the Help menu.
Issue – 3
If you are unable to design ASP.NET pages using FrontPage 2003 after the installation of Visual Studio “Whidbey”, Go to Tools | Options and select the ASP.NET tab. On the first text box enter the following path depending upon the version of ASP.NET you would like to use:
ASP.NET 1.1
<Drive Letter>:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
ASP.NET 2.0
<Drive Letter>:\WINDOWS\Microsoft.NET\Framework\ v1.2.30703
Microsoft didn’t implement certain features in the alpha release of Whidbey. To see them in action open your web project and select Website | Publish menu item. You will a message box with the appropriate message. Note that Microsoft will provide implementation to this functionality in the beta release around 2004 spring.
Conclusion
In this article, you have learned how to resolve some of the problems which will possibly occur after the installation of Visual Studio "Whidbey". In the next article, I will teach you how to work with Whidbey along with some cool working demos. |
