CODEWITHSUNDEEP
axaptadynamics-ax-2012dynamics-ax-2012-r2
ceth
ceth

Reputation: 45295

Deploy .net assembly from AOS to each client in AX2012

Once a week I get the new version of .net assembly which I need to deploy to our Axapta 2012 installation. I don't want to copy this dll to axapta client folder on each computer. So I am searching the way to deploy it to AOS and hope it will deploy on each client automatically.

I have found many solution (this is one of them), but all of them works only if I have the source code of this assembly. I don't have. And I can not to 'Add VS project to AOT' and deploy it using VS add-ins.

Is there any way to deploy .net assembly (as compiled DLL) from AOS to each client ?

Upvotes: 0

Views: 2794

Answers (1)

Klaas Deforche
Klaas Deforche

Reputation: 1151

If you cannot do it using the "Add VS projection to AOT" method, you can use the SysFileDeployment class. This is demonstrated in Joris DG his blogpost here.

On msdn the description of the SysFileDeploymentclass is as follows: The SysFileDeployment class is used for deploying files from the server to the clients.

On msdn it is also explained how you need to do this.Basically all you need to do is extend this class and point to the files you need to deploy (in your case a dll). You will also have to change the build number of you solution to trigger the deployment.

You can also deploy dll's by adding them to the GAC, as demonstrated here: Axilicious: AX2012 DLL Deployment and how AX binds DLL’s at runtime

To summarize main differences are:

  • Using the visual studio properties: it is deployed to a folder specific to that user (so a different folder for each user) at the moment it is needed
  • Using SysFileDeployment: it is copied to the client bin folder, a restart of the client is needed (possibly problems when on citrix/terminal services, like Joris suggests in the link you provided?)
  • GAC: DLL's are stored in the Global Assembly Cache and different versions are stored but you need to provide a mechanism of deploying them yourself

Personally I would try the SysFileDeployment method as it's the standard method MS provide. If you have trouble, you might receive support.

Upvotes: 3

Related Questions