I'm having problems loading WWF b1.2 onto VS2005 RTM on WinXP. Getting error: CodeDomDesignerLoaderNoRootSerializer.
The version for VS RTM is 8.0.50727.42
I've tried install/deinstall/reinstall several times on 2 separate machines.
Any suggestions?
TIA |
| TenDot |
Other users have reported that this occurs when you have VS2003 and VS2005 both installed and that it does not occur if you uninstall VS2003.
Do you have VS2003 installed?
Regards,
Paul
Workflow Product Manager. This posting is provided "AS IS" with no warranties, and confers no rights |
| Paul Andrew |
Hey guys,
I've also got this error on my machine (and like you I did the whole re-install thing too)
I've got:
SQL 2005 - release
VSNet 2005 pro- release
Biztalk 2006 CTP
I'm not sure what caused it. (as VSNET 2003 hasnt been anywhere near this)
My install order:
OS + Patches (Win2003 Srv)
SQL 2005 + dev. studio
VS.NET 2005
BTS CTP 2006
All installed fine - no immediate errors to report.
Any thoughts?
Mick Badran - http://blogs.breezetraining.com.au/mickb |
| Mick Badran |
I'm encountering the same issue (the subject of a number of other threads on this forum) when I try and create any new workflow project, except for an Empty Workflow Project. |
| Carl Dawson |
Regarding the CodeDomDesignerLoaderNoRootSerializer error that some people have seen on Windows Workflow Foundation Beta 1.2 on Visual Studion 2005 RTM.
Some people have seen this occur when they choose only VB.NET when installing Visual Studio 2005.
Regards,
Paul
Workflow Product Manager. This posting is provided "AS IS" with no warranties, and confers no rights |
| Paul Andrew |
Hi Paul,
I'm uisng C# as my main language. I didn't change the language to do this install.
Lou |
| TenDot |
Hi all
I am also set up for C#, and like others on this thread, have never had VS2003 anywhere near the machine...
I have since installed WWF on two other "clean" XP machines and they both work perfectly. I have tried a bit of an agricultural compare between various aspects of a working machine and a broken machine (e.g. registry settings, file versions, gac, directory contents) but can't see anything obvious.
My broken install machine differs from a working install by a series of Beta's previously installed (and removed). |
| Carl Dawson |
Hi Carl,
Let's try something else then to get to the bottom of this CodeDomDesignerLoaderNoRootSerializer issue.
Open explorer. Browse to c:\Windows\Assembly. Check the versions of all the workflow related assemblies. They all should be 3.0.3203.56. Check these assemblies:
System.Workflow.Activities
System.Workflow.ComponentModel
System.Workflow.Runtime
Also check EnvDTE and ENVDTE80 which should both be 8.0.50727.42.
In both cases this is the file version that you see when you right click and choose properties and then click the version tab.
Cheers,
Paul
Workflow Product Manager. This posting is provided "AS IS" with no warranties, and confers no rights |
| Paul Andrew |
Hi Paul,
I am also getting a package load failure with VS2005 when workflow beta 1.2 is installed:
'Microsoft.Workflow.VSDesigner.DesignerPackage, Microsoft.Workflow.VSDesigner, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has failed to load properly...'
I have VS2005 Professional RTM (which I have uninstalled and reinstalled twice). I previously had installed VS2005 beta 2 & workflow beta 1 and then uninstalled the components in the order recommed in another Microsoft post, and then installed VS2005 Professional RTM...but still the package load failure.
I checked in C:\Windows\Assembly and found the assemblies with the following versions:
System.Workflow.Activities 3.0.03203.56
System.Workflow.ComponentModel |
| DrQwest |
Hi Paul
Errrr, ummm... how embarrassing |
| Carl Dawson |
Hi Carl,
Great to hear you solved this. I'm also originally from New Zealand.
Hi DrQwest,
The error you reported has been linked with invalid mixes of VS 2005 Beta 2 and WF Beta 1. One reasonably likely way to solve this (though will take a few hours) is to:
1) uninstall VS2005 from control panel (uninstall the dependent dev tools first)
2) uninstall the .NET Framework from control panel (all versions)
3) delete c:\windows\Assembly
4) delete c:\Windows\Microsoft.NET
5) reinstall VS 2005 RTM and WF Beta 1.2
Regards,
Paul
Workflow Product Manager. This posting is provided "AS IS" with no warranties, and confers no rights |
| Paul Andrew |
Hi Paul,
It worked ...thanks!. The extra steps to delete the folders (C:\Windows\Assembly & C:\Windows\Microsoft.Net) between the uninstall and reinstall made the difference.
Regards,
DrQwest
|
| DrQwest |
Hi Paul and DrQwest,
You pointed me the right direction. I had the same "package load failure", but did not want to go reinstalling right away. I searched the registry and found this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\AutoLoadPackages\{adfc4e64-0397-11d1-9f4e-00a0c911004f}
On my system it contained a DWord with name {FD526733-BD72-4F81-BEEC-BEB06E2AF59F}. This is the same guid as in the errormessage you get.
Besides this DWord there was another, wich I removed.
Then I uninstalled WWF 1.2, rebooted and installed WWF 1.2 again. This fixed the problem.
I also emptyed my recyclebin that contained some old framework stuff, but I hope that was not the problem.
Maybe just removing the key and then rebooting will do the trick.
bye,
Arjan
|
| Arjan Pot |
index > Windows Workflow Foundation > Beta 1.2 install on VS RTM causes error in VS Code Designer