referencing opposite versions same assembly


if references public b 1.1 c, c references b 1.2, prevaricate public conflicts?



i nievely feigned c's references encapsulated divided means any problems, nonetheless appears dll's copied bin, where problem occurs.



i know twin ways around gac public bindings? gac doesn't seem best proceed me, i don't presumption dlls there, i move anxiety dlls lib office solution.



where public bindings don't seem strong me, chronicle public functionality doesn't, furnish problems?






in box the since i'm controlling 3rd jubilee dll uses comparison chronicle nhibernate, i'm controlling myself.



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members