<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How to use Gadgeteer Interfaces directly from your application</title><link>http://blogs.msdn.com/b/net_gadgeteer/archive/2011/11/10/net-gadgeteer-interfaces.aspx</link><description>One of the benefits of the .NET Gadgeteer design is that it provides ready-to-use hardware modules. Module designers can build libraries in such a way that they take care of the lower-level communication protocols and electrical signals that need to take</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: How to use Gadgeteer Interfaces directly from your application</title><link>http://blogs.msdn.com/b/net_gadgeteer/archive/2011/11/10/net-gadgeteer-interfaces.aspx#10236467</link><pubDate>Sat, 12 Nov 2011 15:28:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10236467</guid><dc:creator>Mike Dodaro</dc:creator><description>&lt;p&gt;Great piece! &amp;nbsp;And the online socket types table makes easy to see exactly what you mean any place in the reference.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10236467" width="1" height="1"&gt;</description></item></channel></rss>