Find content
Male
Unfortunately, it is not possible to move OneWire.cs to another project, because there is 'native driver' (the actual implementation of 1-Wire methods decorated with MethodImpl(MethodImplOptions.InternalCall) attribute) in the firmware and it must match the dll name and checksum, otherwise the exception is thrown; and this happens in runtime.
Could you please provide more details on why you need MyNamespace.OneWire? It is planned to include OneWire class in the official firmware (and get the rid of CW.NETMF). Also, you can derive your own OneWire class in MyNamespace:
namespace MyNamespace { public class OneWire : CW.NETMF.Hardware.OneWire { //... } }
Hi CW2
thanks for your replay, I was trieing to migrate your class to my Class Library only to better have all that I need in a whole project and have less namespace to import, and the final and better reason is to grove my knologe to be albe to create by myself a low level language implementation in Netduino. Like yuo can see in this other my post i'm becoming mad with a wind sensor and I need to decide if comunicate with it trought C# or C++ low level language, but for this I need to learn how do it, and your project seem perfect to learn.
For OneWire implementation i can wait the official firmware, but for wind sensor I need do by myself, no one seem have exprerencie with netduino.
