Industry Extensions Alternative Path?

If you have Industry Extensions Installed and you upgrade from .14 to .18 for example. Most of the files stay in-tact.

Except these (for example):

** EpicorERP/Erp/BO/MessageLogging.svc**
** EpicorERP/Erp/BO/IEXLicence.svc**
** EpicorERP/Erp/Rpt/IexPositivePay.svc**
** EpicorERP/Erp/BO/IexMicConfiguration.svc**

Because those folders get rebuild during a “Deploy”.

Is there an Alternative Folder I can place the .svc files in so I dont have to back them up and re-add them during every minor upgrade. Something similar to the CSG Folder, which stays in-tact.

Can you just set those files to read-only?

I was going to edit my post, my typing was faster than my brain. It looks like they do stay in-tact, thats good.

I usually Re-Install the Industry Extensions and I want to avoid doing that every upgrade. So the files are all there… Just any of the Industry Extension Entry Screens get this error:

Yet tst-cm-app1\EpicorERP\Erp\BO\MessageLogging.svc exist, untouched. Looking at its .cab file dissecting it, there is nothing it does besides extracting Client Side DLLs and Server Side DLLs.

I’ll check the Server a bit and worst case scenarion - I will do as I always have done… Reinstall the Industry Extensions from Scratch.

Not sure why I was told that I have to Reinstall IEx Extensions despite them rarely changing… It looks like all you have to do is just modify your web.config and add back the reference to the CSG Folder and it works.

add key=“AssemblyFileSystem” value=“E:\Website\EpicorERP\Server\CSG;E:\Website\EpicorERP\Server\Assemblies” />

Glad you are running. We have a few stories along these lines in the vNext timeframe around improving migration / upgrade handling. Adding this to my notes on the effort.

1 Like

Bart:

During each (minor) upgrade I have to add back the following.

Server Side

web.config
add key=“AssemblyFileSystem” value=“**E:\Website\EpicorERP\Server\CSG;**E:\Website\EpicorERP\Server\Assemblies” />

Client Deployment

Client EpicorERP.sysconfig
all of my customizations></customizations back
Example:
customization name=“IEX-FrameworkClient” directoryName=“CSG” version=“20170511” deploymentType=“ZIP” />

In order to avoid needing to update the web.config file, you can place this path here in the app server config.

3 Likes

If that Custom Directory setting is not carrying over then that’s a ticket please :slight_smile: