General question: C1Dll Versions at customers

General question: C1Dll Versions at customers

Posted by: andreas.kren on 18 November 2017, 4:20 pm EST

• 

  andreas.kren

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 18 November 2017, 4:20 pm EST

  Please apologize if this question does not belong here.

  Following scenario:

  Our main product consists of many (many) single programs laying in one directory at many customers. Receiving 4 major updates a year from C1 I have different C1 dll versions at different customers. Till now I have just copied the dll s in the main app directory (where all .exe and .dlls reside)

  Now I develop an extension for one customer with the new c1 dlls. I build the app, copy it to the customer, copy the new c1 dlls the app needs.

  Will the older apps (built with older c1 dlls) still run? If not, how can I solve this?

  Thank you and Regards

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 20 November 2017, 4:22 am EST

  Hi Andreas,

  we resolved this by adding some kind of project repository: in our project, we have a directory “Dependencies” which contains all C1 dlls. The project references point to these files. So we are version independent and can use different C1 version in our RELEASE/TEST/DEV branches.

  The only drawback: WinForms designer will use the installed DLLs. So, if you have different C1 dlls in your project, you first have to replace the installed files in “C:\Program Files (x86)\ComponentOne\WinForms Edition\bin\v4.0” with the files matching the project version.

  Hope this helps

  Wolfgang

• 

  andreas.kren

  • Post Options:
  • Link
    Copy

  Posted 20 November 2017, 2:11 pm EST

  Thank you. Solved it in the meantime via the app.config Files. When the customer gets an updated version I just copy a new app.config file to the customer. The different c1 dlls reside in different subdirs. (.\C1.2017.v1 .\C1.2017.v2 .\C1.2017.v3)
  
  Dunno if its very intelligent, but pragmatic as I am… it works

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">  
       <probing privatePath="C1.2017.v3"/>  
    </assemblyBinding>