﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>StrataFrame Forum » Updates and Information » Developer Blog Topics  » Design-time issues with Intellisense and APPCRASH using Visual Studio 2008 and VB.NET</title><generator>InstantForum 2017-1 Final</generator><description>StrataFrame Forum</description><link>http://forum.strataframe.net/</link><webMaster>StrataFrame Forum</webMaster><lastBuildDate>Tue, 19 May 2026 14:07:22 GMT</lastBuildDate><ttl>20</ttl><item><title>Design-time issues with Intellisense and APPCRASH using Visual Studio 2008 and VB.NET</title><link>http://forum.strataframe.net/FindPost14420.aspx</link><description>We have run into some issues with Visual Studio, VB.NET, and large projects recently and I thought I would just share this information with you so that you can take some action on your side.&amp;nbsp; The issue that we ran into is that the larger our VB.NET projects became, the slower the response in the .NET editor as well as Intellisense became.&amp;nbsp; Not only that, Visual Studio would just flat out crash...and many times not save your work.&amp;nbsp; This became VERY frustrating...and I am sure that we were not alone :D&lt;/P&gt;&lt;P&gt;Due to our high frustration level, we finally contacted Microsoft and worked through the issue.&amp;nbsp; We were right...we weren't the only people with this issue as they were already in the phase of testing a hotfix.&amp;nbsp; Their initial resolution was to just disable the XML documentation...which just flat out wasn't going to cut it.&amp;nbsp; Though when you did this, the IDE was MUCH faster and the crashes subsided.&amp;nbsp; Today we got a hotfix from Microsoft and so far so good.&amp;nbsp; The Intellisense is much faster, we have our XML docs back, and hopefully this will keep the IDE from dying!&lt;/P&gt;&lt;P&gt;Here was the KB article that was referenced prior to this fix: &lt;A href="http://support.microsoft.com/?id=946452"&gt;http://support.microsoft.com/?id=946452&lt;/A&gt;&amp;nbsp;.&amp;nbsp; Even though this article doesn't yet mention a hotfix, one does exist.&amp;nbsp; Just place a call to MS support, tell them your issue, and you should be able to get this fix.</description><pubDate>Mon, 18 Feb 2008 15:09:58 GMT</pubDate><dc:creator>Trent L. Taylor</dc:creator></item></channel></rss>