1
Vote

Missing Assembly: Xceed.Wpf.Toolkit.Luna

description

I added Xceed Extended WPF Toolkit via Nuget and I get a "A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll" which when I looked into it, found that it was looking for Xceed.Wpf.Toolkit.Luna.

Everything seems to work without this assembly.

file attachments

comments

emartin wrote Mar 25, 2013 at 1:36 PM

Can you send me a sample app that reproduce the problem ?
Others has reported the problem but always ended with a "cannot reproduce" ...

cjb110 wrote Mar 25, 2013 at 2:07 PM

The attached project does it.

I started Visual Studio 2010 SP1 (on XP SP3), created new WPF Application. Went to Nuget and searched for Xceed, and downloaded the latest stable (1.9) release.

I was only using the Integer spinners so I copied that xaml from my original project.

When it loads, you get the First Chance exception (I noticed there's a slight delay, i.e. its not reported straight away).

Hope that helps!

emartin wrote Apr 19, 2013 at 3:24 PM

I've set up an Windows XP SP3 with VS2010 and I can't reproduce the problem.
  • I've run the provided solution and did not reproduce
  • I've created a fresh new WpfApplication,
  • Add reference to the Xceed.Wpf.Toolkit.dll and Xceed.Wpf.DataGrid dlls that were included in your zip file
  • Copy pasted the content of MainWindow.xaml in my App MainWindow.xaml
  • Pressed F5 and did not get the expection.
If you still reproduce the problem easily please provide any feedback.

cjb110 wrote Apr 19, 2013 at 9:10 PM

Ok, I'm out for a week, but will try it when I get back.

Will also try with 2012 to check that as well.

emartin wrote Apr 26, 2013 at 1:00 PM

Theses issues can be considered as duplicates:
Issue 18971
Issue 19506

emartin wrote Apr 26, 2013 at 1:07 PM

In v2.0, I've made some changes to the code that will hopefully fix that issue.
I could not reproduce the issue, so this is a pure guess.

You are encouraged to describe your environment and the step to re-produce the issue. Unfortunately, many people that once felt on this issue fix the problem by clearing and recompiling.

serj1980 wrote Jun 10, 2013 at 1:37 PM

I investigate this on my environment. If I comment DockingManager control, error not occured. If I uncomment DockingManager and comment all internal for DockingManager controls (leave empty DockingManager), error occured.
I moved from original AvalonDock to xceed. With original assembly I don't have this error.

HeinA wrote Jul 31, 2013 at 11:55 AM

Happening to me aswell

emartin wrote Dec 5, 2013 at 3:01 PM

Another issue here

BoucherS wrote Mar 28 at 4:28 PM