Home Dashboard Directory Help
Search

Workflow Designer Rehosting is not possible by semeltheone1


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 535596
Opened: 2/23/2010 3:58:33 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I tried to host the WorkflowDesigner Control in a standard wpf application. This works great for the DesignerControl and the PropertyInspector. But as soon as i try to put the ToolBoxControl into the child collection of a grid or any other content Control it fails with a TargetInvocationException.

The code i used can be found at:
http://msdn.microsoft.com/en-us/library/dd699776(VS.100).aspx

The funny thing is, that i can see the ToolBox in the WPF Designer. But when i try to run the App, it crashes.
A colleague of mine uses the same code and it works perfectly. The only thing different,is that i had installed the beta releases of vs and .net 4.0.

The Exception i get:

bei System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
bei System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache)
bei System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean skipCheckThis, Boolean fillCache)
bei System.Activator.CreateInstance(Type type, Boolean nonPublic)
bei System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
bei System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
bei System.Xaml.Schema.XamlTypeInvoker.CreateInstance(Object[] arguments)
bei MS.Internal.Xaml.Runtime.ClrObjectRuntime.CreateInstanceWithCtor(XamlType xamlType, Object[] args)

InnerException(NullReferenceException):

bei System.Windows.ResourceDictionary.GetKeyValue(KeyRecord key, IServiceProvider serviceProvider)
bei System.Windows.ResourceDictionary.SetKeys(IList`1 keyCollection, IServiceProvider serviceProvider)
bei System.Windows.ResourceDictionary.SetDeferrableContent(DeferrableContent deferrableContent)
bei System.Windows.Baml2006.WpfSharedBamlSchemaContext.<Create_BamlProperty_ResourceDictionary_DeferrableContent>b__168(Object target, Object value)
bei System.Windows.Baml2006.WpfKnownMemberInvoker.SetValue(Object instance, Object value)
bei MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetValue(XamlMember member, Object obj, Object value)
bei MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetValue(Object inst, XamlMember property, Object value)

If i turn on all Exception it says:
The assembly with display name 'System.Activities.Presentation.classic' failed to load in the 'Load' binding context of the AppDomain with ID 1. The cause of the failure was: System.IO.FileNotFoundException: Could not load file or assembly 'System.Activities.Presentation.classic, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Das System kann die angegebene Datei nicht finden.



Details
Sign in to post a comment.
Posted by Microsoft on 4/1/2010 at 10:29 AM
Hi, and thanks for your feedback. We've tested this on a later release and we are not seeing this repro. We did have a couple of bugs in this area that we did fix and it appears that it handles this case as well.

Please let me know if you ahve more questions.

matt winkler, pm wf designer
mwinkle @ microsoft.com
Posted by Microsoft on 3/1/2010 at 1:07 PM
Thank you for using .NET Framework 4.0 providing feedback on the WCF and WF products. This bug is currently going to the feature team who will directly investigate the issue you are reporting. We are very eager to receive this feedback and will take care to address your input. Feel free to provide comments on the Connect site if you have concerns on the resolution of this bug.

Thanks,
Scott
Posted by Microsoft on 2/23/2010 at 7:37 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you
Posted by Microsoft on 2/23/2010 at 7:03 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.