1

Topic: Question about bindingredirect

Greetings to all! In Windows Server 2012 R2 is certain system DLL. This DLL lives in GAC and has version 6.3.0.0. In Windows Server 2016 same DLL I have version 10.0.0.0 In studio added the reference on DLL the old version. The program remarkably works on old C, but refuses to be launched on new (since cannot find DLL version 6.3.0.0). In app.config I added bindingRedirect. Here so: <dependentAssembly> <assemblyIdentity name = "some" publicKeyToken = "31bf3856ad364e35"/> <bindingRedirect oldVersion = "6.3.0.0-6.3.0.0" newVersion = "10.0.0.0"/> </dependentAssembly> Now the program is remarkably launched on the new version of OS, but it refuses on old As though to solve (well except delivery of 2 versions app.config depending on OS)? In advance thanks

2

Re: Question about bindingredirect

Hello, Lonely Dog, you wrote: LD> Greetings to all! LD> in Windows Server 2012 R2 is certain system DLL. This DLL lives in GAC and has version 6.3.0.0. LD> In Windows Server 2016 same DLL I have version 10.0.0.0 LD> In studio added the reference on DLL the old version. The program remarkably works on old C, but refuses to be launched on new (since cannot find DLL version 6.3.0.0). In app.config I added bindingRedirect. Here so: LD> LD> <dependentAssembly> LD> <assemblyIdentity name = "some" publicKeyToken = "31bf3856ad364e35"/> LD> <bindingRedirect oldVersion = "6.3.0.0-6.3.0.0" newVersion = "10.0.0.0"/> LD> </dependentAssembly> LD> LD> Now the program is remarkably launched on the new version of OS, but it refuses on old LD> As though to solve (well except delivery of 2 versions app.config depending on OS)? LD> In advance thanks In gac like can be added at once two versions - 6.3.0.0 and 10.0.0.0. Register at once two versions.

3

Re: Question about bindingredirect

Hello, Sharov, you wrote: S> In gac like it is possible to add at once two versions - 6.3.0.0 and 10.0.0.0. Register at once two versions. So it is not mine DLL, it DLL from OS. From Microsoft.

4

Re: Question about bindingredirect

Hello, Lonely Dog, you wrote: LD> Hello, Sharov, you wrote: S>> In gac like it is possible to add at once two versions - 6.3.0.0 and 10.0.0.0. Register at once two versions. LD> so it is not mine DLL, it DLL from OS. From Microsoft. Also what it changes?

5

Re: Question about bindingredirect

Hello, Sharov, you wrote: S> Hello, Lonely Dog, you wrote: LD>> Hello, Sharov, you wrote: S>>> In gac like it is possible to add at once two versions - 6.3.0.0 and 10.0.0.0. Register at once two versions. LD>> so it is not mine DLL, it DLL from OS. From Microsoft. S> also what it changes? So and as where to register that? On server 2016 there is no version 6.3.0.0 (it in server 2012 r2)

6

Re: Question about bindingredirect

Hello, Lonely Dog, you wrote: LD> Hello, Sharov, you wrote: S>> Hello, Lonely Dog, you wrote: LD>>> Hello, Sharov, you wrote: S>>>> In gac like it is possible to add at once two versions - 6.3.0.0 and 10.0.0.0. Register at once two versions. LD>>> so it is not mine DLL, it DLL from OS. From Microsoft. S>> also what it changes? LD> so and as where to register that? LD> On server 2016 there is no version 6.3.0.0 (it in server 2012 r2) Possibly on 2012 version 10.0.0.0  it not to turn out, and here on 2016 6.3.0.0 quite. Then everywhere it is possible 6.3.0.0 to use.

7

Re: Question about bindingredirect

Hello, Sharov, you wrote: S> Hello, Lonely Dog, you wrote: LD>> Hello, Sharov, you wrote: S>>> Hello, Lonely Dog, you wrote: LD>>>> Hello, Sharov, you wrote: S>>>>> In gac like it is possible to add at once two versions - 6.3.0.0 and 10.0.0.0. Register at once two versions. LD>>>> so it is not mine DLL, it DLL from OS. From Microsoft. S>>> also what it changes? LD>> so and as where to register that? LD>> On server 2016 there is no version 6.3.0.0 (it in server 2012 r2) S> Possibly on 2012 version 10.0.0.0  it not to turn out, and here on 2016 6.3.0.0 quite. Then everywhere it is possible 6.3.0.0 to use. You mean to deliver as a part of product DLL from Microsoft (a system part) and to put it on 2016?

8

Re: Question about bindingredirect

Hello, Lonely Dog, you wrote: S>> it is probable  not to turn out on 2012 version 10.0.0.0, and here on 2016 6.3.0.0 quite. Then everywhere it is possible 6.3.0.0 to use. LD> you mean to deliver as a part of product DLL from Microsoft (a system part) and to put it on 2016? If it earns, yes. Well or hands app.config correct, on the fly at installation somehow it is possible to manage. Or most  in application demanded library.

9

Re: Question about bindingredirect

Hello, Lonely Dog, you wrote: LD> As though it to solve (well except delivery of 2 versions app.config depending on OS)? To correct at start or to resolve through assembly load event. But I would not suffer and would make two  (with slowcheetach elementarily). It is absolutely logical, actually. Is OS-dependent , but reverse compatibility it is not provided, what else variants? If there will be an assembly name - it is possible to try to find the ready decision.

10

Re: Question about bindingredirect

Hello, Lonely Dog, you wrote: LD> Greetings to all! LD> in Windows Server 2012 R2 is certain system DLL. This DLL lives in GAC and has version 6.3.0.0. LD> In Windows Server 2016 same DLL has version 10.0.0.0 LD> As though it to solve (well except delivery of 2 versions app.config depending on OS)? I would consider a variant simply to include it in a product. Because it is not enough  that changed in different versions. Well or if there is a hope that it will be always compatible, separate configs.

11

Re: Question about bindingredirect

Hello, vmpire, you wrote: V> I would consider a variant simply to include it in a product. Because it is not enough  that changed in different versions. V> well or if there is a hope that it will be always compatible, separate configs. In any time. It OS-specific a part, at attempt thrust it in the alien version of OS can be surprises and fireworks, and not at once, and on arrival of the next update from MS. Well and absolutely boring variant - it refuses to work stupidly at once, and all here (because of exterior dependences).