Beta 1.2 install on VS RTM causes error in VS Code Designer

Beta 1.2 install on VS RTM causes error in VS Code Designer

• DaedMajaz

  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
  
  

• ludlowk1

  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
  
  
  
  
  

• Julianin

  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
  
  

• arun_84

  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
  
  

• GreatDane

  Hi Paul,
  
  I'm uisng C# as my main language.  I didn't change the language to do this install.
  
  Lou
  

• Cliff Stanford

  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
  
  
  
  

• Zenit

  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   3.0.03203.56
  System.Workflow.Runtime   3.0.03203.56
  EnvDTE   8.0.50727.42
  ENVDTE80   8.0.50727.42
  
  Which seems to be correct.
  
  Not sure what to do next
  
  Regards,
  
  
  

• GuitarArlen

  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).  The list in order of application:< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

   

  1.  Visual C# 2005 Express Beta 2 (installing this broke some other stuff, most noticeably my Delphi 2005 .NET development environment).

   

  2.  Visual Studio 2005 Beta 2

   

  3.  SQL Server 2005 Beta 2
  

  
  

  There were all uninstalled before I installed VS2005 RTM, and WWF Beta 1.2.  I did accidentally install WWF Beta 1 on top of VS2005 RTM, but uninstalled this and installed the 1.2 Beta. 

   

  The fix is obviously to re-image my development machine, but I just can't bring myself to do that just at the moment, plus call me a dog with a bone, but I do like to get to the bottom on an issue :-)
  
  Cheers
  
  Carl

  
  

• NEROeS

  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
  
  

• Salim

  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
  
  

• Oliver Lundt

  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.  < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

   

  If I create an Empty Workflow Project and then add either a State Machine or Sequential workflow (code), the same CodeDomDesignerLoaderNoRootSerializer issue appears.

   

  I can however add either a State Machine or Sequential workflow (with code separation) to my Empty Workflow Project.  The blank state machine/sequential workflow appears in the Workflow Designer but the Toolbox remains empty (no activities appear in the toolbox). 

   

  If you try and run/build the project you then get the following error:

   

  "The "System.Workflow.ComponentModel.Compiler.CompileWorkflowTask" task could not be loaded from the assembly System.Workflow.ComponentModel, Version=3.0.00000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35. Method not found: 'System.Object Microsoft.Build.Framework.ITask.get_HostObject()'. Confirm that the <UsingTask> declaration is correct, and that the assembly and all its dependencies are available."

   

  Just for mad I tried adding a State Machine/Sequential workflow (code) to a standard windows application and got:

   

  "The designer could not be shown for this file because none of the classes within it can be designed.

   

  at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.EnsureDocument(IDesignerSerializationManager manager)

  at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)

  at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)

  at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)"

   

  I am running XP Pro (patched up to date), the same VS 2005 RTM version reported at the start of this thread, but no SQL Server.  I did however have VS 2005 Beta 2,  SQL Server 2005 Beta 2, but uninstalled these prior to installing RTM and WWF.

   

  Any suggestions warmly welcomed.

   
  Kind regards
  
  

  
  

• lakman

  Hi Paul
  
  Errrr, ummm... how embarrassing... System.Workflow.* were all 3.0.3203.3 - how did I miss that in my wee inter-comparison!!!
  
  Discovered the "old" versions off:
  
  C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\...
  
  A working machine had the version number you specified, but off:
  
  C:\WINDOWS\Microsoft.NET\v2.0.50727\...
  
  As a rather crass fix, I just copied the contents of the Windows Workflow Foundation folder (off the above path) from a working machine across to my broken machine and added the System.Workflow.* to the assembly via the control panel .NET config.
  
  Everything appears to work; but I'll give it a serious flogging next week as for now the weekend beakons!!!  One of the benifits of being at the leading edge of the date line (in New Zealand that is) is that you get to start your weekend before anyone else!
  
  So to conclusion, it looks like the accidental installation of WWF Beta 1 was my downfall.
  
  
  Thanks for your help.  I feel like such a plonker.
  
  Kind regards
  
  Carl
  
  
• Beta 1.2 install on VS RTM causes error in VS Code Designer