5 replies to this topic

[Dan Kowalczyk]

Hello everyone. I hope your projects are all coming along well. I'm noticing what I believe are discrepancies between the .NETMF API documented on MSDN and what I'm able to access in Visual Studio.

 

For example, I was searching through the Microsoft.SPOT.Hardware.Utilities namespace and found that there are methods specified for getting machine time ([font="'courier new', courier, monospace;"][color=rgb(0,0,0);]GetMachineTime()[/color][/font]) and setting local time ([font="'courier new', courier, monospace;"]SetLocalTime( Datetime dt)[/font]) . When I try to access these methods from my application, they are unrecognized.

 

Another example is that the entire [font="'courier new', courier, monospace;"]Ws[font="arial, helvetica, sans-serif;"] (web service) namespace is not available.[/font][/font]

 

Could someone explain these discrepancies?

 

(A side question: Can N+ support NETMF 4.2? I saw some people on the forum using cool new features like the [font="'courier new', courier, monospace;"]PWMChannels [font="arial, helvetica, sans-serif;"]enum and wonder if it's possible. Is there a good resource for getting the Diff of 4.1 and 4.2?)[/font][/font]

 

[NooM]

what you are trying todo?

Utility.SetLocalTime(DateTime.Now); (example..) // working for me

 

the pwmchannels enum is a define from secretlabs, not microsoft. it just routes the pwmchannels to the right cpu.pwmchannel (thats from ms)

 

yes n+ supports 4.2.  4.2 is great!

 

for the webservice: sry no idea

[Chris Walker]

Hi Dan, Also...some of the classes are in add-on assemblies. Go to "Add References..." and check out the available NETMF assemblies. Some of the classes are in different assemblies than their desktop counterparts, to optimize for space. Chris

[Dan Kowalczyk]

Thank you both!

 

I was able to resolve this by adding a [font="'courier new', courier, monospace;"]Reference[/font]. I didn't know that the references (assemblies?) have a different naming scheme than the class names. This also clears up my confusion about why I couldn't find [font="'courier new', courier, monospace;"]System.Http[/font] in the APIs -- it's just a wrapper around the classes[font="'courier new', courier, monospace;"][font="arial, helvetica, sans-serif;"]. [/font][/font]

 

[font="'courier new', courier, monospace;"][font="arial, helvetica, sans-serif;"]I was also able to find the [font="'courier new', courier, monospace;"]Ws[font="arial, helvetica, sans-serif;"] namespace in the [font="'courier new', courier, monospace;"]MFWsStack [/font]assembly.[/font][/font][/font][/font]

 

Would it be correct to say that assemblies are a named collection of namespaces?

 

I'm downloading 4.2 now...

[Dan Kowalczyk]

By the way, I should've looked at the very top of the forum for the answer to my 4.1 v. 4.2 question (D'oh).

[Chris Walker]

Would it be correct to say that assemblies are a named collection of namespaces?

More specifically...assemblies are a collection of classes. These classes are generally in the namespace of the assembly--but that's more of a soft rule. In NETMF, the System.IO.Ports.SerialPort class is in Microsoft.SPOT.Hardware.SerialPort.dll, for instance. So you can usually find a class in the assembly of the same root namespace name. But sometimes they're separated out for space optimization reasons. Chris