<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>.NET Micro Framework</title><link>http://netmf.codeplex.com/project/feeds/rss</link><description>The .NET Micro Framework combines embedded managed code development with Microsoft Visual Studio&amp;#174; tools to deliver exceptional productivity on small devices.</description><item><title>Commented Issue: Add support for IronPython [1839]</title><link>http://netmf.codeplex.com/workitem/1839</link><description>In our work with embedded systems, more and more platforms are supporting Python as their language of choice.  Although we love C&amp;#35; &amp;#40;and even love seeing VB being used&amp;#33;&amp;#41; we really would like a way to standardize our embedded development on a single language ... and currently Python is growing to be that language.&lt;br /&gt;&lt;br /&gt;I know that IronPython seemed to fall by the wayside, and shift outside ... but it would be awesome to get Python support back in ... and in the .NET Micro Framework.&lt;br /&gt;Comments: ** Comment from web user: khmesmer ** &lt;p&gt;Python support for the micro frame work would expand the product base considerably and it would be very much in the interest of Microsoft and the open source community to provide this. &lt;/p&gt;&lt;p&gt;My understanding of doing this is that by providing Python support in the .net Micro Framework that boards built on this standard can seamlessly interact in environments where Python is used. From remote shell programming to system integration the support base expands considerably. If Shell support is possible with these boards now remote access is possible opening up robotic applications and so on.&lt;br&gt;This is not currently available with the current languages provided and is a limiting factor. Limits are to be avoided if possible.&lt;/p&gt;&lt;p&gt;The logic follows : &amp;quot;Well then why not just integrate all languages into it and maximize the support?&amp;quot; &lt;br&gt;The answer is make the full dot net framework integrate seamlessly into the micro framework where you simply down load the latest version of the full dot net framework and the framework decides what the board supports based upon the standards established by the open source community. That goes beyond the scope of this post however.&lt;/p&gt;&lt;p&gt;Python would be a major step in this direction and would truly move the .net micro framework forward in the market. I am not an expert on the subject but I am unaware of any other language not python based that can accomplish what python does with the same wide user base python has.  It's a very smart step.&lt;/p&gt;</description><author>khmesmer</author><pubDate>Sat, 18 May 2013 17:05:35 GMT</pubDate><guid isPermaLink="false">Commented Issue: Add support for IronPython [1839] 20130518050535P</guid></item><item><title>Created Unassigned: StringBuilder.Replace previous bug resurfaced again [2012]</title><link>http://netmf.codeplex.com/workitem/2012</link><description>Hello guys,&lt;br /&gt;the following code have already demonstrated a bug with StringBuilder.Replace back in 4.1 which supposedly was patched according to the link below.&lt;br /&gt;https&amp;#58;&amp;#47;&amp;#47;netmf.codeplex.com&amp;#47;SourceControl&amp;#47;list&amp;#47;patches&amp;#63;page&amp;#61;1&lt;br /&gt;&lt;br /&gt;but now it is back in 4.2, and 4.3 can you guys confirm and apply a permanent patch...&lt;br /&gt;&lt;br /&gt;test code&amp;#58;&lt;br /&gt;String replaced &amp;#61; new StringBuilder&amp;#40;&amp;#34;My car is a a0a a1a a2a&amp;#34;&amp;#41;.Replace&amp;#40;&amp;#34;a0a&amp;#34;,&amp;#34;blue&amp;#34;&amp;#41;.ToString&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;            Debug.Print&amp;#40;replaced&amp;#41;&amp;#59; &amp;#47;&amp;#47; replaced&amp;#58;  yMy car is ablue a1a a2a&lt;br /&gt;&lt;br /&gt;thanks.&lt;br /&gt;</description><author>jcherrabi</author><pubDate>Thu, 16 May 2013 13:53:59 GMT</pubDate><guid isPermaLink="false">Created Unassigned: StringBuilder.Replace previous bug resurfaced again [2012] 20130516015359P</guid></item><item><title>Created Unassigned: StringBuilder.Replace previous bug resurfaced again [2011]</title><link>http://netmf.codeplex.com/workitem/2011</link><description>Hello guys,&lt;br /&gt;the following code have already demonstrated a bug with StringBuilder.Replace back in 4.1 which supposedely was patched according to the link below.&lt;br /&gt;https&amp;#58;&amp;#47;&amp;#47;netmf.codeplex.com&amp;#47;SourceControl&amp;#47;list&amp;#47;patches&amp;#63;page&amp;#61;1&lt;br /&gt;&lt;br /&gt;but now it is back in 4.2, and 4.3 can you guys confirm and apply a permanent patch...&lt;br /&gt;&lt;br /&gt;test code&amp;#58;&lt;br /&gt;String replaced &amp;#61; new StringBuilder&amp;#40;&amp;#34;My car is a a0a a1a a2a&amp;#34;&amp;#41;.Replace&amp;#40;&amp;#34;a0a&amp;#34;,&amp;#34;blue&amp;#34;&amp;#41;.ToString&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;            Debug.Print&amp;#40;replaced&amp;#41;&amp;#59; &amp;#47;&amp;#47; replaced&amp;#58;  yMy car is ablue a1a a2a&lt;br /&gt;&lt;br /&gt;thanks.&lt;br /&gt;</description><author>jcherrabi</author><pubDate>Thu, 16 May 2013 13:53:12 GMT</pubDate><guid isPermaLink="false">Created Unassigned: StringBuilder.Replace previous bug resurfaced again [2011] 20130516015312P</guid></item><item><title>Closed Feature: Support SerialPort.ReadExisting [107]</title><link>http://netmf.codeplex.com/workitem/107</link><description>Please vote to express your interest for this work item. &lt;br /&gt;&amp;#160;&lt;br /&gt;SUGGESTION &amp;#40;from Jan Kucera, forums on http&amp;#58;&amp;#47;&amp;#47;www.netmf.com&amp;#41; &amp;#58; &lt;br /&gt;&amp;#160;&lt;br /&gt;&amp;#34;... I wonder if exposing a Stream &amp;#40;SerialPort.BaseStream on .NET Framework&amp;#41; for use with the StreamReader&amp;#47;StreamWriter methods would help &amp;#91;...&amp;#93; &amp;#63;&amp;#160;Adding a stream wrapper&amp;#160;might&amp;#160;be cheaper than adding all these methods, and it should be even easy enough to implement it yourself... &amp;#34;&lt;br /&gt;</description><author>ZachLibby</author><pubDate>Thu, 16 May 2013 11:52:33 GMT</pubDate><guid isPermaLink="false">Closed Feature: Support SerialPort.ReadExisting [107] 20130516115233A</guid></item><item><title>Closed Feature: Sample support for Dallas / Maxim 1Wire devices [1142]</title><link>http://netmf.codeplex.com/workitem/1142</link><description>Please find in the attached ZIP a simple interop layer to utilise the free SDK for Dallas &amp;#47; Maxim 1Wire devices. &lt;br /&gt;&amp;#160;&lt;br /&gt;Feel free to use in any way that may be useful to you. Use entriely at your own risk. No warrenty etc ... &lt;br /&gt;&amp;#160;&lt;br /&gt;This code uses a single GPIO pin to talk to attached 1Wire device&amp;#40;s&amp;#41;. You set the selected GPIO in the managed C&amp;#35; code. &lt;br /&gt;&amp;#160;&lt;br /&gt;A demo application is included that will scan the 1Wire bus for devices and return a collection of IDs of devices found. &lt;br /&gt;The attached code has only been tested with a single 1Wire device attached to read its 64 bit ID.&lt;br /&gt;&amp;#160;&lt;br /&gt;Sample code to read the list of IDs of attached 1Wire Devices looks like this&amp;#58;&lt;br /&gt;&amp;#160;&lt;br /&gt;            OutputPort port &amp;#61; new OutputPort&amp;#40;DeviceSolutions.SPOT.Hardware.Meridian.Pins.GPIO4, false&amp;#41;&amp;#59;&lt;br /&gt;            OneWire ow &amp;#61; new OneWire&amp;#40;port&amp;#41;&amp;#59;&lt;br /&gt;            ArrayList IDs &amp;#61; ow.FindIDs&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;&amp;#160;&lt;br /&gt;The free Dallas 1Wire SDK includes samples for other 1Wire devices. The Interop may need some extending for some of the other devices as it currently only has basic support for read &amp;#47; write of bytes of data on the serial 1wire bus. More complex functions then use these to achieve higher level functions.&lt;br /&gt;&amp;#160;&lt;br /&gt;The idea was that where the Dallas C&amp;#47;C&amp;#43;&amp;#43; SDK has code like&amp;#58;&lt;br /&gt;   &amp;#47;&amp;#47; success&lt;br /&gt;   printf&amp;#40;&amp;#34;Port opened&amp;#58; &amp;#37;s&amp;#92;n&amp;#34;,argv&amp;#91;1&amp;#93;&amp;#41;&amp;#59;&lt;br /&gt;   owTouchReset&amp;#40;portnum&amp;#41;&amp;#59;&lt;br /&gt;   owWriteByte&amp;#40;portnum,0x33&amp;#41;&amp;#59;&lt;br /&gt;   SwitchSN&amp;#91;0&amp;#93; &amp;#61; &amp;#40;uchar&amp;#41;owReadByte&amp;#40;portnum&amp;#41;&amp;#59;&lt;br /&gt;   SwitchSN&amp;#91;1&amp;#93; &amp;#61; &amp;#40;uchar&amp;#41;owReadByte&amp;#40;portnum&amp;#41;&amp;#59;&lt;br /&gt;   SwitchSN&amp;#91;2&amp;#93; &amp;#61; &amp;#40;uchar&amp;#41;owReadByte&amp;#40;portnum&amp;#41;&amp;#59;&lt;br /&gt;   &amp;#8230;&lt;br /&gt;&amp;#160;&lt;br /&gt;The C&amp;#35; code would become&lt;br /&gt;  OutputPort port &amp;#61; new OutputPort&amp;#40;DeviceSolutions.SPOT.Hardware.Meridian.Pins.GPIO4, false&amp;#41;&amp;#59;&lt;br /&gt;  OneWire ow &amp;#61; new OneWire&amp;#40;port&amp;#41;&amp;#59;&lt;br /&gt;  ArrayList IDs &amp;#61; ow.FindIDs&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;&amp;#160;&lt;br /&gt;  Debug.Print&amp;#40;&amp;#34;Port opened&amp;#34;&amp;#41;&amp;#59;&lt;br /&gt;&amp;#160;&lt;br /&gt;   ow.TouchReset&amp;#40;portnum&amp;#41;&amp;#59;&lt;br /&gt;&amp;#160;&lt;br /&gt;   ow.WriteByte&amp;#40;portnum,0x33&amp;#41;&amp;#59;&lt;br /&gt;   SwitchSN&amp;#91;0&amp;#93; &amp;#61; ow.ReadByte&amp;#40;portnum&amp;#41;&amp;#59;&lt;br /&gt;   SwitchSN&amp;#91;1&amp;#93; &amp;#61; ow.ReadByte&amp;#40;portnum&amp;#41;&amp;#59;&lt;br /&gt;   SwitchSN&amp;#91;2&amp;#93; &amp;#61; ow.ReadByte&amp;#40;portnum&amp;#41;&amp;#59;&lt;br /&gt;   &amp;#8230;&lt;br /&gt;&amp;#160;&lt;br /&gt;Explination of Folders in zip&lt;br /&gt;&amp;#160;&lt;br /&gt;&amp;#160;&lt;br /&gt;Managed Inerop assembly&amp;#58;  &amp;#92;MicroFrameworkPK_v4_1&amp;#92;Interops&amp;#92;ManagedCode&amp;#92;Pulsecor.SPOT.OneWire&lt;br /&gt;Native Driver DLL&amp;#58;               &amp;#92;MicroFrameworkPK_v4_1&amp;#92;Interops&amp;#92;NativeCode&amp;#92;Pulsecor.SPOT.OneWire&lt;br /&gt;Sample&amp;#58;                               &amp;#92;MicroFrameworkPK_v4_1&amp;#92;Product&amp;#92;Samples&amp;#92;OneWireDemo&lt;br /&gt;&amp;#160;&lt;br /&gt;Hope this is useful.&lt;br /&gt;&amp;#160;&lt;br /&gt;Regards&lt;br /&gt;Richard.&lt;br /&gt;</description><author>DoingNZ</author><pubDate>Thu, 16 May 2013 11:52:10 GMT</pubDate><guid isPermaLink="false">Closed Feature: Sample support for Dallas / Maxim 1Wire devices [1142] 20130516115210A</guid></item><item><title>Closed Feature: Better information on deploying [1209]</title><link>http://netmf.codeplex.com/workitem/1209</link><description>The &amp;#35;1 &amp;#40;almost daily&amp;#41; support issue we see is not having the correct firmware on the device. In the device boot up messages, you see &amp;#34;checksum mismatch&amp;#34; message but this is hidden between so many other messages.&lt;br /&gt;&amp;#160;&lt;br /&gt;A very small addition that would have great value to every NETMF user is by VS checking the assemblies checksum before it deploys the assemblies and give the user a warning message box. Perhaps, &amp;#34;Checksum Mismatch. Possible outdated firmware.&amp;#34; message.&lt;br /&gt;&amp;#160;&lt;br /&gt;Not just new users, experienced users also run into this trap. They download a new SDK or get an old device from the field and all they know is their device is not booting. A message box will save them hours of frustration.&lt;br /&gt;&amp;#160;&lt;br /&gt;GHI would love to contribute this but this has to be done in SDK not in PK.&lt;br /&gt;</description><author>lorenzte</author><pubDate>Thu, 16 May 2013 11:52:07 GMT</pubDate><guid isPermaLink="false">Closed Feature: Better information on deploying [1209] 20130516115207A</guid></item><item><title>Closed Issue: TimeService not closing socket after successful update [1702]</title><link>http://netmf.codeplex.com/workitem/1702</link><description>The SNTPClient&amp;#58;&amp;#58;Connect&amp;#40;&amp;#41; method is not closing the socket after a successful update of the time.&lt;br /&gt;A proposed fix for DeviceCode&amp;#92;pal&amp;#92;timeservice&amp;#92;driver&amp;#92;ntp.cpp &amp;#40;based on netmf 4.2 community branch&amp;#41; is attached.&lt;br /&gt;This fix also propagates socket error numbers to the managed application, which helps locating a failure.&lt;br /&gt;</description><author>lorenzte</author><pubDate>Thu, 16 May 2013 11:51:56 GMT</pubDate><guid isPermaLink="false">Closed Issue: TimeService not closing socket after successful update [1702] 20130516115156A</guid></item><item><title>Closed Issue: Debug.EnableGCMessages(true) Does not work in .NET MF 4.2 [1711]</title><link>http://netmf.codeplex.com/workitem/1711</link><description>See the thread here.  It appears that the EnableGCMessages method is broken.  &lt;br /&gt;http&amp;#58;&amp;#47;&amp;#47;forums.netduino.com&amp;#47;index.php&amp;#63;&amp;#47;topic&amp;#47;4807-cant-get-gcmessages-to-work&amp;#47;&lt;br /&gt;</description><author>lorenzte</author><pubDate>Thu, 16 May 2013 11:51:56 GMT</pubDate><guid isPermaLink="false">Closed Issue: Debug.EnableGCMessages(true) Does not work in .NET MF 4.2 [1711] 20130516115156A</guid></item><item><title>Closed Issue: Real world projects/devices? [1857]</title><link>http://netmf.codeplex.com/workitem/1857</link><description>I was not able to find any real world project&amp;#47;device that is using the .NET MF for getting started. How &amp;#34;important&amp;#34; is .NET MF compared to .NET CF&amp;#63; Since devices are getting better and better I am asking myself it makes sense getting started with .NET MF ...Thank you in advance for putting me into the right direction&amp;#33;--hfrmobile &amp;#40;Windows Mobile &amp;#38; Windows Phone developer&amp;#41;&lt;br /&gt;</description><author>lorenzte</author><pubDate>Thu, 16 May 2013 11:51:53 GMT</pubDate><guid isPermaLink="false">Closed Issue: Real world projects/devices? [1857] 20130516115153A</guid></item><item><title>Commented Issue: EWR weak points [2010]</title><link>http://netmf.codeplex.com/workitem/2010</link><description>Saving data into flash is an important feature for most of embedded devices. It allows to store configuration settings and user settings. On .netmf this is done by using EWR. While I recognize that serialization rises the level of abstraction in a lot of cases &amp;#40;xml, data transfert...&amp;#41;, I consider that EWR suffer of a lack of detail. As a result, debugging EWR is really complex. I am using EMX module from GHI Electronics and even if the premium library provides a method to flush extended weak reference, we need more details about the saving scheme. We need to know how much space are needed to store the data but there&amp;#39;s no convenient way to compute it and therefore we can&amp;#39;t know how long it takes to save data into flash memory.&lt;br /&gt;&lt;br /&gt;Finally for now I save an arraylist containing custom objects and there&amp;#39;s no convenient way to modify just a member of a given object. I am obliged to resave the arraylist entirely, which is time consuming and reduce the lifetime of the flash memory. I think this could be enhanced.&lt;br /&gt;Comments: ** Comment from web user: leforban ** &lt;p&gt;An other thing that suffer of a lack of information.&lt;br&gt;I am storing an array list of custom object and these objects can have different size (there's an other array list inside each instance). Let's consider that I store 3 instances A, B and C that have the same size. Then I modify B by adding elements to the inner array list. How is performed the memory management? B won't have enough place to be located between A and C. Does C is moved? is there fragmented memory?&lt;/p&gt;</description><author>leforban</author><pubDate>Tue, 14 May 2013 07:33:43 GMT</pubDate><guid isPermaLink="false">Commented Issue: EWR weak points [2010] 20130514073343A</guid></item><item><title>Commented Issue: EWR weak points [2010]</title><link>http://netmf.codeplex.com/workitem/2010</link><description>Saving data into flash is an important feature for most of embedded devices. It allows to store configuration settings and user settings. On .netmf this is done by using EWR. While I recognize that serialization rises the level of abstraction in a lot of cases &amp;#40;xml, data transfert...&amp;#41;, I consider that EWR suffer of a lack of detail. As a result, debugging EWR is really complex. I am using EMX module from GHI Electronics and even if the premium library provides a method to flush extended weak reference, we need more details about the saving scheme. We need to know how much space are needed to store the data but there&amp;#39;s no convenient way to compute it and therefore we can&amp;#39;t know how long it takes to save data into flash memory.&lt;br /&gt;&lt;br /&gt;Finally for now I save an arraylist containing custom objects and there&amp;#39;s no convenient way to modify just a member of a given object. I am obliged to resave the arraylist entirely, which is time consuming and reduce the lifetime of the flash memory. I think this could be enhanced.&lt;br /&gt;Comments: ** Comment from web user: gus_ghielec ** &lt;p&gt;The EWR flush and data integrity issue was point out long ago https://netmf.codeplex.com/workitem/1156&lt;/p&gt;&lt;p&gt;I think a direct user control over a flash section is better suited for many embedded users.&lt;/p&gt;&lt;p&gt;Gus - GHI Electronics&lt;/p&gt;</description><author>gus_ghielec</author><pubDate>Mon, 13 May 2013 17:33:18 GMT</pubDate><guid isPermaLink="false">Commented Issue: EWR weak points [2010] 20130513053318P</guid></item><item><title>Created Issue: EWR weak points [2010]</title><link>http://netmf.codeplex.com/workitem/2010</link><description>Saving data into flash is an important feature for most of embedded devices. It allows to store configuration settings and user settings. On .netmf this is done by using EWR. While I recognize that serialization rises the level of abstraction in a lot of cases &amp;#40;xml, data transfert...&amp;#41;, I consider that EWR suffer of a lack of detail. As a result, debugging EWR is really complex. I am using EMX module from GHI Electronics and even if the premium library provides a method to flush extended weak reference, we need more details about the saving scheme. We need to know how much space are needed to store the data but there&amp;#39;s no convenient way to compute it and therefore we can&amp;#39;t know how long it takes to save data into flash memory.&lt;br /&gt;&lt;br /&gt;Finally for now I save an arraylist containing custom objects and there&amp;#39;s no convenient way to modify just a member of a given object. I am obliged to resave the arraylist entirely, which is time consuming and reduce the lifetime of the flash memory. I think this could be enhanced.&lt;br /&gt;</description><author>leforban</author><pubDate>Mon, 13 May 2013 14:48:33 GMT</pubDate><guid isPermaLink="false">Created Issue: EWR weak points [2010] 20130513024833P</guid></item><item><title>Created Issue: StreamReader.Peek() misses last character [2009]</title><link>http://netmf.codeplex.com/workitem/2009</link><description>&amp;#35;Description&lt;br /&gt;When using a StreamReader on a MemoryStream, the  StreamReader.Peek&amp;#40;&amp;#41; method will not return the last character.&lt;br /&gt;&lt;br /&gt;&amp;#35;Steps to Repro&amp;#58;&lt;br /&gt;You can use the snippet below to repro the issue.   &lt;br /&gt;&amp;#96;&amp;#96;&amp;#96; C&amp;#35;&lt;br /&gt;const string s &amp;#61; &amp;#34;Hello, world&amp;#33;&amp;#34;&amp;#59;&lt;br /&gt;var b &amp;#61; Encoding.UTF8.GetBytes&amp;#40;s&amp;#41;&amp;#59;&lt;br /&gt;var memStream &amp;#61; new MemoryStream&amp;#40;b&amp;#41;&amp;#59;&lt;br /&gt;var reader &amp;#61; new StreamReader&amp;#40;memStream&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;int p&amp;#59;&lt;br /&gt;while &amp;#40;&amp;#40; p &amp;#61; reader.Peek&amp;#40;&amp;#41;&amp;#41; &amp;#62;&amp;#61; 0&amp;#41;&lt;br /&gt;&amp;#123;&lt;br /&gt;    Debug.Print&amp;#40;p &amp;#43; &amp;#34;&amp;#92;t&amp;#34;&amp;#43; &amp;#40;char&amp;#41; p&amp;#41;&amp;#59;&lt;br /&gt;    reader.Read&amp;#40;&amp;#41;&amp;#59;&lt;br /&gt;&amp;#125;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;This will produce the following debug output &amp;#40;notice the &amp;#39;&amp;#33;&amp;#39; is missing&amp;#41;&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;72&amp;#9;H&lt;br /&gt;101&amp;#9;e&lt;br /&gt;108&amp;#9;l&lt;br /&gt;108&amp;#9;l&lt;br /&gt;111&amp;#9;o&lt;br /&gt;44&amp;#9;,&lt;br /&gt;32&amp;#9; &lt;br /&gt;119&amp;#9;w&lt;br /&gt;111&amp;#9;o&lt;br /&gt;114&amp;#9;r&lt;br /&gt;108&amp;#9;l&lt;br /&gt;100&amp;#9;d&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;&amp;#35;Possible Solution&amp;#58;&lt;br /&gt;After looking at the StreamReader.Peek&amp;#40;&amp;#41; implementation, I think the problem can be found in this loop section &lt;br /&gt;&amp;#96;&amp;#96;&amp;#96; C&amp;#35;&lt;br /&gt;....&lt;br /&gt;        &amp;#47;&amp;#47; Move any bytes read for this character to front of new buffer&lt;br /&gt;        int totRead&amp;#59;&lt;br /&gt;        for &amp;#40;totRead &amp;#61; 0&amp;#59; totRead &amp;#60; m_curBufLen - m_curBufPos - 1&amp;#59; &amp;#43;&amp;#43;totRead&amp;#41;&lt;br /&gt;        &amp;#123;&lt;br /&gt;            m_buffer&amp;#91;totRead&amp;#93; &amp;#61; m_buffer&amp;#91;m_curBufPos &amp;#43; totRead&amp;#93;&amp;#59;&lt;br /&gt;        &amp;#125;&lt;br /&gt;...&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;It should work if the &amp;#34;- 1&amp;#34; is removed as follows&amp;#58;&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96; C&amp;#35;&lt;br /&gt;....&lt;br /&gt;        &amp;#47;&amp;#47; Move any bytes read for this character to front of new buffer&lt;br /&gt;        int totRead&amp;#59;&lt;br /&gt;        for &amp;#40;totRead &amp;#61; 0&amp;#59; totRead &amp;#60; m_curBufLen - m_curBufPos&amp;#59; &amp;#43;&amp;#43;totRead&amp;#41;&lt;br /&gt;        &amp;#123;&lt;br /&gt;            m_buffer&amp;#91;totRead&amp;#93; &amp;#61; m_buffer&amp;#91;m_curBufPos &amp;#43; totRead&amp;#93;&amp;#59;&lt;br /&gt;        &amp;#125;&lt;br /&gt;...&lt;br /&gt;&amp;#96;&amp;#96;&amp;#96;&lt;br /&gt;</description><author>michag</author><pubDate>Fri, 10 May 2013 19:42:02 GMT</pubDate><guid isPermaLink="false">Created Issue: StreamReader.Peek() misses last character [2009] 20130510074202P</guid></item><item><title>Commented Issue: VS2012 deploy and code stepping is very slow [2004]</title><link>http://netmf.codeplex.com/workitem/2004</link><description>Upgrading from VS2010 to VS2012, we noticed that deploying is very slow, which can be worked around but then stepping in code is very slow as well.&lt;br /&gt;&lt;br /&gt;First, we thought it maybe the device but it is very slow even in the emulator. This machine we tested, is i7 processor with 12MB of RAM. This also seem the case for many who have reported on our forums.&lt;br /&gt;&lt;br /&gt;Maybe votes and replies will show us if other users are or aren&amp;#39;t noticing this behavior.&lt;br /&gt;&lt;br /&gt;Please revisit debugging to see what can be done to speed up the debugging features. We are ready to run any tests and provide any help as necessary.&lt;br /&gt;&lt;br /&gt;Thanks&lt;br /&gt;&lt;br /&gt;Gus - GHI electronics&lt;br /&gt;Comments: ** Comment from web user: WeegieBoy ** &lt;p&gt;Using Windows 7 64 bit and VS2012 Express for NETMF and slow here too.&lt;/p&gt;</description><author>WeegieBoy</author><pubDate>Wed, 08 May 2013 17:03:52 GMT</pubDate><guid isPermaLink="false">Commented Issue: VS2012 deploy and code stepping is very slow [2004] 20130508050352P</guid></item><item><title>Commented Issue: XmlReader discrepancy between NETMF and full framework [2007]</title><link>http://netmf.codeplex.com/workitem/2007</link><description>There is a discrepancy in XmlReader from NETMF and Full .NET. I know both have a different code base but maybe it&amp;#39;s convinient to maintain the same functionality.&lt;br /&gt;&lt;br /&gt;The following is going different&amp;#58;&lt;br /&gt;&lt;br /&gt;The xml&amp;#58;&lt;br /&gt;&amp;#60;request&amp;#62;&amp;#60;parameters &amp;#47;&amp;#62;&amp;#60;name&amp;#62;yummo&amp;#60;&amp;#47;name&amp;#62;&amp;#60;&amp;#47;request&amp;#62;&lt;br /&gt;&lt;br /&gt;It&amp;#39;s going different on the element &amp;#39;parameters&amp;#39;. In the full framework the reader iterates on startelement and endelement where NETMF only iterates on startelement and the next read is on startelement of the element &amp;#39;name&amp;#39;.&lt;br /&gt;&lt;br /&gt;Framework versions i use&amp;#58;&lt;br /&gt;&amp;#42; Micro framework v4.2&lt;br /&gt;&amp;#42; Net Framework v4.0&lt;br /&gt;Comments: ** Comment from web user: yummolambert ** &lt;p&gt;After some researching i noticed the 'IsEmptyElement' property on XmlReader instance. Which didn't give a true on the normal framework but it does on NETMF. With this the situation is clear and all works like it should.&lt;/p&gt;&lt;p&gt;This can be closed. Thank you.&lt;/p&gt;</description><author>yummolambert</author><pubDate>Wed, 08 May 2013 11:31:46 GMT</pubDate><guid isPermaLink="false">Commented Issue: XmlReader discrepancy between NETMF and full framework [2007] 20130508113146A</guid></item><item><title>Created Issue: XmlReader discrepancy between NETMF and full framework [2007]</title><link>http://netmf.codeplex.com/workitem/2007</link><description>There is a discrepancy in XmlReader from NETMF and Full .NET. I know both have a different code base but maybe it&amp;#39;s convinient to maintain the same functionality.&lt;br /&gt;&lt;br /&gt;The following is going different&amp;#58;&lt;br /&gt;&lt;br /&gt;The xml&amp;#58;&lt;br /&gt;&amp;#60;request&amp;#62;&amp;#60;parameters &amp;#47;&amp;#62;&amp;#60;name&amp;#62;yummo&amp;#60;&amp;#47;name&amp;#62;&amp;#60;&amp;#47;request&amp;#62;&lt;br /&gt;&lt;br /&gt;It&amp;#39;s going different on the element &amp;#39;parameters&amp;#39;. In the full framework the reader iterates on startelement and endelement where NETMF only iterates on startelement and the next read is on startelement of the element &amp;#39;name&amp;#39;.&lt;br /&gt;&lt;br /&gt;Framework versions i use&amp;#58;&lt;br /&gt;&amp;#42; Micro framework v4.2&lt;br /&gt;&amp;#42; Net Framework v4.0&lt;br /&gt;</description><author>yummolambert</author><pubDate>Wed, 08 May 2013 09:02:24 GMT</pubDate><guid isPermaLink="false">Created Issue: XmlReader discrepancy between NETMF and full framework [2007] 20130508090224A</guid></item><item><title>Commented Issue: HTTP Client possible memory leak when using HTTPS [2005]</title><link>http://netmf.codeplex.com/workitem/2005</link><description>While testing a NetMF V4.2 application which connected to the Azure Service bus I found that after a while it ran out of memory and crashed. After some digging I found that each HTTPS request appeared to leak roughly 45K&amp;#40;forcing a GC appeared to make little or no difference&amp;#41;. Basically the BINARY_BLOB_HEAD value increases until the application dies.&lt;br /&gt;&lt;br /&gt;I only have one NetMF device which can do HTTPS so I wasn&amp;#39;t able to repro on another platform. The problem occurred over both &amp;#91;wireless&amp;#93;&amp;#40;http&amp;#58;&amp;#47;&amp;#47;http&amp;#58;&amp;#47;&amp;#47;www.ghielectronics.com&amp;#47;catalog&amp;#47;product&amp;#47;282&amp;#41; &amp;#38; &amp;#91;wired&amp;#93;&amp;#40;http&amp;#58;&amp;#47;&amp;#47;http&amp;#58;&amp;#47;&amp;#47;www.ghielectronics.com&amp;#47;catalog&amp;#47;product&amp;#47;284&amp;#41; connections  The attached demo application runs on a Fez Spider V4.2 &lt;br /&gt;&lt;br /&gt;Noted down free memory for 10 requests&lt;br /&gt;&lt;br /&gt;HTTPS &lt;br /&gt;7120164 bytes&lt;br /&gt;7074420&lt;br /&gt;7029252&lt;br /&gt;6984036&lt;br /&gt;6938952&lt;br /&gt;6893736&lt;br /&gt;6848520&lt;br /&gt;6803304&lt;br /&gt;6758088&lt;br /&gt;6712740&lt;br /&gt;&lt;br /&gt;HTTP&lt;br /&gt;7165980 bytes&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167708&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;&lt;br /&gt;HTTPS Memory info &amp;#8211; Start&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 3084 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 14352 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 1512 bytes&lt;br /&gt;Type 13 &amp;#40;SZARRAY &amp;#41;&amp;#58; 7860 bytes&lt;br /&gt;Type 03 &amp;#40;U1 &amp;#41;&amp;#58; 3192 bytes&lt;br /&gt;Type 04 &amp;#40;CHAR &amp;#41;&amp;#58; 852 bytes&lt;br /&gt;Type 07 &amp;#40;I4 &amp;#41;&amp;#58; 1044 bytes&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 2616 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 84 bytes&lt;br /&gt;Type 15 &amp;#40;FREEBLOCK &amp;#41;&amp;#58; 7118664 bytes&lt;br /&gt;Type 16 &amp;#40;CACHEDBLOCK &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 17 &amp;#40;ASSEMBLY &amp;#41;&amp;#58; 32688 bytes&lt;br /&gt;Type 18 &amp;#40;WEAKCLASS &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 19 &amp;#40;REFLECTION &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 1B &amp;#40;DELEGATE_HEAD &amp;#41;&amp;#58; 864 bytes&lt;br /&gt;Type 1D &amp;#40;OBJECT_TO_EVENT &amp;#41;&amp;#58; 240 bytes&lt;br /&gt;Type 1E &amp;#40;BINARY_BLOB_HEAD &amp;#41;&amp;#58; 152496 bytes&lt;br /&gt;Type 1F &amp;#40;THREAD &amp;#41;&amp;#58; 1536 bytes&lt;br /&gt;Type 20 &amp;#40;SUBTHREAD &amp;#41;&amp;#58; 144 bytes&lt;br /&gt;Type 21 &amp;#40;STACK_FRAME &amp;#41;&amp;#58; 1632 bytes&lt;br /&gt;Type 22 &amp;#40;TIMER_HEAD &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 27 &amp;#40;FINALIZER_HEAD &amp;#41;&amp;#58; 144 bytes&lt;br /&gt;Type 31 &amp;#40;IO_PORT &amp;#41;&amp;#58; 108 bytes&lt;br /&gt;Type 34 &amp;#40;APPDOMAIN_HEAD &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 36 &amp;#40;APPDOMAIN_ASSEMBLY &amp;#41;&amp;#58; 3552 bytes&lt;br /&gt;&lt;br /&gt;HTTPS Memory info &amp;#8211; Finish&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 3084 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 14364 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 1512 bytes&lt;br /&gt;Type 13 &amp;#40;SZARRAY &amp;#41;&amp;#58; 7860 bytes&lt;br /&gt;Type 03 &amp;#40;U1 &amp;#41;&amp;#58; 3192 bytes&lt;br /&gt;Type 04 &amp;#40;CHAR &amp;#41;&amp;#58; 852 bytes&lt;br /&gt;Type 07 &amp;#40;I4 &amp;#41;&amp;#58; 1044 bytes&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 2616 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 84 bytes&lt;br /&gt;Type 15 &amp;#40;FREEBLOCK &amp;#41;&amp;#58; 6711372 bytes&lt;br /&gt;Type 16 &amp;#40;CACHEDBLOCK &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 17 &amp;#40;ASSEMBLY &amp;#41;&amp;#58; 32688 bytes&lt;br /&gt;Type 18 &amp;#40;WEAKCLASS &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 19 &amp;#40;REFLECTION &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 1B &amp;#40;DELEGATE_HEAD &amp;#41;&amp;#58; 828 bytes&lt;br /&gt;Type 1D &amp;#40;OBJECT_TO_EVENT &amp;#41;&amp;#58; 240 bytes&lt;br /&gt;Type 1E &amp;#40;BINARY_BLOB_HEAD &amp;#41;&amp;#58; 559476 bytes&lt;br /&gt;Type 1F &amp;#40;THREAD &amp;#41;&amp;#58; 1920 bytes&lt;br /&gt;Type 20 &amp;#40;SUBTHREAD &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 21 &amp;#40;STACK_FRAME &amp;#41;&amp;#58; 1632 bytes&lt;br /&gt;Type 22 &amp;#40;TIMER_HEAD &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 27 &amp;#40;FINALIZER_HEAD &amp;#41;&amp;#58; 168 bytes&lt;br /&gt;Type 31 &amp;#40;IO_PORT &amp;#41;&amp;#58; 108 bytes&lt;br /&gt;Type 34 &amp;#40;APPDOMAIN_HEAD &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 36 &amp;#40;APPDOMAIN_ASSEMBLY &amp;#41;&amp;#58; 3552 bytes&lt;br /&gt;Comments: ** Comment from web user: BrynL ** &lt;p&gt;&lt;br&gt;Some logging info which maybe helpful&lt;/p&gt;&lt;p&gt;GC: performing heap compaction...&lt;br&gt;Err: 20, 166, 65, C:\MicroFrameworkPK_v4_2\DeviceCode\ghi\pal\OpenSSL\OpenSSL_1_0_0\ssl\ssl_ciph.cpp (1313)&lt;br&gt;Err: 20, 169, 161, C:\MicroFrameworkPK_v4_2\DeviceCode\ghi\pal\OpenSSL\OpenSSL_1_0_0\ssl\ssl_lib.cpp (1604)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><author>BrynL</author><pubDate>Tue, 07 May 2013 08:52:05 GMT</pubDate><guid isPermaLink="false">Commented Issue: HTTP Client possible memory leak when using HTTPS [2005] 20130507085205A</guid></item><item><title>Commented Issue: HTTP Client possible memory leak when using HTTPS [2005]</title><link>http://netmf.codeplex.com/workitem/2005</link><description>While testing a NetMF V4.2 application which connected to the Azure Service bus I found that after a while it ran out of memory and crashed. After some digging I found that each HTTPS request appeared to leak roughly 45K&amp;#40;forcing a GC appeared to make little or no difference&amp;#41;. Basically the BINARY_BLOB_HEAD value increases until the application dies.&lt;br /&gt;&lt;br /&gt;I only have one NetMF device which can do HTTPS so I wasn&amp;#39;t able to repro on another platform. The problem occurred over both &amp;#91;wireless&amp;#93;&amp;#40;http&amp;#58;&amp;#47;&amp;#47;http&amp;#58;&amp;#47;&amp;#47;www.ghielectronics.com&amp;#47;catalog&amp;#47;product&amp;#47;282&amp;#41; &amp;#38; &amp;#91;wired&amp;#93;&amp;#40;http&amp;#58;&amp;#47;&amp;#47;http&amp;#58;&amp;#47;&amp;#47;www.ghielectronics.com&amp;#47;catalog&amp;#47;product&amp;#47;284&amp;#41; connections  The attached demo application runs on a Fez Spider V4.2 &lt;br /&gt;&lt;br /&gt;Noted down free memory for 10 requests&lt;br /&gt;&lt;br /&gt;HTTPS &lt;br /&gt;7120164 bytes&lt;br /&gt;7074420&lt;br /&gt;7029252&lt;br /&gt;6984036&lt;br /&gt;6938952&lt;br /&gt;6893736&lt;br /&gt;6848520&lt;br /&gt;6803304&lt;br /&gt;6758088&lt;br /&gt;6712740&lt;br /&gt;&lt;br /&gt;HTTP&lt;br /&gt;7165980 bytes&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167708&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;&lt;br /&gt;HTTPS Memory info &amp;#8211; Start&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 3084 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 14352 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 1512 bytes&lt;br /&gt;Type 13 &amp;#40;SZARRAY &amp;#41;&amp;#58; 7860 bytes&lt;br /&gt;Type 03 &amp;#40;U1 &amp;#41;&amp;#58; 3192 bytes&lt;br /&gt;Type 04 &amp;#40;CHAR &amp;#41;&amp;#58; 852 bytes&lt;br /&gt;Type 07 &amp;#40;I4 &amp;#41;&amp;#58; 1044 bytes&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 2616 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 84 bytes&lt;br /&gt;Type 15 &amp;#40;FREEBLOCK &amp;#41;&amp;#58; 7118664 bytes&lt;br /&gt;Type 16 &amp;#40;CACHEDBLOCK &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 17 &amp;#40;ASSEMBLY &amp;#41;&amp;#58; 32688 bytes&lt;br /&gt;Type 18 &amp;#40;WEAKCLASS &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 19 &amp;#40;REFLECTION &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 1B &amp;#40;DELEGATE_HEAD &amp;#41;&amp;#58; 864 bytes&lt;br /&gt;Type 1D &amp;#40;OBJECT_TO_EVENT &amp;#41;&amp;#58; 240 bytes&lt;br /&gt;Type 1E &amp;#40;BINARY_BLOB_HEAD &amp;#41;&amp;#58; 152496 bytes&lt;br /&gt;Type 1F &amp;#40;THREAD &amp;#41;&amp;#58; 1536 bytes&lt;br /&gt;Type 20 &amp;#40;SUBTHREAD &amp;#41;&amp;#58; 144 bytes&lt;br /&gt;Type 21 &amp;#40;STACK_FRAME &amp;#41;&amp;#58; 1632 bytes&lt;br /&gt;Type 22 &amp;#40;TIMER_HEAD &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 27 &amp;#40;FINALIZER_HEAD &amp;#41;&amp;#58; 144 bytes&lt;br /&gt;Type 31 &amp;#40;IO_PORT &amp;#41;&amp;#58; 108 bytes&lt;br /&gt;Type 34 &amp;#40;APPDOMAIN_HEAD &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 36 &amp;#40;APPDOMAIN_ASSEMBLY &amp;#41;&amp;#58; 3552 bytes&lt;br /&gt;&lt;br /&gt;HTTPS Memory info &amp;#8211; Finish&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 3084 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 14364 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 1512 bytes&lt;br /&gt;Type 13 &amp;#40;SZARRAY &amp;#41;&amp;#58; 7860 bytes&lt;br /&gt;Type 03 &amp;#40;U1 &amp;#41;&amp;#58; 3192 bytes&lt;br /&gt;Type 04 &amp;#40;CHAR &amp;#41;&amp;#58; 852 bytes&lt;br /&gt;Type 07 &amp;#40;I4 &amp;#41;&amp;#58; 1044 bytes&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 2616 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 84 bytes&lt;br /&gt;Type 15 &amp;#40;FREEBLOCK &amp;#41;&amp;#58; 6711372 bytes&lt;br /&gt;Type 16 &amp;#40;CACHEDBLOCK &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 17 &amp;#40;ASSEMBLY &amp;#41;&amp;#58; 32688 bytes&lt;br /&gt;Type 18 &amp;#40;WEAKCLASS &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 19 &amp;#40;REFLECTION &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 1B &amp;#40;DELEGATE_HEAD &amp;#41;&amp;#58; 828 bytes&lt;br /&gt;Type 1D &amp;#40;OBJECT_TO_EVENT &amp;#41;&amp;#58; 240 bytes&lt;br /&gt;Type 1E &amp;#40;BINARY_BLOB_HEAD &amp;#41;&amp;#58; 559476 bytes&lt;br /&gt;Type 1F &amp;#40;THREAD &amp;#41;&amp;#58; 1920 bytes&lt;br /&gt;Type 20 &amp;#40;SUBTHREAD &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 21 &amp;#40;STACK_FRAME &amp;#41;&amp;#58; 1632 bytes&lt;br /&gt;Type 22 &amp;#40;TIMER_HEAD &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 27 &amp;#40;FINALIZER_HEAD &amp;#41;&amp;#58; 168 bytes&lt;br /&gt;Type 31 &amp;#40;IO_PORT &amp;#41;&amp;#58; 108 bytes&lt;br /&gt;Type 34 &amp;#40;APPDOMAIN_HEAD &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 36 &amp;#40;APPDOMAIN_ASSEMBLY &amp;#41;&amp;#58; 3552 bytes&lt;br /&gt;Comments: ** Comment from web user: BrynL ** &lt;p&gt;Hi Gus,&lt;/p&gt;&lt;p&gt;With HTTP there didn't appear to be a memory leak. I initially thought it might have been a problem with tidying up a IO stream or similar in my code but I built really cut back sample which still had the problem&lt;/p&gt;&lt;p&gt;I tried different ways of loading the certificate, plus forcing GCs etc. but it didn't seem to make any difference. &lt;/p&gt;&lt;p&gt;I used Redgate Reflector to drill down into the system.HTTP assembly but hit what looked like native SSL code.&lt;/p&gt;&lt;p&gt;I have got more detail on my [blog](http://http://blog.devmobile.co.nz/2013/03/04/netmf-http-client-possible-memory-leak/) if you're interested. &lt;/p&gt;&lt;p&gt;Bryn&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><author>BrynL</author><pubDate>Sat, 04 May 2013 10:17:51 GMT</pubDate><guid isPermaLink="false">Commented Issue: HTTP Client possible memory leak when using HTTPS [2005] 20130504101751A</guid></item><item><title>Commented Issue: HTTP Client possible memory leak when using HTTPS [2005]</title><link>http://netmf.codeplex.com/workitem/2005</link><description>While testing a NetMF V4.2 application which connected to the Azure Service bus I found that after a while it ran out of memory and crashed. After some digging I found that each HTTPS request appeared to leak roughly 45K&amp;#40;forcing a GC appeared to make little or no difference&amp;#41;. Basically the BINARY_BLOB_HEAD value increases until the application dies.&lt;br /&gt;&lt;br /&gt;I only have one NetMF device which can do HTTPS so I wasn&amp;#39;t able to repro on another platform. The problem occurred over both &amp;#91;wireless&amp;#93;&amp;#40;http&amp;#58;&amp;#47;&amp;#47;http&amp;#58;&amp;#47;&amp;#47;www.ghielectronics.com&amp;#47;catalog&amp;#47;product&amp;#47;282&amp;#41; &amp;#38; &amp;#91;wired&amp;#93;&amp;#40;http&amp;#58;&amp;#47;&amp;#47;http&amp;#58;&amp;#47;&amp;#47;www.ghielectronics.com&amp;#47;catalog&amp;#47;product&amp;#47;284&amp;#41; connections  The attached demo application runs on a Fez Spider V4.2 &lt;br /&gt;&lt;br /&gt;Noted down free memory for 10 requests&lt;br /&gt;&lt;br /&gt;HTTPS &lt;br /&gt;7120164 bytes&lt;br /&gt;7074420&lt;br /&gt;7029252&lt;br /&gt;6984036&lt;br /&gt;6938952&lt;br /&gt;6893736&lt;br /&gt;6848520&lt;br /&gt;6803304&lt;br /&gt;6758088&lt;br /&gt;6712740&lt;br /&gt;&lt;br /&gt;HTTP&lt;br /&gt;7165980 bytes&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167708&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;&lt;br /&gt;HTTPS Memory info &amp;#8211; Start&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 3084 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 14352 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 1512 bytes&lt;br /&gt;Type 13 &amp;#40;SZARRAY &amp;#41;&amp;#58; 7860 bytes&lt;br /&gt;Type 03 &amp;#40;U1 &amp;#41;&amp;#58; 3192 bytes&lt;br /&gt;Type 04 &amp;#40;CHAR &amp;#41;&amp;#58; 852 bytes&lt;br /&gt;Type 07 &amp;#40;I4 &amp;#41;&amp;#58; 1044 bytes&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 2616 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 84 bytes&lt;br /&gt;Type 15 &amp;#40;FREEBLOCK &amp;#41;&amp;#58; 7118664 bytes&lt;br /&gt;Type 16 &amp;#40;CACHEDBLOCK &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 17 &amp;#40;ASSEMBLY &amp;#41;&amp;#58; 32688 bytes&lt;br /&gt;Type 18 &amp;#40;WEAKCLASS &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 19 &amp;#40;REFLECTION &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 1B &amp;#40;DELEGATE_HEAD &amp;#41;&amp;#58; 864 bytes&lt;br /&gt;Type 1D &amp;#40;OBJECT_TO_EVENT &amp;#41;&amp;#58; 240 bytes&lt;br /&gt;Type 1E &amp;#40;BINARY_BLOB_HEAD &amp;#41;&amp;#58; 152496 bytes&lt;br /&gt;Type 1F &amp;#40;THREAD &amp;#41;&amp;#58; 1536 bytes&lt;br /&gt;Type 20 &amp;#40;SUBTHREAD &amp;#41;&amp;#58; 144 bytes&lt;br /&gt;Type 21 &amp;#40;STACK_FRAME &amp;#41;&amp;#58; 1632 bytes&lt;br /&gt;Type 22 &amp;#40;TIMER_HEAD &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 27 &amp;#40;FINALIZER_HEAD &amp;#41;&amp;#58; 144 bytes&lt;br /&gt;Type 31 &amp;#40;IO_PORT &amp;#41;&amp;#58; 108 bytes&lt;br /&gt;Type 34 &amp;#40;APPDOMAIN_HEAD &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 36 &amp;#40;APPDOMAIN_ASSEMBLY &amp;#41;&amp;#58; 3552 bytes&lt;br /&gt;&lt;br /&gt;HTTPS Memory info &amp;#8211; Finish&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 3084 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 14364 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 1512 bytes&lt;br /&gt;Type 13 &amp;#40;SZARRAY &amp;#41;&amp;#58; 7860 bytes&lt;br /&gt;Type 03 &amp;#40;U1 &amp;#41;&amp;#58; 3192 bytes&lt;br /&gt;Type 04 &amp;#40;CHAR &amp;#41;&amp;#58; 852 bytes&lt;br /&gt;Type 07 &amp;#40;I4 &amp;#41;&amp;#58; 1044 bytes&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 2616 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 84 bytes&lt;br /&gt;Type 15 &amp;#40;FREEBLOCK &amp;#41;&amp;#58; 6711372 bytes&lt;br /&gt;Type 16 &amp;#40;CACHEDBLOCK &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 17 &amp;#40;ASSEMBLY &amp;#41;&amp;#58; 32688 bytes&lt;br /&gt;Type 18 &amp;#40;WEAKCLASS &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 19 &amp;#40;REFLECTION &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 1B &amp;#40;DELEGATE_HEAD &amp;#41;&amp;#58; 828 bytes&lt;br /&gt;Type 1D &amp;#40;OBJECT_TO_EVENT &amp;#41;&amp;#58; 240 bytes&lt;br /&gt;Type 1E &amp;#40;BINARY_BLOB_HEAD &amp;#41;&amp;#58; 559476 bytes&lt;br /&gt;Type 1F &amp;#40;THREAD &amp;#41;&amp;#58; 1920 bytes&lt;br /&gt;Type 20 &amp;#40;SUBTHREAD &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 21 &amp;#40;STACK_FRAME &amp;#41;&amp;#58; 1632 bytes&lt;br /&gt;Type 22 &amp;#40;TIMER_HEAD &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 27 &amp;#40;FINALIZER_HEAD &amp;#41;&amp;#58; 168 bytes&lt;br /&gt;Type 31 &amp;#40;IO_PORT &amp;#41;&amp;#58; 108 bytes&lt;br /&gt;Type 34 &amp;#40;APPDOMAIN_HEAD &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 36 &amp;#40;APPDOMAIN_ASSEMBLY &amp;#41;&amp;#58; 3552 bytes&lt;br /&gt;Comments: ** Comment from web user: gus_ghielec ** &lt;p&gt;Is it possible to run the same but without SSL? Maybe we can narrow it to the network not SSL?&lt;/p&gt;</description><author>gus_ghielec</author><pubDate>Fri, 03 May 2013 23:11:22 GMT</pubDate><guid isPermaLink="false">Commented Issue: HTTP Client possible memory leak when using HTTPS [2005] 20130503111122P</guid></item><item><title>Created Issue: HTTP Client possible memory leak when using HTTPS [2005]</title><link>http://netmf.codeplex.com/workitem/2005</link><description>While testing a NetMF V4.2 application which connected to the Azure Service bus I found that after a while it ran out of memory and crashed. After some digging I found that each HTTPS request appeared to leak roughly 45K&amp;#40;forcing a GC appeared to make little or no difference&amp;#41;. Basically the BINARY_BLOB_HEAD value increases until the application dies.&lt;br /&gt;&lt;br /&gt;I only have one NetMF device which can do HTTPS so I wasn&amp;#39;t able to repro on another platform. The problem occurred over both &amp;#91;wireless&amp;#93;&amp;#40;http&amp;#58;&amp;#47;&amp;#47;http&amp;#58;&amp;#47;&amp;#47;www.ghielectronics.com&amp;#47;catalog&amp;#47;product&amp;#47;282&amp;#41; &amp;#38; &amp;#91;wired&amp;#93;&amp;#40;http&amp;#58;&amp;#47;&amp;#47;http&amp;#58;&amp;#47;&amp;#47;www.ghielectronics.com&amp;#47;catalog&amp;#47;product&amp;#47;284&amp;#41; connections  The attached demo application runs on a Fez Spider V4.2 &lt;br /&gt;&lt;br /&gt;Noted down free memory for 10 requests&lt;br /&gt;&lt;br /&gt;HTTPS &lt;br /&gt;7120164 bytes&lt;br /&gt;7074420&lt;br /&gt;7029252&lt;br /&gt;6984036&lt;br /&gt;6938952&lt;br /&gt;6893736&lt;br /&gt;6848520&lt;br /&gt;6803304&lt;br /&gt;6758088&lt;br /&gt;6712740&lt;br /&gt;&lt;br /&gt;HTTP&lt;br /&gt;7165980 bytes&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;7167708&lt;br /&gt;7167840&lt;br /&gt;7167840&lt;br /&gt;&lt;br /&gt;HTTPS Memory info &amp;#8211; Start&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 3084 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 14352 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 1512 bytes&lt;br /&gt;Type 13 &amp;#40;SZARRAY &amp;#41;&amp;#58; 7860 bytes&lt;br /&gt;Type 03 &amp;#40;U1 &amp;#41;&amp;#58; 3192 bytes&lt;br /&gt;Type 04 &amp;#40;CHAR &amp;#41;&amp;#58; 852 bytes&lt;br /&gt;Type 07 &amp;#40;I4 &amp;#41;&amp;#58; 1044 bytes&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 2616 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 84 bytes&lt;br /&gt;Type 15 &amp;#40;FREEBLOCK &amp;#41;&amp;#58; 7118664 bytes&lt;br /&gt;Type 16 &amp;#40;CACHEDBLOCK &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 17 &amp;#40;ASSEMBLY &amp;#41;&amp;#58; 32688 bytes&lt;br /&gt;Type 18 &amp;#40;WEAKCLASS &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 19 &amp;#40;REFLECTION &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 1B &amp;#40;DELEGATE_HEAD &amp;#41;&amp;#58; 864 bytes&lt;br /&gt;Type 1D &amp;#40;OBJECT_TO_EVENT &amp;#41;&amp;#58; 240 bytes&lt;br /&gt;Type 1E &amp;#40;BINARY_BLOB_HEAD &amp;#41;&amp;#58; 152496 bytes&lt;br /&gt;Type 1F &amp;#40;THREAD &amp;#41;&amp;#58; 1536 bytes&lt;br /&gt;Type 20 &amp;#40;SUBTHREAD &amp;#41;&amp;#58; 144 bytes&lt;br /&gt;Type 21 &amp;#40;STACK_FRAME &amp;#41;&amp;#58; 1632 bytes&lt;br /&gt;Type 22 &amp;#40;TIMER_HEAD &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 27 &amp;#40;FINALIZER_HEAD &amp;#41;&amp;#58; 144 bytes&lt;br /&gt;Type 31 &amp;#40;IO_PORT &amp;#41;&amp;#58; 108 bytes&lt;br /&gt;Type 34 &amp;#40;APPDOMAIN_HEAD &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 36 &amp;#40;APPDOMAIN_ASSEMBLY &amp;#41;&amp;#58; 3552 bytes&lt;br /&gt;&lt;br /&gt;HTTPS Memory info &amp;#8211; Finish&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 3084 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 14364 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 1512 bytes&lt;br /&gt;Type 13 &amp;#40;SZARRAY &amp;#41;&amp;#58; 7860 bytes&lt;br /&gt;Type 03 &amp;#40;U1 &amp;#41;&amp;#58; 3192 bytes&lt;br /&gt;Type 04 &amp;#40;CHAR &amp;#41;&amp;#58; 852 bytes&lt;br /&gt;Type 07 &amp;#40;I4 &amp;#41;&amp;#58; 1044 bytes&lt;br /&gt;Type 0F &amp;#40;STRING &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 11 &amp;#40;CLASS &amp;#41;&amp;#58; 2616 bytes&lt;br /&gt;Type 12 &amp;#40;VALUETYPE &amp;#41;&amp;#58; 84 bytes&lt;br /&gt;Type 15 &amp;#40;FREEBLOCK &amp;#41;&amp;#58; 6711372 bytes&lt;br /&gt;Type 16 &amp;#40;CACHEDBLOCK &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 17 &amp;#40;ASSEMBLY &amp;#41;&amp;#58; 32688 bytes&lt;br /&gt;Type 18 &amp;#40;WEAKCLASS &amp;#41;&amp;#58; 96 bytes&lt;br /&gt;Type 19 &amp;#40;REFLECTION &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 1B &amp;#40;DELEGATE_HEAD &amp;#41;&amp;#58; 828 bytes&lt;br /&gt;Type 1D &amp;#40;OBJECT_TO_EVENT &amp;#41;&amp;#58; 240 bytes&lt;br /&gt;Type 1E &amp;#40;BINARY_BLOB_HEAD &amp;#41;&amp;#58; 559476 bytes&lt;br /&gt;Type 1F &amp;#40;THREAD &amp;#41;&amp;#58; 1920 bytes&lt;br /&gt;Type 20 &amp;#40;SUBTHREAD &amp;#41;&amp;#58; 192 bytes&lt;br /&gt;Type 21 &amp;#40;STACK_FRAME &amp;#41;&amp;#58; 1632 bytes&lt;br /&gt;Type 22 &amp;#40;TIMER_HEAD &amp;#41;&amp;#58; 216 bytes&lt;br /&gt;Type 27 &amp;#40;FINALIZER_HEAD &amp;#41;&amp;#58; 168 bytes&lt;br /&gt;Type 31 &amp;#40;IO_PORT &amp;#41;&amp;#58; 108 bytes&lt;br /&gt;Type 34 &amp;#40;APPDOMAIN_HEAD &amp;#41;&amp;#58; 72 bytes&lt;br /&gt;Type 36 &amp;#40;APPDOMAIN_ASSEMBLY &amp;#41;&amp;#58; 3552 bytes&lt;br /&gt;</description><author>BrynL</author><pubDate>Fri, 03 May 2013 03:53:54 GMT</pubDate><guid isPermaLink="false">Created Issue: HTTP Client possible memory leak when using HTTPS [2005] 20130503035354A</guid></item></channel></rss>