WDE 8.5 Custom Plugin AssemblyInfo format to guarantee minor build compatibility

[CarloACN]

Hi Everybody,

I built some custom plugin, as you saw if you read this forum  , 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:

[quote]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:...
[/quote]

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

[abudwill]

Hi Charles,

I wanted to confirm that I have experienced the same behavior. I have never tried to work around it since we stay on pretty consistent IWS versions. Genesys agent scripting uses an iws plugin (dll file) and it seems to work with multiple versions of IWS.

I don't have an answer for you if you do come up with a solution please be sure to share.

[CarloACN]

Thanks for the support,

Unfortunatelly i'm still on this problem...as soon as my customer change IWS version i have to rebuild all my ccustom module...

[i]15-07-09 12:31:59.512 [            1] ERROR dows.LoginController - An error occurs while initializing the module ExtensionSampleFollowUpModule. Check the <modules> and <tasks> sections in the app.exe.config file
Microsoft.Practices.Composite.Modularity.ModuleLoadException: Failed to load module ExtensionSampleFollowUpModule from assembly Genesyslab.Desktop.Modules.ExtensionSampleFollowUp, Version=1.0.1.0, Culture=neutral, PublicKeyToken=null. Error was:
Resolution of the dependency failed, type = "Genesyslab.Desktop.Modules.ExtensionSampleFollowUp.ExtensionSampleFollowUpModule", name = "". Exception message is: The current build operation (build key Build Key[Genesyslab.Desktop.Modules.ExtensionSampleFollowUp.ExtensionSampleFollowUpModule, null]) failed: Could not load file or assembly 'Genesyslab.Enterprise.Model, Version=8.5.108.5, Culture=neutral, PublicKeyToken=95e512acdb150ec7' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) (Strategy type BuildPlanStrategy, index 3) ---> Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "Genesyslab.Desktop.Modules.ExtensionSampleFollowUp.ExtensionSampleFollowUpModule", name = "". Exception message is: The current build operation (build key Build Key[Genesyslab.Desktop.Modules.ExtensionSampleFollowUp.ExtensionSampleFollowUpModule, null]) failed: Could not load file or assembly 'Genesyslab.Enterprise.Model, Version=8.5.108.5, Culture=neutral, PublicKeyToken=95e512acdb150ec7' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) (Strategy type BuildPlanStrategy, index 3) ---> Microsoft.Practices.ObjectBuilder2.BuildFailedException: The current build operation (build key Build Key[Genesyslab.Desktop.Modules.ExtensionSampleFollowUp.ExtensionSampleFollowUpModule, null]) failed: Could not load file or assembly 'Genesyslab.Enterprise.Model, Version=8.5.108.5, Culture=neutral, PublicKeyToken=95e512acdb150ec7' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) (Strategy type BuildPlanStrategy, index 3) ---> System.IO.FileLoadException: Could not load file or assembly 'Genesyslab.Enterprise.Model, Version=8.5.108.5, Culture=neutral, PublicKeyToken=95e512acdb150ec7' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
  at Genesyslab.Desktop.Modules.ExtensionSampleFollowUp.ExtensionSampleFollowUpModule..ctor(IObjectContainer container, IViewManager viewManager, ICommandManager commandManager, IInteractionManager interactionManager, IConfigurationService configurationService, IAgent agent)
  at BuildUp_Genesyslab.Desktop.Modules.ExtensionSampleFollowUp.ExtensionSampleFollowUpModule(IBuilderContext )
  at Microsoft.Practices.ObjectBuilder2.DynamicMethodBuildPlan.BuildUp(IBuilderContext context)[/i]

[Kubig]

Do you encounter this issue with all custom modules? I have developed a few modules and never have encountered similiar issue.

[cavagnaro]

I think has to do the way your plug-in references the IWS libraries... I haven't had such experience yet so maybe Kubig can share how he do it and also you so you can compare both methods.

Enviado de meu C6602 usando Tapatalk

[abudwill]

Very interested in Kubigs feedback.  I have encountered this every time we upgrade IWS as well - I have to rebuild my modules while referencing the DLLs from the new version of IWS that is to be used.