4

Closed

VSLab internal error: cannot communicate with Visual Studio through DTE

description

I cannot use the VSLab add-in.
 
System: XP, VS2005, VS2008

 

 
Step to create the problem...
a) Add-In Manager
b) select the VSLab add-in
 
Message box appears:
 
"Error loading the Code Window context menu item"
 
Error Information (in F# console):
 
[Loading C:\Program Files\University of Pisa\VSLab\vslabstartup.fsx]
 
namespace FSI_0005
 
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Error sending command to Visual Studio, RPC is likely busy, trying again (5 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (4 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (3 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (2 attempts left)...
Error sending command to Visual Studio, RPC is likely busy, trying again (1 attempts left)...
VSLab internal error: cannot communicate with Visual Studio through DTE
Managed DirectX is missing.
 
I verified that I have the latest DirectX and F# installed. I reinstalled VSLab.
Closed Jan 31, 2011 at 3:47 PM by cisterni
2010 refresh

comments

allenjs wrote Nov 17, 2008 at 3:51 AM

Same error for me. And it bombs when I load any of the sample script files and try to run them by highlighting the range and sending to FSI.

Repro is very simple -- clean Vista machine with VS2008 install. Install F# September 2008 CTP; verify F# working. Install VSLab, verify that it doesn't work.

honestas wrote Nov 22, 2008 at 5:10 AM

I added a discussion thread.

This should be a high priority issue, IMO. It keeps everyone from using the product.

honestas wrote Nov 22, 2008 at 5:50 AM

Basically, the Add-In will load with errors the first time. After it loads with errors, press Alt-Shift-V. This will reset the add-in, and it should load properly from that point forward.

wrote Nov 24, 2008 at 9:13 AM

gilesknap wrote Nov 24, 2008 at 9:15 AM

I have exactly this issue.

My configuration:-
Windows Vista SP1
VS2008 Shell Clean Install
F# Sept CTP Clean Install

gilesknap wrote Nov 24, 2008 at 9:18 AM

SORRY! I just read honestas comment. Pressing Alt-Shift-V after initial loading errors does indeed work.

wrote Jan 30, 2009 at 8:47 PM

wrote Jan 24, 2011 at 2:46 AM

wrote Jan 31, 2011 at 3:47 PM

wrote Feb 13, 2013 at 11:48 PM

wrote May 16, 2013 at 4:19 AM