Infragistics Runtime

[SBarnes]

Hi Guys,

Is it safe to assume that all of the Infragistics DLLs / run time files are deployed with Jiwa, by this what I am asking is it OK to use any of the controls on a form in a plugin even if one is not used by Jiwa itself?

[Scott.Pearce]

No. We do not explicitly deploy *all* of the Infragistics libraries, only the ones that are referenced by the Jiwa assemblies.

[Mike.Sheen]

is it OK to use any of the controls on a form in a plugin even if one is not used by Jiwa itself?

As Scott already mentioned, we deploy what Jiwa needs - if you come across a control which depends on an Assembly we don't deploy, let us know and we'll add it to the deployment for the next release.

As a work-around you can add any missing Assemblies you require as an embedded reference to the plugin - when the plugin is compiled at Jiwa login time we'll deploy the assembly to the right place and at it to the references of the plugin - it *should* just work.

Mike

[SBarnes]

Hi Guys

Thanks to both of you for the update.

Mike I had considered the embedded reference as an alternative, my only question on this is what would occur if the files then became part of the normal run time, would there be a danger of files being overwritten and then removed that could cause Jiwa not to start, what I guess I am asking is do the files go in the Jiwa program directory or else where at deployment as could there be an issue if two plugins had the same embedded reference?

[Mike.Sheen]

Mike I had considered the embedded reference as an alternative, my only question on this is what would occur if the files then became part of the normal run time, would there be a danger of files being overwritten and then removed that could cause Jiwa not to start, what I guess I am asking is do the files go in the Jiwa program directory or else where at deployment as could there be an issue if two plugins had the same embedded reference?

I don't believe it will cause an issue - it's been a while since I tested that scenario (I remember testing that when we first introduced embedded references).

An embedded reference is deployed to the ProgramData\Jiwa Financials\Jiwa 7\Plugins\... folder - and the assembly is then loaded when the plugin is loaded at logon time - if the assembly is already present in the application domain (for instance, Jiwa has already loaded it) then the .NET assembly resolver (Fusion) will ignore the attempt to load it as it is already present in the current application domain.

I'm fairly confident it won't cause an issue for you.

Mike

[SBarnes]

Thanks