Link to home
Start Free TrialLog in
Avatar of infotechelg
infotechelgFlag for United States of America

asked on

Visual Studio 2010 Crashes on Publishing

I have a new staging server running Windows Server 2008 (running IIS7) and recently started coding in .NET 4.0 using Visual Studio 2010 and when I try to publish to this server using a mapped path to the server, it crashes. The bin publishes, but then it crashes after that.

It's weird because I tried first publishing on the server in the inetpub/wwwroot folder and it was crashing. So then I created a new folder outside of the inetpub folder and published there instead. The first time I published to this new folder, it worked. But every time I've tried to publish to that folder since, Visual Studio crashes.

What's going on?
Avatar of Cimperiali
Cimperiali
Flag of Italy image

I usually publish meaning to compile the web application, not to truly deploy to iis. Onche plublished in a folder, I keep the file published and manually copy to a virtual directory. As an alternative you can
you can create a deployment project that deploys your ASP.NET application to a virtual directory.

 1)start a (web) setup project
 2)in the web setup project, go to the "File System View".
 3)right-click on the "Web Application Folder" and select properties
 4)find the in the "VirtualDirectory" attribute and specify the virtual directory to deploy your web application .
 
ASKER CERTIFIED SOLUTION
Avatar of Cimperiali
Cimperiali
Flag of Italy image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of infotechelg

ASKER

I suppose I could publish somewhere else then transfer the files over, but I never had to do this while using Visaul Studio 2005. Regarding your link, I don't know what DiscountASP.NET is. I don't think this link applies to me.
oppsss. it is too late here, I have to go to sleep. Sorry for misleading you. Cesare
Ok...anyone else?
The link posted here was irrelevant, but the statement "could it be permissions?" got me thinking. I contacted our IT guys to make sure my username was set up as an administrator on the server and it wasn't. They added me, and now things SEEM to be working properly.