When I start up VS 2008 to work on a WPF / Silverlight App and open a XAML or XML file the XAML / XML editor is no longer working. The designer does not show up and intellisense is unavailable. It basically looks like a text file has been opened.
Try running the following command.
"%ProgramFiles%\Microsoft Visual Studio 9.0\Common7\ide\devenv" /resetSkipPkgs
If that doesn't work try repairing the Visual Studio Install
Start -> Control Panel
Add Remove Programs
Select VS
Choose repair
The designer for XAML is awful. Do yourself a favour and set your XAML files to open in the code viewer instead; they'll load quicker and you won't have to deal with the designer's flakiness.
However, to fix the intellisense, just re-register TextMgrP.dll using regsvr32 as indicated here.
I've seen this problem before, running this command should fix it :
Devenv.exe /ResetSkipPkgs
If you right click the file, select "Open With", and then choose "Windows Presentation Foundation Designer", does that work? If so, most likely the default editor for .xaml files has changed. You can reset this back to the designer by pressing "Set as Default" when the designer you want is selected in the list in the Open With dialog.
It looks like there is an XML package that was previously not loaded, see other question here;
Visual Studio 2008 XML Editor Disappeared
Also, there is an answer on the Silverlight forums that describes using the "devenv /setup" command that can be found in (VS2008InstallationDirectory)\IDE.
AHHHHHHHHHHHHHHH!!!!!! It finally worked!!!!! Only after a week of pulling my hair out. I had multiple issues.
Xaml editor and add DataSource Wizard and other things would not work with VS 2008.
Tried to install SP1. It would not let me because Office Suite 2007 was in the middle of an SP1 update and would not finish.
Un-installed Microsoft office and reinstalled and service packed.
Tried devenv /setp & devenv /resetskippkgs to no avail.
Finally service packed VS2008.
Retried the devenv /setp & devenv /resetskippkgs twice and voila!! It worked.
Thanks a bunch.
i had similar problems when i installed VS2008 Professional over an existing VS2008 Express edition. Suddenly my XAML designer stopped working . i got failed loading the XAML dll error.
So i just uninstalled all VS Express stuff and then installed VS 2008 SP1 fixed all things.
try link below for VS 2008 SP1.
http://www.microsoft.com/downloads/details.aspx?FamilyId=27673C47-B3B5-4C67-BD99-84E525B5CE61&displaylang=en
Related
I'm using Visual Studio 2012 Professional Edition and have a WPF project.
I'd like to open my WPF project with Blend but the option doesn't exist in my visual studio.
Should I install Blend separately? How can I make the option visible and enable it?
Look at this video: http://www.microsoft.com/en-us/showcase/details.aspx?uuid=ab9788fc-cd18-474a-942c-61754e9e428b
there is an "Open for Blend" option when right clicking on the project.
You can initiate a new instance of blend 2012 and open the corresponding project in that.. This is very basic.. is it not working?
I have had this same exact problem with using VS2013 Ultimate SP2.
It would appear that this only actually works when it's a Silverlight project, but once you open up Blend for Visual Studio you're able to go to File -> Open Project/Solution... and select the project you want to design with Blend.
As far as I am aware this is the only way to open Blend without looking through the VS 2012/2013 program folders. I have tried it several times with WPF (even right-clicking on specific XAML files) with no success.
This may have been fixed, so I will be updating VS2013 to the latest version (SP3) and update this answer with my findings.
I just got a new PC with Windows 7. While editing a WPF window, when I right-click on a control and select Properties, I get the familiar property window docked in the lower-right coner. For some reason, I do not see the lightning bolt button to toggle over to the events. Also, when I double-click on a control, nothing happens.
Has anyone seen this? What can I do?
You need to install VS 2008 SP1 for that feature (and a lot more!).
I manually uninstalled VS 2008 (by uninstalling each component one-by-one as specified in the readme file), then reinstalled it along with SP1, and it's fixed now.
I have just installed Visual Studio 2010.
when I attempt to create a new project in c#, there is no option for a WPF application. There is for Visual Basic.
The WPFApplicaton.zip flie does exist in C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplates\CSharp\Windows\1033
What could be wrong here?
My first suggestion would be to run the installer again - it should come up with "repair" and "change" (or something like that) options along with "uninstall".
"Repair" will reset what you already have installed.
"Change" (or "Update" - I don't have VS2010 installed on this machine to check the actual wording) should let you run through the install again adding and removing components. Step through this double checking that you've installed all the templates and options.
If that doesn't work then you could try an uninstall and re-install/
You need to specify the targeting .NET framework.
Select File menu from VS2008 or VS2010; Select .NET framework 3.5 or 4.0; Select Visual C#. you will find WPF Application template listed
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.
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!