|
I found something out about VS2012 and .Net 4.5 last night - If you create a class library in a solution, and try to add a reference to that class library in a WPF project, the compiler will generate an error unless the class library contains a reference to WindowsBase, even if it doesn't utilize anything inside WindowsBase. The same thing does NOT happen in VS2010.
WTF, over?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
On the surface, it works fine for me.
Got the exact steps to reproduce??
|
|
|
|
|
Create a new WPF app
Add a class library
Reference that class library in your WPF app
I was getting a compiler error about setting a DependencyObject in the class library when I tried to set a DateTime object's value.
I think it's a bug, because it was working fine earlier. It's a rather extensive solution (my MediaAtHome project), so posting bits and pieces of it to try to help someone duplicate the problem isn't viable. It's happened to me twice though...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
I've tried everything I can to try and replicate the problem, but failed.
I'm thinking it's got to be something specific to your project causing VS to bust a nut on it.
|
|
|
|
|
Have you seen the new type of class library? I think it's called something like "Portable Class Library". It's supposed to work across all the different projects that didn't play nicely before (Silverlight, XNA, maybe WPF).
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
