Plot spoiler: Install VB Express 2008, which includes an x64
remote debugger that satisfies the free Integrated VS Shell. C# Express 2008
probably would do the trick just as well.
Context: This is probably not something anyone would see
unless running on an x64 version of Windows.
Today I installed VS Shell 2008 for use in starting to learn
F#. Then I installed F#, made a new project.
Very cool that when I added a new .fs file, it was full of
code examples. Thanks guys!
But when I hit F5, VS errored out, babbling about how the
remote debugger was not registered, or found, whatever. It’s not like I was trying to remote debug, I
just hit F5. I discovered that Ctrl-F5 did work, but I wanted a debugger.
I vaguely kinda remembered seeing some sort of remote
debugger lite install on another machine some weeks/months ago when installing
an Express 2008, thought I’d give it a whirl. Grabbed VB Express 2008, sure
enough, an x64 remote debugger lite installed as part of VB.
I don’t know or care whether the lite remote debugger would
actually remote debug, because I’m just going to debug locally for now. It does
stop VS Shell 2008 from complaining when I hit F5, and I can debug F# code locally.
Stepping thru those code examples in the
.fs file was a trip; more study required.
In any case, this workaround does work for me. Your mileage
may vary.
If you install the Express Edition before VS Shell and F#,
that sequence might work, but I didn’t test it. I usually have VB or C# Express
always installed, so perhaps it’s only by small chance I tripped across this
and was able to do this workaround/bug (quirk?) report.