arjI got the following exception on one of our installed machines:
The invocation of the constructor on type 'wyDay.Controls.AutomaticUpdater' that matches the specified binding constraints threw an exception.
The inner exception is:
Could not load file or assembly 'WindowsFormsIntegration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Can not find file specified.
Inner backtrace: at wyDay.Controls.AutomaticUpdater..ctor() at System.Xaml.Schema.XamlTypeInvoker.DefaultCtorXamlActivator.CallCtorDelegate(XamlTypeInvoker type) at System.Xaml.Schema.XamlTypeInvoker.CreateInstance(Object[] arguments) at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CreateInstance(XamlType xamlType, Object[] args)
Why is it trying to load WindowsForms? This is a WPF app, I don't reference Windows Forms in my app.
This is Windows 7 64 bit.
Thanks
Yes, the WPF version of the AutomaticUpdater uses the "WindowsFormsIntegration" assembly. But this exception shouldn't happen -- the "WindowsFormsIntegration" assembly should exist on the machine (it's part of the default .NET 4.0 installation).
Is there any chance the user is using a beta (or release candidate) version of .NET framework 4.0? Did they modify the .dlls? Try uninstalling & reinstalling .NET Framework 4.0.
arjAha. I've been optimizing the startup time of my application, and one of the bigger components was removing windows forms as it's quite a big dll. I have just quickly looked at the source of AutomaticUpdater and it seems that Windows.Forms is quite deeply integrated 😉
I don't have any chance of getting in contact with the user, this info is just from automatic crash reports. It of course only happens very few machines, so nothing big, but still quite annoying.
Thanks for your input Sam!
