Search

System.Runtime.InteropServices.COMException in WebApplication project by kulov

Closed
as Fixed Help for as Fixed

10
Sign in to vote
0
Sign in to vote
Sign in
to vote
Type: Bug
ID: 317124
Opened: 12/12/2007 1:09:47 PM
Access Restriction: Public
3
Workaround(s)
10
User(s) can reproduce this bug
when you try to open WebApplication project set up to use IIS and web site url that can not be found you will get System.Runtime.InteropServices.COMException message box.
the same you will get if you run VS2008 without elevated privileges, because VS can not access IIS metadata.
Details (expand)
Product Language
English

Version

Visual Studio 2008 (All Products and Editions)
Operating System
Windows Vista
Operating System Language
English
Steps to Reproduce
open the attached project and you will get the error
Actual Results
do not validate the existence of url and do not try to access IIS with elevated privileges
if you are getting the project from source control, chances that you have the web site predefined are not big
Expected Results
open the attached project without errors
TAP Code (if applicable)
 
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
2 attachments
error.jpg
WebApplication1.zip
Sign in to post a comment.
Posted by Microsoft on 12/12/2007 at 11:30 PM
Thanks for your feedback. We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 1/7/2008 at 10:52 AM
Thank you for reporting this issue. We have been able to reproduce the problem and are fixing it in the next release of the product (targetted for a service pack release).

Thanks,
The Web Development Tools Team
Posted by DavidChristiansen on 1/24/2008 at 10:01 AM
Thanks to http://www.codeattest.com/blogs/martin/2008/01/comexception-loading-solution.html I found the solution to my occurance of this bug and indeed this BUG report.
Posted by PAFreshney on 2/1/2008 at 7:04 AM
I came across this error after converting a 1.1 based Web Application (developed with VS2003) to a 2.0 based Web Application. Strangely though, when I chose to convert it to 3.5 instead the error never appears and I can access the project with no problems.

The URL being used to connect to IIS does exist and is available.