The Netduino forums have been replaced by new forums at community.wildernesslabs.co.
This site has been preserved for archival purposes only
and the ability to make new accounts or posts has been turned off.
For those of you that would like to build your own installer: 1. Check out the full source tree of NETMF from netmf.codeplex.com. 2. Unzip the attached file into the root of the client_v4_3 directory. 3. Open a VS 2013 developer command prompt and cd to the client_v4_3 directory. 4. > setenv_vs.cmd 12 5. > msbuild sdk.dirproj /p:flavor=release The build output will be located at: client_v4_3BuildOutputpublicReleaseServermsmMicroFrameworkSDK.MSI Chris
I'm running Visual Studio Express 2013 for Windows Desktop on a Windows 8.1 machine and ran into an issue when attempting to install the .NET MF SDK4.3. The installer says I don't have Visual Studio 2013 or Visual Studio Express 2013 for Windows Desktop installed but I actually do have Express. Any ideas?
Spiked--very interesting. The SDK installer actually runs that same command-line argument to update the Visual Studio templates. I wonder if perhaps we're starting it as an asynchronous process and if loading Visual Studio before it's done causes the procedure to abort.
eugenhuber--the Netduino 4.3.1 SDK, even though it is marked as experimental, is basically release quality. We always like to test with the final VS bits before calling it "release"--but we're using it full-time with the NETMF 4.3.1 R2 SDK Beta today. If you want to be on VS2013, go ahead and upgrade. If you run into any VS2013-specific troubles, let us know, swap back to VS2012 and we'll work with Microsoft to resolve.
That's why I said not 100% sure. I am 100% sure it was a command line argument to devenv, just not 100% which one. But yeah, I did spend 4-5 hours on it.
Note that I believe that requires Admin elevation, which may not happen during your install? But I also had your templates after your(and MF) install, they just disappeared later. From what I've read, this latest addition of 'portable library' stuff has created many new issues (hard coded links to v2.05 of System.Core), of which I am guessing this is just 1 more.