It seems that if System.Security (from .NET MF) is added to a project and then deployed to my Netduino 3, the entire device crashes and burns. It becomes completely unresponsive and I am left with no option but to flash the device. It doesn't matter if you are actually using the assembly; just having it in the references will crash the Netduino, even if nothing from the assembly is even used. Once the reference is removed, everything is fine.
When deploying/debugging with Visual Studio, the debugger halts as it tries to load the symbols for System.Security. But even if the debugger is not attached, the Netduino just dies.
I have reproduced this with a very simple project that simply flashes the LED.
I have noticed that System.Security does not appear to be in the firmware for 220.127.116.11, even though Visual Studio marks "Copy Local" as false. Setting "Copy Local" to true doesn't help because then VS says that it can't find %ProgramFiles(x86)%\Microsoft .NET Micros Framework\v4.3\Assemblies\le\LE\System.Security.pe ... which doesn't exist at that location although it is in the Assemblies\le folder. Creating this folder and moving the files there so VS will happily try to deploy does not fix anything.
Any ideas on why this is happening?
Right now, there's nothing that I really need in this assembly but since it kept me up until the wee hours of the morning last night, I'm really curious if anyone has any ideas on what's going on.