Deployment of custom DLLs

We have several different config files that come non standard. The default.mfgsys should be updated at the least. And yes the version value it's near the top of the file
and should be numbers only. Ex. I'm technically on 9.05.700B2 but my version value is 9.05.700



Sent from my Atari 600



-----Original Message-----

From: Tom J. Christie [tchristie@…]

Received: Friday, 10 Jan 2014, 17:44

To: vantage@yahoogroups.com [vantage@yahoogroups.com]

Subject: RE: [Vantage] Deployment of custom DLLs



 

That sounds good. When you say you update “all my mfgsys files” which ones are you referring to? The ones located on the epicor905/client/config directory? Also, in the config file, what value are you changing, the “Version Value”?

 

I just want to make sure I have it right before I break it entirely and no one in the company can log in!

 

Tom Christie |  Information Technology Manager  |  AGM Container Controls, Inc.  |   tchristie@...  | t: 520.881.2130 ext 2176

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joshua Giese
Sent: Friday, January 10, 2014 4:34 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Deployment of custom DLLs

 

 

I usually add my new dll to the client folder with clientrelease.zip. add my new dll to the client folder in my server. Update all my mfgsys files with a new version number (I use a .A, .B, .C method begins the Epicor version number). Copy those mfgsys files into the clientrelease.zip. then wait for the magic to happen. The mismatch between the server version in the config file and the client config file will trigger an auto update.

Sent from my Atari 600

-----Original Message-----
From: Tom J. Christie [tchristie@...]
Received: Friday, 10 Jan 2014, 17:31
To: vantage@yahoogroups.com [vantage@yahoogroups.com]
Subject: [Vantage] Deployment of custom DLLs

 

I have seen some discussion on the board about how to deploy dlls to clients by placing the dlls in the epicorapp/epicor905/custom/client/ directory and then running a utility to up the revision on the server files so that the client gets repulled next time it gets run by a user.

 

I have been unable to find how exactly to do this. Does anyone have any documentation or suggestions on how to get this done. I really would prefer not to have to run around to all the computers with a USB drive…

 

Regards,

 

Tom Christie |  Information Technology Manager  |  AGM Container Controls, Inc.  |   tchristie@...  | t: 520.881.2130 ext 2176

 

I have seen some discussion on the board about how to deploy dlls to clients by placing the dlls in the epicorapp/epicor905/custom/client/ directory and then running a utility to up the revision on the server files so that the client gets repulled next time it gets run by a user.

 

I have been unable to find how exactly to do this. Does anyone have any documentation or suggestions on how to get this done. I really would prefer not to have to run around to all the computers with a USB drive…

 

Regards,

 

Tom Christie |  Information Technology Manager  |  AGM Container Controls, Inc.  |   tchristie@...  | t: 520.881.2130 ext 2176

 

I usually add my new dll to the client folder with clientrelease.zip. add my new dll to the client folder in my server. Update all my mfgsys files with a new version number
(I use a .A, .B, .C method begins the Epicor version number). Copy those mfgsys files into the clientrelease.zip. then wait for the magic to happen. The mismatch between the server version in the config file and the client config file will trigger an auto
update.



Sent from my Atari 600



-----Original Message-----

From: Tom J. Christie [tchristie@…]

Received: Friday, 10 Jan 2014, 17:31

To: vantage@yahoogroups.com [vantage@yahoogroups.com]

Subject: [Vantage] Deployment of custom DLLs



 

I have seen some discussion on the board about how to deploy dlls to clients by placing the dlls in the epicorapp/epicor905/custom/client/ directory and then running a utility to up the revision on the server files so that the client gets repulled next time it gets run by a user.

 

I have been unable to find how exactly to do this. Does anyone have any documentation or suggestions on how to get this done. I really would prefer not to have to run around to all the computers with a USB drive…

 

Regards,

 

Tom Christie |  Information Technology Manager  |  AGM Container Controls, Inc.  |   tchristie@...  | t: 520.881.2130 ext 2176

 

Done the client zip.

I also dropped the file in a folder and asked IT to push to all computers.

Sometimes I drop the files into a folder, tell them to click on a bat file that will copy the files.  Taking into account XP, 32bit and 64 bit systems.

 

Miguel A. Santillan

Compass Manufacturing Systems

510-661-6666  Office

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joshua Giese
Sent: Friday, January 10, 2014 3:34 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Deployment of custom DLLs

 

 

I usually add my new dll to the client folder with clientrelease.zip. add my new dll to the client folder in my server. Update all my mfgsys files with a new version number (I use a .A, .B, .C method begins the Epicor version number). Copy those mfgsys files into the clientrelease.zip. then wait for the magic to happen. The mismatch between the server version in the config file and the client config file will trigger an auto update.

Sent from my Atari 600

-----Original Message-----
From: Tom J. Christie [tchristie@...]
Received: Friday, 10 Jan 2014, 17:31
To: vantage@yahoogroups.com [vantage@yahoogroups.com]
Subject: [Vantage] Deployment of custom DLLs

 

I have seen some discussion on the board about how to deploy dlls to clients by placing the dlls in the epicorapp/epicor905/custom/client/ directory and then running a utility to up the revision on the server files so that the client gets repulled next time it gets run by a user.

 

I have been unable to find how exactly to do this. Does anyone have any documentation or suggestions on how to get this done. I really would prefer not to have to run around to all the computers with a USB drive…

 

Regards,

 

Tom Christie |  Information Technology Manager  |  AGM Container Controls, Inc.  |   tchristie@...  | t: 520.881.2130 ext 2176

 

That sounds good. When you say you update “all my mfgsys files” which ones are you referring to? The ones located on the epicor905/client/config directory? Also, in the config file, what value are you changing, the “Version Value”?

 

I just want to make sure I have it right before I break it entirely and no one in the company can log in!

 

Tom Christie |  Information Technology Manager  |  AGM Container Controls, Inc.  |   tchristie@...  | t: 520.881.2130 ext 2176

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joshua Giese
Sent: Friday, January 10, 2014 4:34 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Deployment of custom DLLs

 

 

I usually add my new dll to the client folder with clientrelease.zip. add my new dll to the client folder in my server. Update all my mfgsys files with a new version number (I use a .A, .B, .C method begins the Epicor version number). Copy those mfgsys files into the clientrelease.zip. then wait for the magic to happen. The mismatch between the server version in the config file and the client config file will trigger an auto update.

Sent from my Atari 600

-----Original Message-----
From: Tom J. Christie [tchristie@...]
Received: Friday, 10 Jan 2014, 17:31
To: vantage@yahoogroups.com [vantage@yahoogroups.com]
Subject: [Vantage] Deployment of custom DLLs

 

I have seen some discussion on the board about how to deploy dlls to clients by placing the dlls in the epicorapp/epicor905/custom/client/ directory and then running a utility to up the revision on the server files so that the client gets repulled next time it gets run by a user.

 

I have been unable to find how exactly to do this. Does anyone have any documentation or suggestions on how to get this done. I really would prefer not to have to run around to all the computers with a USB drive…

 

Regards,

 

Tom Christie |  Information Technology Manager  |  AGM Container Controls, Inc.  |   tchristie@...  | t: 520.881.2130 ext 2176