Compiling .NET component that uses a non specific required version of a 3rd Party Vendor component
Posted
by Dan
on Stack Overflow
See other posts from Stack Overflow
or by Dan
Published on 2010-06-08T23:08:05Z
Indexed on
2010/06/08
23:12 UTC
Read the original article
Hit count: 352
If someone were to develop a .NET component that relied on non specific versions of a vendor DLL - let's say it worked with My3rdPartyComponent.dll which is a .NET assembly, but it didn't matter which version.
Some instances of classes found in this component would need to be passed into my component. Developers would reference my component dll but not have access to the source code.
Basically, I want to be able to require the user to pass in an instance of 3rdPartyComponent.MyClass to my component functions but I do not care if it's version 1.1, 2.2, 2.23.980, etc of the 3rd party dll.
Is there a way to do this while still typing the parameter I want to be passed in to my component? I don't want to use Object as the reference.
In my component project I could specify SpecificVersion=True on the assembly reference. Will this solve my problem or will there be other 'dll hell' issues to deal with that I am not seeing?
© Stack Overflow or respective owner
