Netduino home hardware projects downloads community

Jump to content

The Netduino forums have been replaced by new forums at This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.

Adding a reference to System.Security

  • Please log in to reply
2 replies to this topic

#1 timothyp



  • Members
  • PipPip
  • 24 posts

Posted 14 January 2015 - 06:40 AM

I created a new project for the Netduino Plus 2, running 4.3.1 (http://forums.netdui...-firmware-v431/)  and made the led blink.


Works like a charm, obviously  :D

However, as soon as I add a reference to System.Security.dll and try to deploy trouble kicks in.

The device is rebooted because it's not in the correct state and after that it shows up in 
Windows as a device that is malfunctioning / cannot be recognized.


The only thing to do at this point is to reboot it in DFU mode and erase the application.

Removing the System.Security.dll reference solves the problem.


At first I thought it might be to big, but looking at the dll it's not that big (33k) and
the netduino plus 2 has 384kb available (?)  


When adding a reference to System.IO.dll instead (27kb) there are no issues (just as an example).


(Also I'm wondering if System.Security.dll isn't already available as part of the firmware itself)


So... I have no idea what's causing the issues, any suggestions?


#2 iced98lx


    Advanced Member

  • Members
  • PipPipPip
  • 134 posts
  • LocationSouth Dakota

Posted 14 January 2015 - 04:31 PM

So you went into the project -> references area, right clicked, and hit "Add Reference" and selected from the .NET tab, built and deployed (the rebooting for correct state is normal btw) and it locks?

#3 timothyp



  • Members
  • PipPip
  • 24 posts

Posted 25 January 2015 - 03:12 PM

Indeed. After adding the reference it tries to reboot for the application to start and the debugger to connect,

but after that it is dead. It does not complain about the size of the assemblies (that was my first guess, that they were to big) either.


The only thing I can do then is use the DFU tools to erase everything and flash .NET MF 4.3.1 again.

Then I simply remove the reference, start it again and verifies it works. I do not change the code as it doesn't actually
use any of the code in those assemblies yet (since it is a test)

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.