Last post Jan 07, 2013 03:43 PM by rmdw
Dec 30, 2012 12:27 AM|rmdw|LINK
I have a situation where my app is running fine within the VS2012 IDE but crashes when I deploy it to a server running IIS7. So I need to run it within the VS2012 IDE but use IIS rather than the built-in development server.
In my situation both my development machine ("WORKSTATION") and my server ("MULTIMEDIA") are running Windows 7 (64-bit). IIS is only activated on the server.
I can access the deployed app from my development machine by typing this into the browser: http://MULTIMEDIA\Incentives ("Incentives" is the name of my app). Though the app does crash, at least I know that the compiled, deployed code is being run. So I
figure that I can also run it from VS2012 on my development machine.
Here's what I did on the server:
Here's what I did in VS2012:
Note: "Start Without Debugging" actually does work - in the same way that running the app directly from the browser works - but is of little use to me because I need to resolve why it's crashing.
I've read through everything I can find but have not been able to find a solution yet. What am I failing to do?
Dec 31, 2012 06:44 AM|DarthSwian|LINK
Have you given the directory where your application code is the right security for IIS to run? I believe you need to allow NETWORK SERVICE, IUSR to have privelages to read, write and modify
Jan 07, 2013 04:59 AM|Steven Cheng - MSFT|LINK
Hi rmdw, If you don't need to serve request from remote test clients (when running/debugging the web app in vs 2012), you can consider using IIS express which is light weight version of IIS and has less requirements of installation (can be setup side by
side with full version of IIS)
#Introducing IIS Express
#IIS Express Overview
#Web Servers in Visual Studio for ASP.NET Web Projects
Jan 07, 2013 03:43 PM|rmdw|LINK
My client will be using IIS so therefore I want to test everything in IIS.
It makes no sense to me to "approximate things" by running IIS Express.
In any case, I am able to:
The one thing I'm unable to do is run the app in VStudio from my workstation, which does not have IIS running locally. I've spent several hours back & forth with Microsoft tech personnel to try to resolve the Remote Debugger issues but to no avail. So
I will just stick with #2 above as my only way to troubleshoot problems when running the app in IIS.