.net 2.0 accessing .net 40 assembly thru binding

I have .net 2.0 application (third party) is window's application(DLL's) -> future plans to move to .net 4.0

.net 2.0 my application(web service /asmx) interacts with above windows application (DLL) . these DLL's are updated frequently every 2 months, so direct reference will not work hence my web service has bindings set in web config file, here is the example below

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
     开发者_StackOverflow社区   <assemblyIdentity name="ABCProcesses" publicKeyToken="21f532fe36bf9cd6" culture="neutral" />
        <bindingRedirect oldVersion="1.0.0.0-65535.65535.65535.65535 " newVersion="3.128.20.0" />
        <codeBase version="3.128.20.0" href="file:///C:\Program Files\APPS\DLL\ABCProcesses.dll" />
      </dependentAssembly></runtime>

Every time the DLL versions are changed i have to update my config file with new version number.

Now my question is

if the above .net 2.0 windows application(third party DLL) is moved to .net 4.0 windows application(DLL), will this effect my net2.0 web service accessing the DLL's or will i be forced to move to .net 4.0 WCF ?

You can't reference a .NET 4.0 assembly from 2.0, you would need to upgrade as well or hope that the vendor continues to maintain the 2.0 version as well.