IIS problem with ASP.Net when migrating from win2003 server to Win XP

[AndyH1]

A few weeks ago I joined a new group and have been forced to do development on Win XP rather than on a win 2003 server environment I used to due to company policy (everyone has to have same build).

Iv'e been trying to cope with the limitations of win XP to run ASP.Net sites and have encountered two problems. I wondered if anyone can advise.

The first is that I am trying to run a site I created before in a win 2003 server environment which ran fine in that environment. As you can only have one default site on XP the only way I gather on win XP to do multiple sites is to create a virtual directory for a site and run it under this in XP. This is not great as you can't assign references like href="/Admin/" anymore since you can't set up host header values such localsite.company.com in IIS (unless someone can advise me how?).

So Iv'e set up a virtual directory under the default web site in IIS called 'newsbpc' and make the call through my browser as

http://localhost/newsbpc/

However when I do this I get the error below:

Server Error in '/newsbpc' Application.

The current identity (SB005371\ASPNET) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: The current identity (SB005371\ASPNET) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): The current identity (SB005272\ASPNET) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) +3570267
System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags) +218

[HttpException (0x80004005): The current identity (SB005272\ASPNET) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3465427
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +69
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +279

I have tried giving 'ASP.Net Machine Account (SB005272\ASPNET) Full Access to the 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files' and 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\

tried IUSR and IWAM. In desperation I even gave everyone full acceess (only temporary) but still got this error (restarting the computer each time to make sure it came into effect). I'm at a complete loss what to do now, can anyone advise?

The second problem I have is I can browse the site if I'm in the Visual Studio 2005 environment using the ASP.Net Development server. The problem is that that some of my menus are cached for efficency. On the win 2003 server all I had to do was clear the cache on the browser (as I was using the '

http://localsite.company.com'

address rather than the development server to look at the site, whenever I updated the user control. With the development server even if I clear the cache on my browser it doesn't sem to update the site so if I modify a user control it still remains the old version when I browse view in browser, I assume it is not clearing the development server cache. Even if I build the site it still keeps the old version, again any help would be appreciated

thanks
Andy

 

[AndyH1]

Have tried all the things mentioned in here

http://forums.asp.net/t/883471.aspx

inc %windir%/Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i -enable

but still not luck - anybody got other ideas, I'm getting desperate. Only thing i can't do which was mentioned is reinstall windows (I'm not allowed)

Thanks
Andy