![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
| |
| | #1 (permalink) |
| | Problem upgrading to Feb CTP Hi all, I tried to upgrade from the Dec CTP to the Feb CTP. After successive attempt, I finally removed Visual Studio as well, then installed everything in the following order: - WinFX runtime - Visual Studio - Windows SDK - Visual Studio extensions I can at least open my projects, but any build results in the following: Error 1 The "Microsoft.Build.Tasks.Windows.GetWinFXPath" task could not be loaded from the assembly PresentationBuildTasks, Version=3.0.51116.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35. Could not load file or assembly 'PresentationBuildTasks, Version=3.0.51116.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, and that the assembly and all its dependencies are available. Is anyone else experiencing this? Jason |
My System Specs![]() |
| | #2 (permalink) |
| | Re: Problem upgrading to Feb CTP I have the same exact problem... I had the January CTP installed, used the uninstall tool, and installed the other tools as instructed. I am seeing the exact same error messages. I've tried repairing twice and reinstalling 3 times. No luck. Jake "Leo Xue" wrote: > You should remove the reference of PresentationBuildTasks the reload it. > As I noticed, the location of the assembly(s) is changed in the new SDK. > > Hope this help. > > > "Jason Dolinger" <jdolinger@lab49.com> > ??????:OLUcMjMOGHA.1360@TK2MSFTNGP10.phx.gbl... > > Hi all, > > > > I tried to upgrade from the Dec CTP to the Feb CTP. After successive > > attempt, I finally removed Visual Studio as well, then installed > > everything in the following order: > > > > - WinFX runtime > > - Visual Studio > > - Windows SDK > > - Visual Studio extensions > > > > I can at least open my projects, but any build results in the following: > > > > Error 1 The "Microsoft.Build.Tasks.Windows.GetWinFXPath" task could not be > > loaded from the assembly PresentationBuildTasks, Version=3.0.51116.0, > > Culture=neutral, PublicKeyToken=31bf3856ad364e35. Could not load file or > > assembly 'PresentationBuildTasks, Version=3.0.51116.0, Culture=neutral, > > PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system > > cannot find the file specified. Confirm that the <UsingTask> declaration > > is correct, and that the assembly and all its dependencies are available. > > > > Is anyone else experiencing this? > > > > Jason > > > > > |
My System Specs![]() |
| | #3 (permalink) |
| | Re: Problem upgrading to Feb CTP GooberDLX wrote: > I have the same exact problem... I had the January CTP installed, used the > uninstall tool, and installed the other tools as instructed. > > I am seeing the exact same error messages. > > I've tried repairing twice and reinstalling 3 times. No luck. > Jake > > "Leo Xue" wrote: > >> You should remove the reference of PresentationBuildTasks the reload it. >> As I noticed, the location of the assembly(s) is changed in the new SDK. >> >> Hope this help. >> >> >> "Jason Dolinger" <jdolinger@lab49.com> >> ??????:OLUcMjMOGHA.1360@TK2MSFTNGP10.phx.gbl... >>> Hi all, >>> >>> I tried to upgrade from the Dec CTP to the Feb CTP. After successive >>> attempt, I finally removed Visual Studio as well, then installed >>> everything in the following order: >>> >>> - WinFX runtime >>> - Visual Studio >>> - Windows SDK >>> - Visual Studio extensions >>> >>> I can at least open my projects, but any build results in the following: >>> >>> Error 1 The "Microsoft.Build.Tasks.Windows.GetWinFXPath" task could not be >>> loaded from the assembly PresentationBuildTasks, Version=3.0.51116.0, >>> Culture=neutral, PublicKeyToken=31bf3856ad364e35. Could not load file or >>> assembly 'PresentationBuildTasks, Version=3.0.51116.0, Culture=neutral, >>> PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system >>> cannot find the file specified. Confirm that the <UsingTask> declaration >>> is correct, and that the assembly and all its dependencies are available. >>> >>> Is anyone else experiencing this? >>> >>> Jason >>> >> >> Well, I got fed up and restored my system... I've now done two upgrades, Nov CTP -> Dec CTP, Dec CTP -> Feb CTP. In terms of success rate it's 0 for 2 for me (exactly following the directions from the winfx site and using the uninstall tool). Jason |
My System Specs![]() |
| | #4 (permalink) |
| | RE: Problem upgrading to Feb CTP I solved this problem, but don't know exactly how. There was Dec CTP on my computer. I uninstall Dec [VS Extensions and RC Components] and install Feb (without SDK). Error about Microsoft.Build.Tasks.Windows.GetWinFXPath (above). I uninstall Dec SDK and tried install Feb SDK (minimum). After ~100 Mb downloading through my 56k modem installation stoped with Uknown Fatal Error. I removed all this stuff ![]() After that i install Feb RC Components again, Dec SDK, Feb VS Extensions. And recieved another error about versions 3.0.51116.0 vs 6.0.5070. I removed RC Components, RENAME C:\Program Files\Reference Assemblies folder and install RC Components again. Now it's work. Maybe this helps. |
My System Specs![]() |
| | #5 (permalink) |
| | Re: Problem upgrading to Feb CTP I'm getting the same problem. Also, all of my WPF-related references are marked as not loading in VS, even if I add them by browsing to them. The only "Presentation" dlls showing up in my GAC are CFFRasterizer, Framework.Royale, and UI. Nick Jason Dolinger wrote: > Hi all, > > I tried to upgrade from the Dec CTP to the Feb CTP. After successive > attempt, I finally removed Visual Studio as well, then installed > everything in the following order: > > - WinFX runtime > - Visual Studio > - Windows SDK > - Visual Studio extensions > > I can at least open my projects, but any build results in the following: > > Error 1 The "Microsoft.Build.Tasks.Windows.GetWinFXPath" task > could not be loaded from the assembly PresentationBuildTasks, > Version=3.0.51116.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35. > Could not load file or assembly 'PresentationBuildTasks, > Version=3.0.51116.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' > or one of its dependencies. The system cannot find the file specified. > Confirm that the <UsingTask> declaration is correct, and that the > assembly and all its dependencies are available. > > Is anyone else experiencing this? > > Jason > |
My System Specs![]() |
| | #6 (permalink) |
| | Re: Problem upgrading to Feb CTP I think I might have found part of the problem: the Windows SDK contains version 3.0.51116.0 of the various files, but the WinFX RC Feb CTP contains version 3.0.50727.38... Could this be causing the issue? Most of my Presentation files (including PresentationFramework and PresentationBuildTasks) are marked 3.0.50727.38, but Visual Studio (and XAMLPad) complain that they can't find version 3.0.51116.0. Could somebody on the WPF team tell me if I'm right about this, and if so, how I would go about fixing it? Thanks, Nick |
My System Specs![]() |
| | #7 (permalink) |
| | Re: Problem upgrading to Feb CTP OK, I found the problem and fixed it. Assuming that everybody else has the same problem as me (instead of just the same symptoms), here's what I did: Uninstall WinFX SDK. Move "C:\Program Files\Reference Assemblies" to a different folder (I renamed it to "_Reference Assemblies"). Repair WinFX RC Feb. The problem is (apparently) that some old assemblies get left behind in the Reference Assemblies folder, and the new RC CTP doesn't overwrite them. So, the new assemblies are not copied to the folder, and thus can't be registered in the GAC. By removing the folder (or renaming it) and reinstalling the RC, you get it to install the new assemblies. You have to uninstall the SDK so that you can reinstall it after removing the Reference Assemblies folder. I hope this helps all you guys having this problem. Nick Howell |
My System Specs![]() |
| | #8 (permalink) |
| | Re: Problem upgrading to Feb CTP I'll try it this afternoon and see what I can come up with as well... "Nick Howell" wrote: > OK, I found the problem and fixed it. Assuming that everybody else has > the same problem as me (instead of just the same symptoms), here's what > I did: > > Uninstall WinFX SDK. > Move "C:\Program Files\Reference Assemblies" to a different folder (I > renamed it to "_Reference Assemblies"). > Repair WinFX RC Feb. > > The problem is (apparently) that some old assemblies get left behind in > the Reference Assemblies folder, and the new RC CTP doesn't overwrite > them. So, the new assemblies are not copied to the folder, and thus > can't be registered in the GAC. > > By removing the folder (or renaming it) and reinstalling the RC, you get > it to install the new assemblies. > > You have to uninstall the SDK so that you can reinstall it after > removing the Reference Assemblies folder. > > I hope this helps all you guys having this problem. > > Nick Howell > |
My System Specs![]() |
| | #9 (permalink) |
| | Re: Problem upgrading to Feb CTP I confirmed that by just installing the Feb CTP WinFX run time, that the assemblies do get into the GAC properly. Once you install the SDK, for some strange reason it's messing it up. Will verify the rest of this process later. "GooberDLX" wrote: > I'll try it this afternoon and see what I can come up with as well... > > "Nick Howell" wrote: > > > OK, I found the problem and fixed it. Assuming that everybody else has > > the same problem as me (instead of just the same symptoms), here's what > > I did: > > > > Uninstall WinFX SDK. > > Move "C:\Program Files\Reference Assemblies" to a different folder (I > > renamed it to "_Reference Assemblies"). > > Repair WinFX RC Feb. > > > > The problem is (apparently) that some old assemblies get left behind in > > the Reference Assemblies folder, and the new RC CTP doesn't overwrite > > them. So, the new assemblies are not copied to the folder, and thus > > can't be registered in the GAC. > > > > By removing the folder (or renaming it) and reinstalling the RC, you get > > it to install the new assemblies. > > > > You have to uninstall the SDK so that you can reinstall it after > > removing the Reference Assemblies folder. > > > > I hope this helps all you guys having this problem. > > > > Nick Howell > > |
My System Specs![]() |
| | #10 (permalink) |
| | Re: Problem upgrading to Feb CTP Hi, Has anyone fixed this yet? I'm getting the Package Load Failure for 'PresentationDesignVisualStudio' error when I try to open a .xaml file in an existing (MSDN sample) Visual Studio project. I have installed WinFx as follows: 1. FRESH install of Vista 5308 (Feb 06 CTP). 2. Windows Update for the machine specific drivers. 3. WinFX Runtime Components - Feb 06 CTP. 4. Visual Studio 2005 Pro 5. Windows SDK 6. Visual Studio Extensions for WinFX 7. Visual Studio Extensions for Workflow Foundation Next, I open the Avalon Basic3D CSharp sample project from MSDN. This opens fine. When I try to open the MyApp.xaml file it reports the error above. Any ideas? Thanks, Mart. "GooberDLX" wrote: > I confirmed that by just installing the Feb CTP WinFX run time, that the > assemblies do get into the GAC properly. Once you install the SDK, for some > strange reason it's messing it up. Will verify the rest of this process later. > > "GooberDLX" wrote: > > > I'll try it this afternoon and see what I can come up with as well... > > > > "Nick Howell" wrote: > > > > > OK, I found the problem and fixed it. Assuming that everybody else has > > > the same problem as me (instead of just the same symptoms), here's what > > > I did: > > > > > > Uninstall WinFX SDK. > > > Move "C:\Program Files\Reference Assemblies" to a different folder (I > > > renamed it to "_Reference Assemblies"). > > > Repair WinFX RC Feb. > > > > > > The problem is (apparently) that some old assemblies get left behind in > > > the Reference Assemblies folder, and the new RC CTP doesn't overwrite > > > them. So, the new assemblies are not copied to the folder, and thus > > > can't be registered in the GAC. > > > > > > By removing the folder (or renaming it) and reinstalling the RC, you get > > > it to install the new assemblies. > > > > > > You have to uninstall the SDK so that you can reinstall it after > > > removing the Reference Assemblies folder. > > > > > > I hope this helps all you guys having this problem. > > > > > > Nick Howell > > > |
My System Specs![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Problem upgrading from XP SP2 to Vista | Vista installation & setup | |||
| problem with upgrading | Vista installation & setup | |||
| A Problem I've had In Upgrading Vista | Vista General | |||
| Problem upgrading to RC2 from RC1 | Vista installation & setup | |||