Network Toolkit and Netduino Plus
#1
Posted 12 October 2010 - 11:57 PM
#2
Posted 13 October 2010 - 12:04 AM
#3
Posted 13 October 2010 - 02:03 AM
The MFToolkit has class libraries for both .NET Micro Framework devices and regular .NET. The projects and compiled DLL's prepended with "Micro" are meant for the .NET Micro Framework.
In order to make everything work with .NET Micro Framework 4.1, you'll will need to download the source code. Once you opened the solution, you will need to change the target framework for each project to .NET Micro Framework 4.1 (done in each project's properties section) and recompile the solution. For the regular .NET Framework projects (non micro) you'll need to set the target framework to .NET 4.0.
Then you'll be able to add references in your project to the newly compiled DLL's.
Hi, thanks for the quick response.
I understand what you're saying, I just don't follow how I can re-use the original DNS.dll, HTTP.dll, etc., if they have been compiled with a different version of .NET?
For example, I opened the MicroHTTPConsole project, I removed the missing references and re-added them from the root directory of the project.
The build failed initially because of this line:
Error 1 The type or namespace name 'ExtendedTimeZone' does not exist in the namespace 'Microsoft.SPOT' (are you missing an assembly reference?) D:\Visual Studio 2010\Projects\NetworkingToolkit\MicroHTTPConsole\Program.cs 25 28 MicroHTTPConsole
I simply commmented it out, and now the build is returning this:
------ Rebuild All started: Project: MicroHTTPConsole, Configuration: Debug Any CPU ------
MicroHTTPConsole -> D:\Visual Studio 2010\Projects\NetworkingToolkit\MicroHTTPConsole\bin\Debug\MicroHTTPConsole.exe
C:\Program Files (x86)\MSBuild\Microsoft\.NET Micro Framework\v4.1\Device.targets(402,5): error MSB3021: Unable to copy file "D:\Visual Studio 2010\Projects\NetworkingToolkit\LE\MicroDNS.pe" to "bin\Debug\LE\MicroDNS.pe". Could not find a part of the path 'D:\Visual Studio 2010\Projects\NetworkingToolkit\LE\MicroDNS.pe'.
C:\Program Files (x86)\MSBuild\Microsoft\.NET Micro Framework\v4.1\Device.targets(402,5): error MSB3021: Unable to copy file "D:\Visual Studio 2010\Projects\NetworkingToolkit\LE\MicroHTTP.pe" to "bin\Debug\LE\MicroHTTP.pe". Could not find a part of the path 'D:\Visual Studio 2010\Projects\NetworkingToolkit\LE\MicroHTTP.pe'.
C:\Program Files (x86)\MSBuild\Microsoft\.NET Micro Framework\v4.1\Device.targets(402,5): error MSB3021: Unable to copy file "D:\Visual Studio 2010\Projects\NetworkingToolkit\LE\MicroNTP.pe" to "bin\Debug\LE\MicroNTP.pe". Could not find a part of the path 'D:\Visual Studio 2010\Projects\NetworkingToolkit\LE\MicroNTP.pe'.
C:\Program Files (x86)\MSBuild\Microsoft\.NET Micro Framework\v4.1\Device.targets(402,5): error MSB3021: Unable to copy file "D:\Visual Studio 2010\Projects\NetworkingToolkit\LE\MicroIO.pe" to "bin\Debug\LE\MicroIO.pe". Could not find a part of the path 'D:\Visual Studio 2010\Projects\NetworkingToolkit\LE\MicroIO.pe'.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========
#4
Posted 13 October 2010 - 02:10 AM
#5
Posted 13 October 2010 - 02:27 AM
#6
Posted 13 October 2010 - 02:36 AM
#7
Posted 13 October 2010 - 02:39 AM
#8
Posted 13 October 2010 - 02:39 AM
How can I tell?
Visual Studio should tell you how many bytes it's trying to deploy right after compiling...and right before your Netduino app starts running. It may be in the Output window.
Chris
#9
Posted 13 October 2010 - 11:46 AM
#10
Posted 13 October 2010 - 03:18 PM
#11
Posted 13 October 2010 - 03:55 PM
Attached Files
#12
Posted 13 October 2010 - 04:04 PM
#13
Posted 13 October 2010 - 07:43 PM
#14
Posted 18 October 2010 - 11:36 AM
There are source files for the MicroHTTP and MicroDNS projects. They look empty because they're just referring to the .cs files located at HTTP and DNS projects. Have a look at the textual view of MicroHTTP.csproj, there you'll find references like:Yes, I didn't see where the assembly source was included for the MicroHTTP, MicroDNS, etc. It would seem that the author just provided the assemblies and the source only for the sample applications that use it.
<Compile Include="..\HTTP\HttpServer.cs"> <Link>HttpServer.cs</Link> </Compile>
The same with MicroDNS, MicroNTP and maybe others.
Regards,
Myszor
#15
Posted 05 November 2010 - 01:17 PM
Download the release at http://mftoolkit.cod...ases/view/55143
Regards,
Michael
http://michael-schwarz.blogspot.com/
http://www.ajaxpro.info/
#16
Posted 06 November 2010 - 12:42 AM
There was a period at the end of you URL. The working link is http://mftoolkit.cod...ases/view/55143Download the release at http://mftoolkit.cod...ses/view/55143.
#17
Posted 06 November 2010 - 08:32 AM
There was a period at the end of you URL. The working link is http://mftoolkit.cod...ases/view/55143
Thanks...
Michael
http://michael-schwarz.blogspot.com/
http://www.ajaxpro.info/
#18
Posted 02 December 2010 - 02:02 AM
#19
Posted 14 November 2011 - 10:52 PM
refer to: GHI Fez Cobra Solution
somehow one reference in the project file got the following XML attribute set: processorArchitecture=MSIL, once removed , was able to deploy
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users