Doug Seven's Blog

What is Whidbey?

What is Whidbey (besides an island in the Pacific Northwest)?

“Whidbey“ is the codename for the next release of Visual Studio .NET scheduled to release in 2004. This release of Visual Studio and the .NET Framework will offer innovations and enhancements to the class libraries, common language runtime (CLR), programming languages, and the integrated development environment (IDE). In addition, this product will provide deep support for the next version of SQL Server (code name "Yukon") by enabling developers to write stored procedures using Visual Basic and C#.

You can read a little about it from Chris Maunder at Code Project - Visual Studio 'Whidbey' and VSIP - the VSLive keynote in New York.

You can also read the Microsoft Developer Toools Roadmap 2003-2005.

PRB: "Access denied" Error Message When You Run an ASP.NET 1.0 Application in IIS 6.0

Full Knowledge Base (KB) Article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q817033

The information in this article applies to:

• Microsoft ASP.NET (included with the .NET Framework) 1.0, when used with:
  the operating system: Microsoft Windows Server 2003
  Microsoft Internet Information Services version 6.0

SYMPTOMS
When you run an ASP.NET Web Application project on a computer running Windows Server 2003 with the .NET Framework 1.0 installed, and the Internet Information Services (IIS) 6.0 is running in IIS 5.0 isolation mode, you may receive the following error message if you do not grant the seImpersonatePrivilege function to the ASPNET account:

System.Web.HttpException: Access denied to 'd:\inetpub\wwwroot\ImpersonateTest\WebForm1.aspx'. Failed to start monitoring file changes.

RESOLUTION
To resolve this problem, grant the seImpersonatePrivilege to your ASPNET account. To do so, follow these steps:

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Administrative Tools.
3. Double-click Local Security Policy. Under Local Policies, click User Rights Assignment.
4. In the details pane, double-click Impersonate a client after authentication.
5. Click Add, and then assign the permission to the local account that you name ASPNET.
6. Open a command prompt, and then type iisreset.

STATUS

This behavior is by design.

"Server Application Unavailable" Issue on Windows XP

I heard about the following from Scott Guthrie (Product Unit Manager for ASP.NET):
------------------------------------------------------------------------------------------

We have identified an issue with the recent MS03-32 Security Update for Internet Explorer security patch and ASP.NET V1.0 running on Windows XP. This patch can be installed manually or by obtaining recent critical updates from the Windows Update site.

The symptom of this issue is that after installing the patch, all requests to ASP.NET result in an error message saying "Server Application Unavailable".

This issue only impacts installations running ASP.NET V1.0 on Windows XP Professional. It *does not* impact machines running Windows 2000 or Windows Server 2003. It also *does not* impact machines running Windows XP with ASP.NET v1.1 installed.

We are working hard on a permanent solution for this issue. In the meantime, you can visit the below page to learn about the problem as well as a safe workaround you can apply immediately to fix the issue:

http://www.asp.net/faq/ms03-32-issue.aspx

Included on the page with the details is a link to a new forum dedicated to the problem (http://www.asp.net/Forums/ShowForum.aspx?tabindex=1&ForumID=128). Please post any questions or issues you run into with this issue in this forum -- we on the ASP.NET team will be actively monitoring these posts and will be able to provide technical help to hopefully address them.

Many apologies for the inconvenience that this has caused. We'll post additional information as it becomes available.

Thanks,

ASP.NET Team