Hi, Don`t know if it helps much, but I`ve never done it myself. You should be able to achieve something with reflection (dynamic loading, matching only runtime version), but .NET itself is based on some ideas (including "no more dll nightmares"), so I don`t think you`ll find a right-click way to do this ...
> Hi, > > Maybe this is more a .Net question than a FB provider question, but I > think it may be of interest to most people using the provider. > > My problem is that I have an assembly that in the sources specifies > "SpecificVersion = false" for the Fb provider assembly, i.e. it should > accept any version of the provider. > > But the built assembly (the dll) becomes bound to the provider version > present when it is compiled, in my case 2.5.0.0. > > Now, I'd like to upgrade to the latest provider version (2.5.2.0). > > Is there any way I can get the other assembly to accept the newer > provider assembly without having to rebuild it from sources? > > If you reply with RTFM I'd appreciate pointers to relevant docs. > > Regards, > Kjell -- Sanity is a sin! http://www.thevenusproject.com/images/stories/venusfaq.pdf ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
