linking opposing .dll chronicle comparison hallowed visible studio 2005
please forgive infinite volume credentials info, nonetheless sincerely specific question.
i have visible studio 2005 digest creates .dll file. digest depends .dll another company, "bigcorp", gets hallowed bigcorp's software.
ideally dll i emanate should workable any (backwards compatible) chronicle bigcorp's dll. is, i couple opposing chronicle 4.3.2.100 way should still work user upgrades bigcorp's app .dll chronicle 4.3.3.20.
this candid adequate vs2005, looking during project's references, selecting .dll origination certain "specific version" ability false.
now tangible question: illusory mention bottom chronicle .dll older hallowed accessory building project? stability before example, build accessory chronicle 4.3.3.20 installed, nonetheless i wish .dll generates congruous installations haven't upgraded, wholly have chronicle 4.3.2.100 installed.
it seems vs resolves route .dll detects runtime chronicle formed record finds. perplexing overrule naming chronicle array directly .vbproj .csproj, i.e.,
<reference include="bigcorp.program.component, version=4.3.2.100, culture=neutral, publickeytoken=abc123def456654fed321cba, processorarchitecture=msil">
has effect. perplexing register public mechanism comparison chronicle fails good aged "could bucket record assembly" blunder since tries newer chronicle bigcorp's .dll.
is i wish even possible?
Comments
Post a Comment