Edit#3 BLINKY LIVES !!!!
When I purged the broken (Release 4.1) SecretLabs libraries that I had somehow acquired, Blinky works including single-stepping from MSVC. This is running on firmware compiled from the 4.2.1 source using the free GCC compiler (instead of the $5000 one-computer-only RVDS one) following these instructions ( posts for context ) from ziggurat29 (monster thanks again, buddy!).
Details:
Initially I wasn't able to get any of the SecretLabs assemblies to load except the diagnostic (it complained there was no SecretLabs.NETMF.Hardware; so it refused the SecretLabs.NETMF.Hardware.Netduino DLL I'd imported -- huh?). So I dumped them, spent a couple minutes with the board schematic and blinked
Microsoft.SPOT.Hardware.Cpu.Pin.GPIO_Pin10 instead of SecretLabs.NETMF.Hardware.Netduino.Pins.ONBOARD_LED
It worked fine! Then I switched back to the compiled source (I was debugging with the official download firmware once I realized that had the problem too after I tried to switch back to 4.2 QFE1 SDK and Porting Kit and Netduino SDK) and verified that worked. Finally, I tried switching to the SecretLabs ONBOARD_LED, and that worked, too.
While Visual Studio 10 was linking, I noticed a message saying it was downloading SecretLabs.NETMF something -- presumably that's why it worked. That reminded me that I'd seen that message flash up when I first ran MSVS10 after switching back to QFE1. I'm wondering if that's where my 4.1 SecretLabs assemblies came from that have been messing me up the last day or so.
At a programming conference long ago I met a programmer who had named his business "Abracadabra Typesetting" to be first in the Yellow Pages listing (I told you it was long ago). He'd discovered that name was a big mistake: customers told him it made them afraid his business might go "Poof!". These automagical downloads are charming when they just work, but now every time I see it, I'll worry what might have broken. At least give us a way to know what was downloaded if we miss the 5-second popup.
Anyway: all's well that ends well. I can finally make the firmware changes and give my boss what he is clamoring for (just not eager-to-buy-a-$5000-tool-for-what-should-have-been-a-small-project clamoring). I suspect we aren't the only ones who'll be very happy about this capability.
Howie
============== OLDER, FOR BACKGROUND ONLY =====================
Edit#2: In trying to go back to 4.2 QFE1, I clearly have gotten some Netduino 4.1 assemblies somehow. The version of Microsoft.SPOT.Hardware that two of them ask for (4.1.2821.0) is the exact version in my 4.1 assembly. I am trying to get the SecretLabs 4.2 references to link properly instead of the 4.1. Then I should be developing on top of an interop-ready system using the free GCC compiler; yah!
Edit #1
Hi --
I'm having a related problem. After uninstalling the QFE2 SDK and PK and installing 4.2 QFE1 versions, a Blinky project created in my MS Visual Studio 10 downloads but refuses to run, not only on the GCC-compiled version that I built following ziggurat29's procedure here , but even on the stock 12/3/2012 firmware download (NetduinoPlus2_Firmware_4.2.1.2.dfu). Visual Studio apparently is still looking for the wrong version of modules: Debug output at the end of this.
Chris, I think somewhere you mentioned unzipping an update over SecretLabs SDK Visual Studio sources. Can that work in reverse, or do I need to uninstall and reinstall Secret Labs SDK VS?
Thanks!
Howie
================ Debug output on attempted download ===================
(note cleaning and rebuilding got rid of these errors, but it still failed to initialize after the download)
Create TS.
Loading start at 806a328, end 808443c
Assembly: mscorlib (4.2.0.0)
Assembly: Microsoft.SPOT.Native (4.2.0.0)
Assembly: Microsoft.SPOT.Hardware (4.2.0.0)
Assembly: Microsoft.SPOT.Net (4.2.0.0)
Assembly: System (4.2.0.0)
Assembly: Microsoft.SPOT.Hardware.SerialPort (4.2.0.0)
Assembly: Microsoft.SPOT.IO (4.2.0.0)
Assembly: System.IO (4.2.0.0)
Assembly: Microsoft.SPOT.Hardware.PWM (4.2.0.1)
Assembly: Microsoft.SPOT.Hardware.Usb (4.2.0.0)
Assembly: SecretLabs.NETMF.Diagnostics (4.2.0.0)
Assembly: SecretLabs.NETMF.Hardware.Netduino (4.2.1.0)
Assembly: Microsoft.SPOT.Hardware.OneWire (4.2.0.0)
Assembly: Microsoft.SPOT.Time (4.2.0.0)
Loading Deployment Assemblies.
Attaching deployed file.
Assembly: np2Blnk (1.0.0.0)
Attaching deployed file.
Assembly: SecretLabs.NETMF.Hardware.Netduino (4.1.0.0)
Attaching deployed file.
Assembly: SecretLabs.NETMF.Hardware (4.1.0.0)
Resolving.
Link failure: some assembly references cannot be resolved!!
Assembly: SecretLabs.NETMF.Hardware.Netduino (4.1.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.1.2821.0)
Assembly: SecretLabs.NETMF.Hardware.Netduino (4.1.0.0) needs assembly 'mscorlib' (4.1.2821.0)
Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) needs assembly 'mscorlib' (4.1.2821.0)
Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.1.2821.0)
Error: a3000000
Waiting for debug commands...
The program '[0x1] Micro Framework application: Managed' has exited with code 0 (0x0).
