I have a project which references another project’s dll. They both were in .net framework 2.0.
So upgraded both to 3.5, but when I go to reference for second project(the one referencing the first project) it still says on properties runtime version 2.0, even though I deleted the reference and readded.
-
How would I determine if the referenced dll is the upgraded one, before deploying to server where it has version 2.0?
-
I don’t want to delete all files in server and deploy, after upgrading do I need to check the config files are referencing same dlls and deploy published files or it needs replacing all together?
.Net 3.5 and .Net 2 both run on version 2 of the CLR, so the runtime version of the ‘old’ and ‘upgraded’ assemblies will not change.
As for finding out whether it is ‘upgraded’, I would recommend using ILDASM to see which version of mscorlib is referenced.
However, the answers to this SO question provide a few alternatives.