Package Load Failure message

[Carl]

I have worked in VB6 for a few years; taking the plunge now into VB.NET.
I just installed Visual Studio 2008; it installed with no errors. I
launch it and receive the following error message:

Package 'Microsoft.VisualStudio.Xaml' has failed to load properly ( GUID
= {E58C2A8B-etc., etc., etc.} ). Please contact package vendor for
assistance. Application restart is recommended, due to possible
environment corruption. Would you like to disable loading this package
in the future? You may use 'devenv /resetskippkgs' to re-enable package
loading.

Has anyone else encountered this, and if so what did you do to resolve it?

Thanks in advance,

Carl

 

[Cor Ligthert[MVP]]

Carl,

There are more versions of Visual Studio 2008, the version with only the
name you give don't exist.

Carl,

I tried Google.

http://www.google.com/search?hl=en&...to+load+properly+&btnG=Google+Search&aq=f&oq=

Cor

 

[Andrew Morton]

I have worked in VB6 for a few years; taking the plunge now into
VB.NET. I just installed Visual Studio 2008; it installed with no errors.
I
launch it and receive the following error message:

You could try installing SP1 (takes ages) and see if the problem goes away.

VS2008SP1:
http://www.microsoft.com/downloads/...48-7106-44A7-9649-6D9F6D58056E&displaylang=en

Andrew

 

[Carl]

I have worked in VB6 for a few years; taking the plunge now into VB.NET.
I just installed Visual Studio 2008; it installed with no errors. I
launch it and receive the following error message:

Package 'Microsoft.VisualStudio.Xaml' has failed to load properly ( GUID
= {E58C2A8B-etc., etc., etc.} ). Please contact package vendor for
assistance. Application restart is recommended, due to possible
environment corruption. Would you like to disable loading this package
in the future? You may use 'devenv /resetskippkgs' to re-enable package
loading.

Has anyone else encountered this, and if so what did you do to resolve it?

Thanks in advance,

Carl

Thanks for both of your responses - I should have gone onto the
internets and checked the Google first
Although I did not install any pre-release software, I still was
encountering this issue. Long story short - complete uninstall
(including the two Express version installs that I had done) then a
complete install then SP1 and it seems to have taken care of the issue.
Thanks to both of you for your time.
Carl