Just getting going in WPF, I'm sure it's something simple -- don't assume that I'm down the right road. Using VS 2010, targeting .Net 4 Client.
I've created a BaseWindow class which has a property to hold the logged-in Employee, so each window in my app can get to it easily. This Employee object lives in a "core" dll outside of my WPF application (but I have a reference to it), and the BaseWindow
lives right in my WPF app. BaseWindow inherits from System.Windows.Window.
The problem is, when I make a window inherit from BaseWindow (i.e., change the Window tag to "local:BaseWindow" and add a "local" namespace to myself, the designer starts throwing out errors that it can't find the "core" dll. I don't understand, as the
"core" dll is easily available; compilation/testing doesn't have any trouble finding it. Also, there's
no place in the window the designer needs to reference that dll. The "core" dll is
strictly domain-layer objects, nothing to render out of that.
By switching my window's tag from "Window" to "local:BaseWindow", rebuilding, and reloading the designer, I'm pretty confident in my discovery. Every time my Window is just a Window, the designer works great; when it's a BaseWindow, can't load the
View Complete Post