1

I'm trying to create my own language service in Visual Studio 2008 SP1, but when I run the program (which starts the Visual Studio Experimental Hive) and try to open a source file, I get this error:

Package 'Microsoft VisualStudio CodeTools PropertyPage Package' has failed to load properly ( GUID = {072DD0C6-AE1E-4ED6-A0BF-B99D5B68D29E} ).

Any ideas how to fix it? (I already tried uninstalling and reinstalling VS, it didn't work. :( )

Update

It turns out this was due to a poor uninstallation of Spec#. I cleaned it up, but now the issue is that my language service doesn't actually highlight anything... I imagined this to be the cause, but seeing as how I still get the error and how it was irrelevant, I don't know what the problem is.

I'm using the default lexer/parser files with the default tokens, so I'd imagine there would be some sort of highlighting for my file types, but there isn't... any thoughts?

Community
  • 1
  • 1
user541686
  • 205,094
  • 128
  • 528
  • 886
  • please post your "update" as a new question as it is not related to your original post and change back the title of the post to the original so other people with the same error can find this post. – Brian McCarthy Apr 26 '11 at 12:46
  • Perhaps, you can add into the update how you found out a poor uninstallation of Spec# was the issue as part of your update to help other people out. – Brian McCarthy Apr 26 '11 at 12:48

2 Answers2

1

Here are the steps you need to take to get rid of this error:

The Visual Studio 2008 Service Pack Preparation Tool will help getting rid of pre-release versions of the SP1 software and other items which are known to cause issues, such as:

  • Microsoft Silverlight Tools Beta 1
  • Microsoft Visual Studio 2008 - KB949325
  • Microsoft Visual Studio 2008 - KB944899 (v1)
  • Microsoft Visual Studio 2008 - KB945140 (SP1 Beta)

If you encounter issues installing SP1, uninstall technologies and/or development add-ins not listed above, and then try SP1 Setup again. Only the following technologies have been tested and verified to work with SP1:

  • Silverlight 2 SDK Beta 2 & Silverlight Tools Beta 2. (If Silverlight Tools Beta 2 is already installed, you must upgrade it after you install Visual Studio 2008 SP1. To upgrade, use the installer on the Silverlight Tools Beta 2 page on the Microsoft Download Center Web site.)
  • MVC Preview Release #3
  • ASP.NET Extensions/Dynamic Data Preview
  • VC 2008 Feature Pack
  • VB PowerPack Controls (2.0 & 3.0)
  • Expression Studio 2 (RTM)
  • SQL Server 2008
  • .NET Framework 3.5 SDK
  • XSLT Profiler
  • VSTA 2.0 SDK
  • Visual Studio 2008 SDK
Brian McCarthy
  • 4,658
  • 16
  • 49
  • 66
  • @Mehrdad, try this and let me know if this helps! It did for me! :) – Brian McCarthy Apr 25 '11 at 14:03
  • Thanks for the list. However, given that I didn't/don't have any beta/pre-release software on my machine, it seems like it all pretty much reduces down to "Uninstall Visual Studio 2008" and then "Reinstall Visual Studio 2008" and "Reinstall SP1", no? That's pretty much what I tried, except that I skipped installing SP1 the second time because it seems irrelevant to the error IMHO... so isn't this basically what I tried at first? – user541686 Apr 25 '11 at 16:39
  • +1 since this helped me figure out it was an add-in problem. Now I'm trying to figure out what's preventing the language service from working, any thoughts? – user541686 Apr 25 '11 at 16:55
  • @Mehrdad, there could be multiple causes for this error so it's better to go through all the steps to make sure you don't leave anything out. SP1 works with a limited list of technologies that I listed above. I would start with running "devenv.exe /resetskippkgs". If that doesn't work, I would go through your "programs and features" / "add or remove programs" and uninstall anything that you aren't familiar with and/or isn't listed above. I would also use the Visual Studio 2008 Service Pack Preparation Tool. If that doesn't work, back-up your data, and reformat with a clean install of windows. – Brian McCarthy Apr 26 '11 at 12:32
0

Never mind, it seems like it's working correctly:

if (x == 0)
{
}

is not even correct C code in the first place!

I was looking for syntax highlighting but I needed to set it up first, and it seems like it's working now.

user541686
  • 205,094
  • 128
  • 528
  • 886