visual studio 2010 - Multi targeting hell and changing project defaults -


ok. going little crazy today wpf project. i'm using vs2010 .net 4.0 , added simple reference project in solution, added member variable of 1 of referenced types , tried compile. nothing. well, something. did not recognize type @ all.

i verified @ namespace using statement. intellisense seemed it. in fact, visual studio content let me browse class via go definition function.

some of reading know is, thought going crazy.

the wpf project defaults client profile, while other projects targeting full .net 4.0. had warnings turned off (stupid), wasn't seeing warning message client profile mismatch.

does else think it's stupid have wpf projects default client profile targeting, while rest of projects default targeting full .net 4.0?

...which leads me question. possible change default, scenario doesn't happen again? target 1 platform or other.

many project types in vs2010 target client profile. ms making bigger push time around 4.0 client profile take hold (the 3.5 client profile largely ignored).

for it's worth, profile project type targets default defined in template, , easy change if desire ([vs root]\common7\ide\projecttemplates , alter targetframeworkprofile element inside csproj files inside templates see fit). don't recommend though.

generally speaking, inelegant may be, think have used idea client profile more prominent , more aware of work vs2010


Comments

Popular posts from this blog

javascript - Enclosure Memory Copies -

php - Replacing tags in braces, even nested tags, with regex -