[Firebird-net-provider] Getting an assembly to accept more than one provider version?

2011-03-07 Thread Kjell Rilbe
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

Re: [Firebird-net-provider] Getting an assembly to accept more than one provider version?

2011-03-07 Thread Ivan Arabadzhiev
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

Re: [Firebird-net-provider] Getting an assembly to accept more than one provider version?

2011-03-07 Thread Daniel Rail
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

Re: [Firebird-net-provider] Getting an assembly to accept more than one provider version?

2011-03-07 Thread Kjell Rilbe
Den 2011-03-07 15:14 skrev Daniel Rail såhär: Is there any way I can get the other assembly to accept the newer provider assembly without having to rebuild it from sources? Add this to your application's config file, under the configuration section: runtime assemblyBinding