<?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>Another Virtual Memory Tip</title><link>http://blogs.msdn.com/b/bharry/archive/2009/12/09/another-virtual-memory-tip.aspx</link><description>In truth, this won’t apply to very many of you and it is with some trepidation that I share it.&amp;#160; The last thing in the world I want is for everyone to blindly follow it.&amp;#160; This, like in many things in software, involves trade-offs that you need</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Another Virtual Memory Tip</title><link>http://blogs.msdn.com/b/bharry/archive/2009/12/09/another-virtual-memory-tip.aspx#9935187</link><pubDate>Thu, 10 Dec 2009 16:30:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9935187</guid><dc:creator>Brian Harry MS</dc:creator><description>&lt;p&gt;I'll look into it.&lt;/p&gt;
&lt;p&gt;Brian&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9935187" width="1" height="1"&gt;</description></item><item><title>re: Another Virtual Memory Tip</title><link>http://blogs.msdn.com/b/bharry/archive/2009/12/09/another-virtual-memory-tip.aspx#9935184</link><pubDate>Thu, 10 Dec 2009 16:24:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9935184</guid><dc:creator>Steve Nuchia</dc:creator><description>&lt;p&gt;Early in our Orcas adoption I set up a terminal server VM with it. &amp;nbsp;We found that it was entirely unusable by simultaneous users in different security contexts, even though you can open as many instances as you want in one session.&lt;/p&gt;
&lt;p&gt;I reported it and got no traction at the time. &amp;nbsp;But while you're working on the DLL partitioning and deployment issues may I suggest you include this scenario in the test plans?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9935184" width="1" height="1"&gt;</description></item><item><title>re: Another Virtual Memory Tip</title><link>http://blogs.msdn.com/b/bharry/archive/2009/12/09/another-virtual-memory-tip.aspx#9935063</link><pubDate>Thu, 10 Dec 2009 11:49:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9935063</guid><dc:creator>Brian Harry MS</dc:creator><description>&lt;p&gt;GT,&lt;/p&gt;
&lt;p&gt;We call that feature &amp;quot;Build Lab Compile&amp;quot;. &amp;nbsp;It's definitely something we would like to do and something we'll consider for future versions.&lt;/p&gt;
&lt;p&gt;Leon?,&lt;/p&gt;
&lt;p&gt;Here's a nice post by Mark Russinovich on memory and Windows:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.technet.com/markrussinovich/archive/2008/11/17/3155406.aspx"&gt;http://blogs.technet.com/markrussinovich/archive/2008/11/17/3155406.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Alex,&lt;/p&gt;
&lt;p&gt;Yeah, definitely on the backlog as a VS11 candidate. &amp;nbsp;On the other hand, we do still need to make sure we aren't being wasteful so the exercise to understand all of this is still good.&lt;/p&gt;
&lt;p&gt;Brian&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9935063" width="1" height="1"&gt;</description></item><item><title>re: Another Virtual Memory Tip</title><link>http://blogs.msdn.com/b/bharry/archive/2009/12/09/another-virtual-memory-tip.aspx#9935049</link><pubDate>Thu, 10 Dec 2009 10:36:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9935049</guid><dc:creator>Patrick Smacchia</dc:creator><description>&lt;p&gt;Very interesting insider info there, thanks for sharing.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9935049" width="1" height="1"&gt;</description></item><item><title>re: Another Virtual Memory Tip</title><link>http://blogs.msdn.com/b/bharry/archive/2009/12/09/another-virtual-memory-tip.aspx#9935000</link><pubDate>Thu, 10 Dec 2009 07:16:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9935000</guid><dc:creator>David Berg</dc:creator><description>&lt;p&gt;Alex, you can run VS on a 64 bit OS and get 4GB of address space. &amp;nbsp; This pretty much solves VM issues for most VS customers. &amp;nbsp;We just don't believe that all our customers with large projects are ready or able to move to 64 bit yet, so we need to keep supporting 32 bit and make sure we work well on it.&lt;/p&gt;
&lt;p&gt;David Berg - Developer Division Performance Engineering&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9935000" width="1" height="1"&gt;</description></item><item><title>re: Another Virtual Memory Tip</title><link>http://blogs.msdn.com/b/bharry/archive/2009/12/09/another-virtual-memory-tip.aspx#9934982</link><pubDate>Thu, 10 Dec 2009 06:13:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9934982</guid><dc:creator>Alex</dc:creator><description>&lt;p&gt;Maybe it is time VS went 64-bit app.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9934982" width="1" height="1"&gt;</description></item><item><title>re: Another Virtual Memory Tip</title><link>http://blogs.msdn.com/b/bharry/archive/2009/12/09/another-virtual-memory-tip.aspx#9934944</link><pubDate>Thu, 10 Dec 2009 03:20:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9934944</guid><dc:creator>youngdriversleonj</dc:creator><description>&lt;p&gt;This is a nice tip sir...but i want to learn more about this type of virtual memory tip, i'm a starter in this field. can u help thanks.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9934944" width="1" height="1"&gt;</description></item><item><title>re: Another Virtual Memory Tip</title><link>http://blogs.msdn.com/b/bharry/archive/2009/12/09/another-virtual-memory-tip.aspx#9934652</link><pubDate>Wed, 09 Dec 2009 16:49:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9934652</guid><dc:creator>GT</dc:creator><description>&lt;p&gt;It would be nice if the C# was directly compiled to native code bypassing the NGEN tool, this would have solved many performance issues, especially when you deploy a click once application on machines with limited user access where you cannot run NGEN.&lt;/p&gt;
&lt;p&gt;MSIL was a nice competitor to the Java byte code, but at this point, I personally just cannot see any reason for having to make hundreds of millions of computers all over the world to JIT the same MSIL over and over every day :-)&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9934652" width="1" height="1"&gt;</description></item></channel></rss>