I'm writing a WPF app using VS2013. I used NuGet to add the WPF Extended toolkit to my app. At home everything works as expected, but at work, weird stuff happens.
The project references are not showing an error, and the xmlns entry (that was automatically added to the XAML when I added a given control for the xceed toolkit) is not showing an error, but everywhere in the XAML that I try to use a control from the toolkit, it says the control doesn't exist in the namespace. However, if I instantiate one of the controls in the code-behind, everything is fine.
There's nothing weird about this solution (that I'm aware of). It's located on a local drive and the solution's projects (including the added nuget package) are all in a single folder, so I know when I transfer the code from work to home and back, all the code/projects/packages are contained in the ZIP file.
The code compiles with XAML errors, but runs fine.
Again, this does NOT happen at home, but DOES happen at work. WTF?
What I have tried:
I tried removing the package and adding it back, but that didn't have any affect.
I also tried removing all references to NUGET and just added the DLL references to my app. This also had no affect.
At work, we have problems accessing nuget.org. This is a network issue that can only be fixed by the IT idiots. Thinking this might be the issue, I cleared the package cache and turned off the nugget update on startup feature. That also had no affect.