PureEngage On-Premises

 View Only

Sign Up

  • 1.  WDE 8.5 Custom Plugin AssemblyInfo format to guarantee minor build compatibility

    Posted 06-30-2015 16:18
    Hi Everybody,

    I built some custom plugin, as you saw if you read this forum   [;D] , and during my build phase the WDE had 3 minor update, from the 8.5.104.17b1 passing by the 8.5.106.22b1 to arrive to the 8.5.108.11b1 and all the time i had to recompile my plugin and release them coz of the following problem:

    ERROR dows.LoginController - An error occurs while initializing the module MyModule. Check the <modules> and <tasks> sections in the app.exe.config file
    Microsoft.Practices.Composite.Modularity.ModuleLoadException: Failed to load module MyModulefrom assembly Genesyslab.Desktop.Modules.MyModule, Version=8.5.104.17, Culture=neutral, PublicKeyToken=null. Error was:...

    So Recompiling and updating the class AssemblyInfo.cs with the correct build version of the WDE everything restart to work fine...

    I'm sure that it's impossible that i have to rebuild the pluings for each minor update of the WDE it should be my mistake...but which one?

    Can you help me?

    Thanks,

    Cheers,

    Charles


  • 2.  RE: WDE 8.5 Custom Plugin AssemblyInfo format to guarantee minor build compatibility

    Posted 06-30-2015 18:05
    Carlo,

    Given this issue is custom and fairly detailed, I'd recommend opening case with Customer Care.

    Thanks,
    Roger Farr
    Genesys Customer care


  • 3.  RE: WDE 8.5 Custom Plugin AssemblyInfo format to guarantee minor build compatibility

    Posted 10-09-2015 07:49
    Hi,
    I don't know why you are so surprised. imagine that you have version 104 with interface with one method. you use this interface for you customisation. genesys in version 105 add second method ... so you customisation is not valid and you have to reference new version of dll where the interface is.
    genesys is not interface ... genesys wde is still under development so you customise live organism.
    in you case there is no reason why still upgrade to new version ... on project startup dwnload some stable version and customise it. durins some CHRs you can upgrade to new version and rebuild your customisation against new dlls.

    i guess this question is not for support, because its not a issue nor feature request


    Radek