.NET 4.0 and WPFToolkit VSM namespace ambiguity

Jun 15, 2010 at 6:20 PM

Hi, I've  recently added WPFToolkit reference to a WPF .NET 4.0 project. Now I  am getting namespace collisions for VisualStateManager as it exists in .NET 4.0 (PresentationFramework) and WPFToolkit
Does anyone know a quick fix around instead of removing VSM and rebuilding the toolkit.





Jun 16, 2010 at 6:33 AM

Hi Xoma,


I had the exact same problem, unfortunately the only way to work around it for me was to use the system namespace.

What happened here is that the toolkit was merged into .net 4.0 release and I think the later versions of the toolkit have changed the namespaces.