Intellisense has stopped working in my project's Visual Studio 2008 solution. Note, I am opening the .xaml files with the Source Code (Text) Editor. I have tried the fixes mentioned in these posts (http://social.msdn.microsoft.com/Forums/en-US/vswpfdesigner/thread/ad9e6ed4-ce4c-450e-aa52-6db21a4d1900 and http://social.msdn.microsoft.com/Forums/en-US/vswpfdesigner/thread/a4cd0d5f-71dc-4b2c-977d-0a6825838160 including the Windows SDK fix), but none of them seem to solve my problem. If I create a new WPF Application the intellisense works in it, it just does not work in my existing project's solution anymore for some reason. Any suggestions?

My PC is running Vista Business 64-bit with 8GB of RAM and I'm using Visual Studio 2008.

We are looking into this for you. It could be Tuesday 8 Sept before we can get the answer back to you.

For now, try this. Using Windows Explorer, open the folder where one of your current solutions is located and delete the .suo file for the solution. Please let me know if this corrects the problem.

---

Cheers, Karl - Microsoft Product Team, Code Project MVP - http://karlshifflett.wordpress.com/

Hi Karl, deleting the .suo file did not work. After deleting the .suo and reopening visual studio I tried the intellisense in xaml before and after cleaning and rebuilding the project. No change. Thanks for getting back to me.

Hi Karl, it looks like the XAML intellisense is only broken in one of my solution's projects, and it is a VB.NET project (We have a mix of C# and VB projects in our solution). It was working before, then suddenly stopped one day a few weeks ago. Any more suggestions?

Would you be able to share the problem project with us? I know this may not be possible if the project is large or is your company's private intellectual property, but it would be useful to better understand the issue. If you are able to share the project, please contact me directly at mwthomas at microsoft dot com.

If not, since you are only seeing the issue in one of the solution's projects,one possibility that may enable you to work around the issue would be to port the files from the problem project to a new one(add a new VB.NET project and add the files from the old project to it, then delete the old project), and see if that helps. If this helps, it's likely the issue was with your VBProj file.

Thanks
Mark

---

Mark Wilson-Thomas - Program Team - WPF & SL Designer for Visual Studio - posts are provided 'as-is'

Unfortunately it is my company's project, so I am not able to share it with you. If I do try and port the projects files from one VB project to another I will let you know if it works or not. There are hundreds of files in the project though, so I'm not sure yet if I will attempt it or not. Thanks for the help so far anyways :)