<?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>Visual Studio 2008 Find Crashes on Windows XP 64 &amp; Windows 2003 Server</title><link>http://blogs.msdn.com/b/vseditor/archive/2008/02/15/visual-studio-2008-find-crashes-on-windows-xp-64-windows-2003-server.aspx</link><description>I know that quite a few people are running into an issue where any edition Visual Studio 2008 can crash when users open the find dialog if they are running on Windows XP 64-bit or Windows 2003 Server. There's a patch available for Microsoft Support. You</description><dc:language>en-CA</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Visual Studio 2008 Find Crashes on Windows XP 64 &amp; Windows 2003 Server</title><link>http://blogs.msdn.com/b/vseditor/archive/2008/02/15/visual-studio-2008-find-crashes-on-windows-xp-64-windows-2003-server.aspx#7775161</link><pubDate>Mon, 18 Feb 2008 18:23:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7775161</guid><dc:creator>Ami</dc:creator><description>&lt;p&gt;When VS 2008 SP1 is going to be released ?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7775161" width="1" height="1"&gt;</description></item><item><title>re: Visual Studio 2008 Find Crashes on Windows XP 64 &amp; Windows 2003 Server</title><link>http://blogs.msdn.com/b/vseditor/archive/2008/02/15/visual-studio-2008-find-crashes-on-windows-xp-64-windows-2003-server.aspx#7752527</link><pubDate>Sun, 17 Feb 2008 16:37:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7752527</guid><dc:creator>Julian</dc:creator><description>&lt;p&gt;This is a typically over-complicated solution to a problem. Instead of making your customers waste time calling up support, why don't you just allow them to download it and provide an email where you can contact them if you discover a problem with the patch. Especially for developer products, where you have can be reasonably certain that your customers are technically competent!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7752527" width="1" height="1"&gt;</description></item><item><title>BioSensorAB &amp;raquo; Visual Studio 2008 Find Crashes on Windows XP 64 &amp;amp; Windows 2003 Server</title><link>http://blogs.msdn.com/b/vseditor/archive/2008/02/15/visual-studio-2008-find-crashes-on-windows-xp-64-windows-2003-server.aspx#7726404</link><pubDate>Sat, 16 Feb 2008 04:42:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7726404</guid><dc:creator>BioSensorAB » Visual Studio 2008 Find Crashes on Windows XP 64 &amp; Windows 2003 Server</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.biosensorab.org/2008/02/15/visual-studio-2008-find-crashes-on-windows-xp-64-windows-2003-server/"&gt;http://www.biosensorab.org/2008/02/15/visual-studio-2008-find-crashes-on-windows-xp-64-windows-2003-server/&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7726404" width="1" height="1"&gt;</description></item></channel></rss>