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:
>
>
>
>
>
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
>> acce
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
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
Hi,
Sorry it took me that long, but I don`t tend to read the mail too often.
Don`t know Why you have problems with rebuilding, but including the
sources is quite literal in fact - Simply "Add existing files" to your
project. If memory serves, you should be able to drag`n`drop the sources
fo
