VS2010 XAML Intellisense Failure by Kent Boogaart

We apologize for the inconvenience caused by this issue. We plan to make the fix available in the next Service Pack for Visual Studio 2010.

There are a few possible workarounds:
-    Ensure all xmlns definitions are valid and assemblies referenced also have valid xmlns definitions
-    Don’t open IntelliSense until the designer has loaded
-    Don’t leave IntelliSense open longer than 5 minutes

Thank you,
Visual Studio WPF and Silverlight Designer Team

Is there a hotfix?

I got this error when I try to add a property to a <Grid />. It happens anytime I am adding a property X to element <Y />

System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain. at Microsoft.Windows.Design.IXamlCompletion.get_Name() at MS.Internal.XamlLanguageService.XamlDeclarationsAdapter.GetName(Int32 index) at Microsoft.VisualStudio.Package.CompletionSet.OnCommit(String textSoFar, Int32 index, Int32 selected, UInt16 commitChar, String& completeWord) at Microsoft.VisualStudio.Editor.Implementation.ShimCompletion.TryCommit(Nullable`1 queryCommitChar, Boolean isSelected) at Microsoft.VisualStudio.Editor.Implementation.ShimCompletionController.TryCommit(Nullable`1 commitChar) at Microsoft.VisualStudio.Editor.Implementation.ShimCompletionController.PreProcessCommand(Guid& pguidCmdGroup, UInt32 nCmdID, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Editor.Implementation.IntellisenseCommandFilter.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Editor.Implementation.CommandFilterWrapper.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Editor.Implementation.CommandFilterWrapper.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Package.ViewFilter.InnerExec(Guid& guidCmdGroup, UInt32 nCmdId, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Package.ViewFilter.ExecCommand(Guid& guidCmdGroup, UInt32 nCmdId, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at MS.Internal.XamlLanguageService.VsXamlLanguageService.XamlViewFilter.ExecCommand(Guid& guidCmdGroup, UInt32 nCmdId, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Package.ViewFilter.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& guidCmdGroup, UInt32 nCmdId, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Editor.Implementation.CommandFilterWrapper.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Editor.Implementation.VsTextViewAdapter.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut) at Microsoft.VisualStudio.Editor.Implementation.VsKeyboardFilter.SendCommand(Guid cmdGroup, UInt32 cmdID, Object inParam) at Microsoft.VisualStudio.Editor.Implementation.VsKeyboardFilter.TextInput(TextCompositionEventArgs args) at Microsoft.VisualStudio.Text.Editor.Implementation.KeyProcessorDispatcher.<DispatchTextInputEvents>b__0(KeyProcessor p, TextCompositionEventArgs args) at Microsoft.VisualStudio.Text.Editor.Implementation.KeyProcessorDispatcher.<>c__DisplayClass1e`1.<Dispatch>b__1a() at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.CallExtensionPoint(Object errorSource, Action call)

This started happening after I reinstalled Windows 7, VS2010, et al. Other developers on my project with the same software installed do not have this problem with the XmlnsDefitions. Why does it work for some VS2010/SL4 installations but not mine?

Thanks to your feedback we were able to fix the issue for the next release of Visual Studio.

Thank you,
Visual Studio WPF and Silverlight Designer Team

Thank you for your feedback. We were able to reproduce the issue, and are investigating the cause. We apologize for any inconvenience this issue has caused.

Thank you,
Visual Studio WPF and Silverlight Designer Team

Thanks for reporting the issue.

In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with a dump file

You can get the dump file with the following steps:

****************************************************************
Note: Please zip the file and use "FeedbackID-575719" as prefix of the file name

****************************************************************

1. Download the Debugging Tools from Windows from
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx and install. Assume that you copy it to
“C:\Debuggers”.

2. Open a command line prompt. Close all unnecessary applications.

3. Try to reproduce the problem.

4. Before VS IDE crashes , execute the following command at the command line prompt:

cscript C:\Debuggers\adplus.vbs -crash -FullOnFirst -pn devenv.exe –o C:\Dump

Dump file will be generated at “C:\Dump” and it usually takes several hundred MB. Make sure that you have sufficient disk space.

5. After VS IDE crash, please go to the folder “C:\Dump”. There can be multiple .DMP files. If their size are huge, please add the first .DMP file sorted by the timestamp (e.g. the first .DMP file captured) to a zip and upload it to the workspace:

https://sftus.one.microsoft.com/choosetransfer.aspx?key=3742328a-8d23-46e0-921d-c0c454a3f6a8

Password is X5eRup%anJ

If we do not receive a response from you after 7-days , we will automatically close your issue. There is no obligation to respond -- at any time you may edit your issue via Connect and change the status to “Active.”

Thank you,
Microsoft Visual Studio Connect Support Team

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)