VS 2005 Reference Problem With Version Number

I have successfully compiled a program that references several dlls. The program runs fine in the IDE but when installed I get the error below that indicates a version problem. The referenced dll has version 1.2.1.0 while the calling dll is looking for version 1.2.0.0. Okay, I deleted the reference in the calling dll and then put in a reference to the correct dll. When the reference is added, its properties show version 1.2.0.0 but its manifest shows version 1.2.1.0. I also removed and replaced the reference to the dll in the main program and the same thing happens. So, what can I do to get the version numbers in agreement? Note that the calling dll has Specific Version set to False but that doesn't seem to make a difference. The main program is VB and the calling dll is C#, but that should be immaterial. The called dll is skybound.visualstyles.dll.
LVL 1
rkulpAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

psdavisCommented:
Do you have your assembly version hard coded, or are you using the * feature?
[assembly: AssemblyVersion ( "1.5.4.0057" )]
or
[assembly: AssemblyVersion ( "1.5.*" )] ?
0
rkulpAuthor Commented:
psdavis,

Thanks for your quick response. The main program is hard coded as 1.0.0.0 and the tri-state tree view dll is coded as 1.0.*. The skybound.visualstyles.dll manifest shows 1.2.1.0 but I don't know if that indicates it was hard coded. The problem is with skybound.visualstyles.dll which I cannot change.
0
rkulpAuthor Commented:
I solved the problem. As usual, the error messages are multi-layered and sometimes are misleading. After removing the two dlls and recompiling the tristatetreeview I got down to the true problem -- a mismatched 32-bit vs 64-bit assembly. Once that was resolved by recompiling the main program to be x86 only, the program worked.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
psdavisCommented:
No objection
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.