What’s This? No Intellisense for WPF’s Xaml View.
I swear that the Xaml view had intellisense at one point. What is going on? Well apparently there is a problem where the intellisense stops working after installing an SDK or MSDN. In my case I believe this occurred after installing the .NET 2.0 Framework SDK. Great news though, there is a fix thanks to Brett Kilty of Microsoft.
To fix this you need to set the Default string value to the path of your TextMgrP.dll for the key “HKEY_CLASSES_ROOT\CLSID\{73B7DC00-F498-4ABD-AB79-D07AFD52F395}\InProcServer32”.
Here are the steps I executed to fix this:
1) Opened regedit
2) Searched for ‘{73B7DC00-F498-4ABD-AB79-D07AFD52F395}’
3) Expanded the key and clicked InProcServer32
4) The Default string was empty so I set it to ‘C:\Program Files\Common Files\Microsoft Shared\MSEnv\TextMgrP.dll’
5) Restarted Visual Studio
6) Smiled
btw – I’m running Visual Studio Professional 2008.
Link to Brett’s Post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2840817&SiteID=1
It’s Official: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2892404&SiteID=1
Thanks Brett!
Tags: Intellisense, Visual Studio 2008, WPF, Xaml
You can comment below, or link to this permanent URL from your own site.
March 19, 2008 at 3:13 am
[...] to fix… Tom Krueger did a nice summary post about a problem that many are running into: "What’s This? No Intellisense for WPF’s Xaml View." He points to forum posts [...]
March 21, 2008 at 12:59 pm
[...] On trouve quelques échanges à ce sujet, comme celui-ci, mais c'est l'article de Tom Krueger qui m'a permis de contourner le problème. Thanks Tom ! Filed under: .NET, WPF, [...]
June 10, 2008 at 1:17 am
AWESOME!
Smiled too after restarting VS
October 30, 2008 at 5:11 am
Thanks a lot my friend, you are the man.
i found the key in this path
HKEY_CLASSES_ROOT\CLSID\{73B7DC00-F498-4ABD-AB79-D07AFD52F395}\
February 15, 2009 at 2:48 pm
Thanks a lot!!!
March 4, 2009 at 7:54 am
[...] What’s This? No Intellisense for WPF’s Xaml View. (Tom Krueger) [...]