WPF Package Load Failure? - wpf

Package Load Failure
Package 'Microsoft.VisualStudio.Xaml' has failed tot load properly. . . yadda, yadda, yadda.
So now what? This package is somewhat important since I was hoping to do some WPF stuff this afternoon. Tried running without it and my XAML design view is gone.
I already tried "devenv /resetsettings" from the command prompt.
Thanks,
Scott

Try repairing the install.
Control Panel
Add Remove Programs
Select Visual Studio 2008 and choose "repair"
Did you recently install any updates to Visual Studio or any Add-Ins? If so can you please list them?

Install SP1: http://www.microsoft.com/downloads/details.aspx?FamilyId=FBEE1648-7106-44A7-9649-6D9F6D58056E&displaylang=en
I had this problem after a fresh install of VS2008 Team System. Tried loading the updates, running setup, re-installing. No luck.
Installed SP1 and bingo! No more package load failures.

I -FINALLY- saw this error going into Tools|Options|Environment Fonts and Colors after trying everything I could think of to get it not to crash when I chose Tools|Import and Export Settings.

I had this problem when I installed Visual Studio Professional.
My theory was that it was because I already had Visual C# 2008 Express Edition installed.
Once I uninstalled both then reinstalled Visual Studio Professional it worked.
This is consistent with the OP's solution, which was to uninstall anything else which implemented XAML functionality.

In my case, just reinstalling SP1 didnt worked
Then i saw ive had two languages mixed in the IDE. So ive checked the installed programs and found:
Microsoft Visual Studio Tools For Applications 2.0 ENU
Microsoft Visual Studio Tools For Applications 2.0 Language Pack - ESN
When ive uninstalled the additional pack, the design views started to work again

In my case the machine.config file had gotten some bad XML due to a recent installation. There were two closing tags. After we corrected the bad XML, .NET works just fine.

Thank you Abraham for the hint. I was missing an end tag in my .NET 2.0 x86 machine.config.
However I had already spent hours repairing, uninstalling, installing and installing service packs.
WOULDN'T IT BE NICE IF VISUAL STUDIO 2008 GAVE A "MACHINE.CONFIG" CORRUPT ERROR!

Related

SQL Server Management Studio 2016: The application cannot start

I installed SQL Server Management Studio 2016. When I tried to open it gives this error. I tried uninstall and again install. Also I uninstall all Visual Studio and SQL Server and reinstall all of them but problem still continue.
How can I solve this issue?
In my case, the issue was with broken VS2015 isolated shell installation.
I resolved it by downloading and re-installing this shell from Visual Studio Isolated Shell page https://learn.microsoft.com/en-ca/visualstudio/extensibility/visual-studio-isolated-shell (which should eventually lead you to http://go.microsoft.com/fwlink/?LinkId=615451 - after filling out the survey).
Note:
I had following warnings after the VS1205 shell install. But that
did not matter, since the existing version of these components was
higher.
I had no VS IDEs installed on my computer prior to
installing SSMS 16.5.3 (or 17.1). Both had the same issue. For now I
am using only SSMS 16.5.3, since I do not have a need for 17.1
I completely remove all microsoft application and re install sql server 2016 and the reinstall ssms and ssms worked and finally I install vs17 now its working.
Problem is about to "Microsoft Visual Studio 2015 Shell(Isolated)"
We need to install vs after ssms.
Happened to me on SSMS v17.9.1.
I've repaired Microsoft Visual Studio 2015 Shell (Isolated) and the problem went away.
According to MSDN documentaion:-
An unexpected error has prevented Visual Studio from starting. This error appears when one of the following items occurs:
The integrated development environment (IDE) was not able to load Msxml3.dll.
The IDE was not able to load Mso.dll.
The IDE was not able to load DTE.olb.
The license key for Visual Studio was not created during setup.
Script blocking is turned on and not allowing scripting code to execute.
Setup for the .NET Framework, a component required by Visual Studio, failed to generate a valid native image for mscorlib.dll.
The Klez virus is present on your computer
And the article is introduced specific procedures to correct this error.
Hope helps.

Unable to open SSIS project in Visual Studio 2012 or 2013 (migration fails)

