Geek Answers Handbook

Why is VS.NET trying to enable Microsoft.Windows.Design.Extensibility for WPF and ClickOnce?

I built a WPF application in VS.NET 2008 using ClickOnce deployment. It worked perfectly on any machine on which VS.NET was installed, but my business users received an error message: "The application could not be installed or started. The application requires Microsoft.Windows to be installed on Microsoft Windows 2000 .Design.Extensibility Version 3.5.0.0 Global Assembly Cache (GAC). "

I was surprised to find that this DLL is not part of the standard client installation of .NET 3.5 SP1, but for some reason my application thought it was necessary. I checked the Publish tab for the project, and that turned out to be a prerequisite.

Oddly enough, I was able to simply delete this (and all other Microsoft.Windows.Design. * .Dll files), and it just worked everywhere. I completely removed them from my project, and everything was in order.

Can someone explain why the VS.NET 2008 project wizard forced them to be included in the project, and more importantly, why ClickOnce thought they had to be on the client machine to run?

It's just a matter of curiosity, but I'm sure I'm not the first to bite him. I hope this post at least saves someone else from a headache.

+4
source share
4 answers

Try to remove all links to * .Design.dll. In my case, it was WPFToolkit.Design.dll.

+6
source

This is old and the OP is gone, but I ran into it today, so I decided to mention that my solution removed the link to one of the WPFToolkit links that ends in .Design .

I referred to System.Windows.Controls.Input.Toolkit , but also had a link to System.Windows.Controls.Input.Toolkit.Design , which should not have been. They removed it, and everything was right with the world again.

+3
source

This describes how to find the code that loads the assembly:

http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/755272f6-0e79-4a6d-ae50-4412d0f2bc4c

+1
source

I found that I am using the SelectionCommands.Clear property, which is inside the Microsoft.Windows.Design.Interaction namespace inside the dll dll version of Microsoft.Windows.Design.Extensibility.

It seems that this DLL is not included in the .NET 3.5 installation.

0
source

More articles:


All Articles