tag:blogger.com,1999:blog-8338234734413867615.post1495405329333462292..comments2013-03-23T18:03:42.660-07:00Comments on Common Knowledge: The Mystery of mscorlibPaul Keisterhttp://www.blogger.com/profile/03500839803346226676noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8338234734413867615.post-63198647544480819312012-09-04T13:35:37.384-07:002012-09-04T13:35:37.384-07:00man I think I love you, this is valuable info!man I think I love you, this is valuable info!Miloxhttps://www.blogger.com/profile/00737195285620968857noreply@blogger.comtag:blogger.com,1999:blog-8338234734413867615.post-42747716395940645162012-08-18T22:42:50.058-07:002012-08-18T22:42:50.058-07:00I'm late to the party on this one, but I found...I'm late to the party on this one, but I found a different cause for this so thought I'd throw it out. After ripping out some hair I finally found my cause. I was looking at what it would take to switch out my code base from 3.5 to 4.0. It proved to cause a lot of problems so I switched back. Then it happened ... <br /><br />Turned out there is a directory for compiled MSIL in the framework\assembly directory and it had a bunch of listings for my project outputs. Once I deleted those my issue went away.<br /><br />Hope this helps some of you.Anonymoushttps://www.blogger.com/profile/03844303113198807571noreply@blogger.comtag:blogger.com,1999:blog-8338234734413867615.post-7704597904229252142011-04-21T14:01:54.778-07:002011-04-21T14:01:54.778-07:00Berend, it's good to know this was helpful, th...Berend, it's good to know this was helpful, thanks!Paul Keisterhttps://www.blogger.com/profile/03500839803346226676noreply@blogger.comtag:blogger.com,1999:blog-8338234734413867615.post-11597271436737843202011-03-07T22:44:32.684-08:002011-03-07T22:44:32.684-08:00Thanks so much for providing this solution. I have...Thanks so much for providing this solution. I have just upgraded a large set of projects from vs2008 to vs2010 and the spurious reference to mscorlib v4.0 was driving me nuts! Any dependent project that had .Net 2.0 output stopped compiling, because vs2010 incorrectly claimed that the referred projects targeted .Net 4.0.<br /><br />Best regards,<br /><br />Berend EngelbrechtUnknownhttps://www.blogger.com/profile/06489051360289535281noreply@blogger.com