Ambiguous references in VS 2010

Question

Trying to upgrade a solution from 2008 to 2010. And I suddenly get a lot of ambiguous reference errors compiling in VS 2010.

It works fine in 2008. Is VS 2010 more strict regarding the using directives?

Answer 1

I had a similar issue.

I dont think it is stricter, but more a coincidences of the newer framework now having the same class name I was using in the dlls referenced, either things were moved or there was some new development to existing dlls.

It took some time to fix the entire project, but the ways around it I found were:

To use either define the full location of the classes

or

define an alias:

using CompanyMagic = Core.Company.Magic;