I am trying to open a solution file in Visual Studio 2013 Ultimate that includes an Integration Services project (.dtproj). Unfortunately, the migration failed for reasons that are slightly baffling to me.
The migration report contains the following error:
RecommenderJobs.dtproj: The application which this project type is based on was not found. Please try this link for further information: http://go.microsoft.com/fwlink/?prd=12395&pver=11&sbp=ProjectTypeDeprecated&plcid=0x409&clcid=0x409&ar=MSDN&sar=ProjectCompatibility&o1=159641D6-6404-4A2A-AE62-294DE0FE8301
Unfortunately, the link appears to be dead, so that's no help.
I also received the following error message when I tried to open this in Visual Studio 2012:
I've tried opening this solution in both Visual Studio 2012 Ultimate and Visual Studio 2013 Premium (which is why I tagged both). Both are on Update 5. I already tried updating all of my extensions and updates, even ones that seem like they wouldn't be directly relevant to the problem (like Visual Studio's Office tools).
I found a similar question on Microsoft's forum. The suggestion there was to upgrade my version of SSIS to the latest version. I tried to install SSDT for VS2013 as suggested, but the install failed:
When I checked the logs, it had the following error:
Error 0x80070666: Cannot install a product when a newer version is installed.
I do, in fact, have a different version installed, but it's not actually newer as far as I can tell (in fact, it launches in the Visual Studio 2010 shell), so I'm a little confused by this. The version information is below:
Microsoft SQL Server Integration Services Designer
Version 11.0.5058.0
Microsoft SQL Server Reporting Services Designers
Version 11.0.5058.0
I do also have tools related to SQL Server 2012 installed.
Based on what I've read in other posts, I'd expect to see the SQL Server Data Tools in "Add/Remove Programs," but it's not. Does anyone know why that might be?
I've also seen related questions for other types of projects, such as for a PowerShell project. (Obviously, my question has nothing to do with Powershell, but the OP there was receiving the same exact error message for a different project type). Unfortunately, the suggestions on that post didn't seem all that helpful - for example, the accepted answer there involved completely uninstalling and reinstalling Visual Studio, which would be a major pain to say the least. I'm also not all that confident that that would work for me since this problem occurs in two separate versions of Visual Studio.
Does anyone have any suggestions on what else I could try?
You likely need to install both Integration services and Business Intelligence for Visual Studio (BIDS). You can do it launching SQL Server Setup and adding features to your current SQL Server Instance.
Have a look at this one: https://guruprasadv.wordpress.com/2009/06/17/opening-ssis-package-in-visual-studio/
BIDS is the IDE (integrated into Visual Studio) that allows you to drag and drop the components and create the SSIS packages. From SQL Server 2014 on wards you won't see BIDS anymore packaged in the SQL Server Setup, so you will have to install it independently. If you need it for VS 2013 here you have the link: https://www.microsoft.com/en-us/download/details.aspx?id=42313

How do I uninstall SSDTBI for VS 2013/SQL Server 2014?

I recently installed the client tools for SQL Server 2016. This seemed to hose the COM classes for SSIS in my VS 2013 install, as well as my SSMS 2014 install.
I get a COM class not found {guid} error. I don't have a screenshot because I have since uninstalled VS 2013. I've uninstalled SQL Server 2014 as well. The problem is I'm pretty sure SSDTBI is still installed somewhere, and it does not have an entry in the control panel.
I don't want to waste my time installing VS 2013 again if those templates and everything are still going to be there.
Running the SSDTBI installer shows the SSDTBI features as grayed out (meaning they are already installed) and offers no option to remove.
Does anyone know what files are installed and their locations? I really would like to do a clean install.
Thank you.
Well - After googling some more and seeing all the code for command line installs - I had a revelation that worked:
setup.exe /ACTION=UNINSTALL
Did the trick.

SQL Server Management Studio (SSMS) 2014 System.EnterpriseServices.Wrapper.dll Error

SSMS 2014 SP1 recently started throwing an error around a mismatch of the System.EnterpriseServices.Wrapper.dll when trying to connect to any database.
I had recently installed LinqPad 5 which required installing.Net 4.6.
Trying to repair SSMS did not fix the issue. Various resources online, suggesting updating the GAC and C:\Windows\winsxs\x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790 assemblies from the .Net 2.0 folder and the also did not fix the issue.
This was my solution to get my dev environment back to working as normal. Obviously it isn't ideal, so if anyone has a better solution, please share.
As an interim measure:
Uninstall .Net 4.6 from Add/Remove Programs
Reinstall .Net 4.5.1
from: https://msdn.microsoft.com/en-us/vstudio/hh487283.aspx
Restart SSMS, possibly you may need to restart your computer
If you subsequently recieve an error in Visual Studio:
Open the VS developer command prompt (C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\Shortcuts for Visual Studio 2013)
Run devenv /setup
Alternatively you could run a repair from the VS installer
I believe this is because .Net 4.6 overwrites the files in the C:\Windows\Microsoft.NET\Framework\v4.0.30319 folder, as .Net 4.x all share this folder, SSMS doesn't seem to be able to handle the updgrade. .Net 2.0 uses a different folder, hence why alot of the solutions around presumably didn't help.

Visual Studio 2008 WPF Project error "project type is not supported"

I'm running Windows 7 x64 with Visual Studio 2008 (SP1). Yesterday I came across an issue when creating WPF projects. I don't know if I've created any other WPF projects since I installed Win7.
First of all, in the Create Project dialog, the project type says "csWPFApplication" which is weird enough and I never noticed before. When I try creating the project I get 2 Package Load Failure errors for Microsoft.VisualStudio.Internal.WPFFlavor.WPFPackage and then a message that "The project file ... cannot be opened. The project type is not supported by this installation.
I tried a number of different suggestions from Google and even uninstalled/reinstalled to no avail. Any ideas?
Try starting Visual Studio with.
C:\Program Files\Microsoft Visual
Studio 9.0\Common7\IDE\devenv.exe
/resetskippkgs
I would also try to just create a blank solution/WPF project. and then add the files from your old project one at a time, and see if you still get the error.
If that doesn't work, I would try to uninstall and reinstall .NET 3.5 which looks it could be corrupt.

Resources