Friday, 15 August 2014

.net - How to refresh a wcf service reference from c# project in Dynamics AX without VS -


I'm not an expert in Dynamics X, so I need to ask this question here.

I have the following scenario: I need to consume the WCF service from within a form, so that I can call for web service and get some data. For that purpose I have created a C # project, where I have added my WCF service reference. So far, so good. The next step I need to do is to deploy this assembly which is my WCF ref for Dynamix X. I have seen some tutorials to do this, and it seems that AX tools work well for Visual Studio, which will give it VS. Deploy from within.

But when I have to update my service reforms production environment, I always install VS with the Ax tool installed. I can not blame them (I can not blame them for that), so I have a question: because VS tools should have only a cover on some other AX commands because it is responsible for deploying NAT to AX, How to manually update or run a script or I can do this.

I have found this article that explains how to work with managed code in AX and where it is.

So my questions are as follows:
1. Is it possible to refresh any Net Enterprise, which has service reference for my WCF service without installing VS + AX ​​tool on the server ? 2. If so, will it be enough to just copy a new assembly in server-client folders to refresh the assembly?
3. Is there any advanced article that dive deep into the deployment of AX device or AX device .NET assembly works?

Thanks in advance for the answer!

As you are a provider of solutions in your development environment, , Assembly and all dependencies).

In the customer's environment, you make AX models and compile.

Then your answer to your questions:

  1. You should not refresh the service in the production environment. The refreshed proxy should be made in the development environment and the model should be exported, which is imported into the (former) production environment.
  2. AoS dependent assemblies are restarted (unless your proxy is marked as).
  3. Blog:
  4. White Paper:
< / Html>

No comments:

Post a Comment