Chris,
I guess this firmware is for the Netduino only, not for the Mini nor Plus?
Is it possible to use both 4.2 and 4.1 next to each other for those devices?
Don't want to break the continuity of my workshop but also want to test 4.2

Oh dear, that SDK should be possible to be installed with only Visual Basic 2010 Professional installed right? Retorical question actually With only VB2010Pro installed, I get "Microsoft .NET Micro Framework SDK 4.2 (beta) requires Visual C# 2010 to be installed."
I consider that a bug since the SDK is also for Visual Basic. Installing C# helped.

Sure thing. Right now, it's just the v4.1.1b1 source merged with the .NET MF 4.2b1 changes...but as soon as we have the new ADC and PWM code checked in we'll post the full source. We'll definitely be posting the full source (with PWM out of beta) for the RC/RTM release.

This will detail pretty much what is left out and what is included. VB support on these platforms is not the same as full desktop version. Older legacy function, late binding, generics, old style error handling are all not supported. If your writing modern VB.NET code you should be fine but functionality is not full desktop functionality. So please be aware of the limitations.

Also enure optimization is enabled for all projects - by default it is turned on for new project but turning it off will prevent debugging from working correctly because of the limited framework functionality.

If I create an empty Netduino Plus project and add a breakpoint then it builds, deploys and breaks successfully. However if I add a reference to System.Ftp and build then I get the warning:

Warning 1 Could not resolve this reference. Could not locate the assembly "System.Ftp". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. FTPServer

If I then attempt to deploy and run the project I get:

Error 2 An error has occurred. Please check your hardware

I previously used the temporary binaries that were available on here about 24 hours ago. I had an issue where the MicroFramework was attempting to find assemblies in ~\v4.2\Assemblies\le\LE. Changing the AssemblyFolder registry key fixed this but I still encountered the System.Ftp issue. I then uninstalled the MicroFramework and Netduino SDK and re-installed using the current installer. Not sure if this impacted anything.

I've tried adding the actual .dll file as a reference directly but I get the same issue. I attempted to add the file "C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\System.Ftp.dll" I noticed that there isn't any mention of the assembly in the "be" folder, not sure if this is significant.

MSBuild says:

C:\Program Files (x86)\MSBuild\Microsoft\.NET Micro Framework\v4.2\Device.targets(517,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Ftp". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
For SearchPath "C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\be".
Considered "C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\be\System.Ftp.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\be\System.Ftp.exe", but it didn't exist.
For SearchPath "{Registry:Software\Microsoft\.NETMicroFramework,v4.2,AssemblyFoldersEx}".
Considered "C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\System.Ftp.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\System.Ftp.exe", but it didn't exist.
Considered "C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.1\System.Ftp.dll", but it didn't exist.
Considered "C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.1\System.Ftp.exe", but it didn't exist.
For SearchPath "{RawFileName}".
Considered treating "System.Ftp" as a file name, but it didn't exist.
For SearchPath "bin\Debug\".
Considered "bin\Debug\System.Ftp.dll", but it didn't exist.
Considered "bin\Debug\System.Ftp.exe", but it didn't exist.

I've attached a detailed MSBuild log, the project was cleaned and then run.

If anyone has it then could they send me be\System.Ftp.* please?

Any help would be greatly appreciated,

Joe

PS: It has just ocured to me that I installed the 64 bit version but I'm seeing a C:\Program Files (x86)\ path. Might re-try with the 32bit version.

When you add System.Ftp.dll to your project, be sure to add the one on the main ".NET References" page. If it's not there, add the version in the root assemblies folder--not the version in the LE folder. Visual Studio will automatically "step into" the LE folder to get the little-endian-specific version for compilation.

Also -- System.Ftp.dll relies on System.Http.dll, I believe. This means that it may not leave too much room for your code--and it also means that you may need the System.Http.dll file in your project (although that should get pulled in as a dependency automatically).

We did some testing with FTP in .NET MF 4.2 Alpha...so it should work in the Beta. If you continue running into issues, please let us know...and please post a bug report at CodePlex.

A bit more info; sorry that I can't edit it in to my previous post, it hasn't been approved yet.

I decompiled all of the installers and couldn't find any additional FTP assemblies but the amazingly techincal task of just copying the System.FTP.* files from the le folder to the be folder fixed the build issue (or rather I don't get any warnings at least.)

The project runs in the emulator and hits the breakpoint.

The FTP sample project runs in the emulator too and creates FTPListener objects etc correctly so there doesn't seem to be anything wrong with the assembly.

When deploying to the Netduino is there anyway to make it more verbose?

I noticed that the Netduino SDK installer doesn't contain System.Ftp.dll I suppose that as long as the hardware layer works correctly it shouldn't matter. ILDasm doesn't show anything networking related in it (but I don't know what I'm looking for.) Is networking/ftp actually supported in this beta?

Hi Chris,
Sorry I didn't see your reply. I had been adding to that post bit by bit, feel free to merge the posts if needed. I'm coding in C#.
I just tried referencing System.Http.dll but no luck. I think I might try reinstalling everything on a fresh box and re-flashing the bootloader and firmware tomorrow.
Glad to hear that it supports FTP,
Joe

Code that worked on 4.1 but doesn't work on 4.2 breaks with this error:
Error 1 The type or namespace name 'Utility' does not exist in the namespace 'Microsoft.SPOT.Hardware' (are you missing an assembly reference?) C:\Users\Stefan\Documents\Visual Studio 2010\Projects\Super Demo\Super Demo\FusionWare.SPOT\Stopwatch.cs 35 56 Super Demo
Appairently 'Microsoft.SPOT.Hardware.Utility' isn't available anymore. Is this by design or by flaw?

Code that worked on 4.1 but doesn't work on 4.2 breaks with this error:
Error 1 The type or namespace name 'Utility' does not exist in the namespace 'Microsoft.SPOT.Hardware' (are you missing an assembly reference?) C:\Users\Stefan\Documents\Visual Studio 2010\Projects\Super Demo\Super Demo\FusionWare.SPOT\Stopwatch.cs 35 56 Super Demo

Appairently 'Microsoft.SPOT.Hardware.Utility' isn't available anymore. Is this by design or by flaw?

Stefan--can you post this as an issue on the netmf.codeplex.com. It may be by design--but if it does we need to find a new way to do a few of its features.

I see the methods in C:\MicroFrameworkPK_v4_2\Framework\Core\Native\HW_Utility.cs...so I'm not sure why it's not working. Do you have Microsoft.SPOT.Native.dll as a reference in your project?