Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jun 22, 2012 07:01 AM by AxelD
Jun 22, 2012 07:01 AM|LINK
It's embarrassing for me to ask, but I can't find help to my problem, given above search criteria, in Google or here...
Here's my problem:
I have installed Visual Studio 2010 Ultimate SP1 on a fresh Windows Server 2008 R2 VM in order to debug one of my customer's projects.
The project requires IIS because a couple of IIS properties must be set at certain directories for the ASP.NET application to work properly. The internal team is working with IIS 6 / Windows Server 2003 yet.
I cannot set the project to use IIS without administrative privileges... So I'm then starting up VS2010 with administrative privileges in order to set the ASP.NET project to use IIS: I change the ASP.NET project's Web settings, save everything, close VS2010.
When I'm then re-opening VS2010 in standard user mode, the ASP.NET project doesn't load because I'm not running VS2010 with administrative privileges again.
OK, if I then re-open VS2010 with administrative privileges, set the ASP.NET project as startup project, start a debugging session, I won't be able to connect to my local SQL Server 2008 R2 Standard instance... When a SqlConnection gets opened in code, ASP.NET
throws an exception telling me that there is "no process at the other end of the pipe", although I've activated Named Pipes in SQL Server configuration.
Moreover, while debugging with administrative privileges, a message box opens in the background telling me that the debugger is not able to attach to w3wp.exe.
I guess I must be doing something very stupid, because I couldn't find any forum post describing the same problems I have.
Can someone please enlighten me on what I'm doing wrong here? I just want to work on an ASP.NET project with VS 2010 using IIS 7.5.
(By the way: The company developers have set up the ASP.NET project to be a MVC 3 project, however they're not using MVC. It's a standard ASP.NET Web Forms application. They had set up the MVC 3 project type "just in case". Perhaps this information is
helpful to you? Although I don't believe so.)
Your help is appreciated!