Posts Tagged 'visual studio'

Silvertlight Spelling Error

Yes, you read that right. After the Visual Studio 2008 SP1 upgrade, here’s what my Help|About dialog looks like:

Spelling error in the VS 2008 SP1 Help|About dialog

Spelling error in the VS 2008 SP1 Help|About dialog

Look in the “Product Details” section at the bottom.

The Missing F# Visual Studio Add-In

UPDATE 2: Even weirder. I was unable to use Alt+Enter to run F# statements within the interactive console in Visual Studio 2008 on Vista, so I tried to uninstall F#. It hung with 2 seconds remaining. I switched gears, cancelled the F# uninstall, and moved to uninstall VSLab. This occured without error, but I found that F# was also uninstalled when the VSLab uninstall was complete.

After reinstalling F# 1.9.6.2, I now have:

  • The F# interactive console in Visual Studio 2008
  • The ability to use Alt+Enter to run F# statements

I don’t have:

  • The F# Add-In option in the Add-In Manager dialog.

Strange. Making progress!

**************************************************

UPDATE: Partial progress. I downloaded and installed the VSLab “Hal” release and the F# interactive console loads in Visual Studio 2008, but I get the error “Error loading the Code Window context menu item” when enabling the VSLabs Add-In:

Here’s the output from the F# console:

val ___VS_PID : int

> [Loading C:\Program Files\University of Pisa\VSLab\vslabstartup.fsx]

namespace FSI_0003

Binding session to ‘C:\Program Files\University of Pisa\VSLab\VSLabFSICore.dll’…
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’ve had no luck today figuring out how to get the F# Add-In for Visual Studio working. On both machines – one a Windows XP box running Visual Studio 2005, and another running Vista with Visual Studio 2008 – the F# Add-In option in Visual Studio’s Tools|Add-In Manager is missing.

I’m running F# September CTP, version 1.9.6.2. It may be a distro problem.

Anyone else run into this issue?

VS 2005 Debugging Broken on Vista

I’ve been trying to work around this problem for the last few months but the frustration has reached a boiling point.

VS 2005 is a great product — easily the best IDE of the Visual Studio line. Easy to use, customizable, well-integrated with the various tools I use, etc. However, since I’ve installed Vista Business, debugging directly out of VS 2005 has been a nightmare.

First I ran into the “Debugging failed because integrated Windows authentication is not enabled” error. Even when enabling Windows Authentication, I ran into the problem. So moving everything back to the Classic Pipeline worked, but I hated it — why have the new Integrated Pipeline available if you can’t use it?

Then, Microsoft released the hotfix KB 937523. Great? Not really. Now after F5 I get the error “IIS does not list an application that matches the launched URL“. I can debug to a root page, but not a subdirectory page. Irritating.

Another link to the IIS.net forums about this new issue.