4 Replies

#1 − How do I update the version


Great article.

I am having the problem described above where the underlying component is version, but the designer is trying to load Any ideas on how to force VS to load the current version? I used to be able to simply rebuild the underlying assembly and the problem would be solved, but since I moved to 64bit, this strategy no longer seems to work.



First I would try deleting ALL compiled binaries in all bin and obj directories (for all your projects). Then do a rebuild and maybe restart VS.

We created Windows batchfiles to do this when VS bot in trouble again.

#3 − @trpugh


You’ll have to dig out any references to the wrong version number. First, do as Marc says: get rid of all compiled assemblies that Visual Studio may be using. Also make sure that VS can’t find the wrong version in the GAC because it might be grabbing that one as well. Restarting VS is also a good idea as it sometimes retains caches references in memory.

If none of that works, then you have an explicit reference to the assembly using the old version number somewhere in your solution. Check project files for references with that version number; check those pesky license.licx files (you can just delete the offending line from those).

Good luck! And be reassured, there’s always some logical reason for the assembly mismatch. It’s just sometimes tedious to find.