Home Dashboard Directory Help
Search

There was no endpoint listening at net.pipe: http:// localhost /CBMOutOfProcService by Fred Chateau


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


4
0
Sign in
to vote
Type: Bug
ID: 785134
Opened: 4/19/2013 8:19:57 AM
Access Restriction: Public
0
Workaround(s)
view
4
User(s) can reproduce this bug

Description


I am receiving this error after I installed Update 2.

The error manifests itself as a squiggly line below the entire page or control declaration when using the ASP.NET view engine. It it also prefaced with "ASP.NET Run-Time Error". The project seems to compile and run fine, but the error seems to be interfering with normal editor font colors within ASP tags.

I have re-installed my add-ins (Reflector and ReSharper) but that didn't help. I also performed a repair using Update 2, which didn't work either.

The error does not occur in Administrator mode.

It doesn't happen on two other development machines I use, and the configuration on all three machines is the same. Operating system is Windows 8.
Details
Sign in to post a comment.
Posted by Microsoft on 5/1/2013 at 1:13 PM
Hi,
Thank you for contacting us with this issue and we would like to work with you to resolve this.
Could you give us some more details on your project and its componetsm for us to understand the scenario better

Thanks
Posted by BillB1234 on 4/22/2013 at 5:43 AM
This is similar to this issue: https://connect.microsoft.com/VisualStudio/feedback/details/780930/unit-test-debugging-not-working#tabs

The error message also refers to "no endpoint listening at net.pipe".
Posted by Microsoft on 4/22/2013 at 12:51 AM
Thanks for your feedback.

We are rerouting 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.
Posted by Microsoft on 4/19/2013 at 8:54 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.