Hi,
The DLL needs to be in the Epicor905\Client folder on the client PC.
I have never been able to get it to work with the Global Assembly Cache which
would have been a bonus.
If you need to deploy the dll then copy it to the Custom folder on the
server Epicor905\Custom\....\<Country>\Client folder just check the
path we have country specific functionality so our path is slightly
different. Then what you can do is run the utility in the
Epicor905\utilities folder for updating the config files. (I’m doing this
for memory and don’t have a server in front of me so forgive me for the rough
instruction)
Run the exe and it will prompt you for your config file location on your
server copy method and version. The version number will be something like
9.05.701.00. Just increment the .00 to the next number eg .01 You
can find the actual value that gets changed in the config file under
customizations I recall. I always take a look in the config file to make
sure I am grabbing the next number. It would be nice if the tool could
work that out. Anyway once you click ok it will update the customisation
version number in all of the config files.
The next time the user logs in provide their shortcut is forced not to
update (-skip flag) it will check its customisation version against the config
file in the server and if it is less than the server version it will perform and
update and grab the files from the customisation folder. Deploying the
file nicely. I use it for hot fixes and once offs as it allows me to
create a backup copy of the dll I am overwriting and it sends that to the
client.
Hope you find the information useful.
Cheers
Simon Hall
