Build from command line: xppc.exe

(0) Share

Report

Posted on by Deshpande

216

Does anyone have an example on how to use this utility to build D365 application from command line? I could not find any. :( Looking to build entire application.

Please let me know if you have a sample command that I can use. Don't want reinvent the wheel if possible :)

regards

harry

I have the same question (0)

All responses (14)

Answers (1)

faheem Ahmed 450 on at

Like (0)

Report

community.dynamics.com/.../use-command-line-to-build-your-dynamic-365-visual-studio-metadata-project-xppc

Was this reply helpful? Yes No
Martin Dráb 237,965 Most Valuable Professional on at

Like (0)

Report

If you don't want to reinvent the wheel, what about utilizing a build server? It's whole purpose is to build the application.

Was this reply helpful? Yes No
Deshpande 216 on at

Like (0)

Report

Thanks, I already looked at that page. Unfortunately, it is not showing me how to use the parameters, some of them are mandatory. :(

Was this reply helpful? Yes No
Deshpande 216 on at

Like (0)

Report

I have to admit that I am rather weak on SysAdmin side. So here is what I am trying to do.

Main objective is to create a 100% replica of Production environment. If I use build server then there is no guarantee that the build will be same as production. Another problem is that we have all these ISV solutions that are not checked in (I dont know why and what is the BP). So I don't know how the build server will work in this scenario, any suggestions?

Was this reply helpful? Yes No
Martin Dráb 237,965 Most Valuable Professional on at

Like (0)

Report

How is compilation of source code related to production? There are is no source code in production.

You use a build server to create deployable packages (this is when source code gets compiled to binaries) and then ask Microsoft to install these binaries to production. If you install the same binaries to another environment with the same version as in production, you'll get the same application. Another solution would be copying binaries from production, but you don't need that if you know what you've installed to production (and that's what you definitely should know, otherwise you're in trouble).

Was this reply helpful? Yes No
Deshpande 216 on at

Like (0)

Report

"If you install the same binaries to another environment with the same version as in production, you'll get the same application." Yes, this is exactly what I am trying to do. I have written script to deploy packages on the local box. However, I need to compile application once I deploy the package and I am trying to automate this step. Once this is done I will write script to load db but that should not be terribly complicated.

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,162 Moderator on at

Like (0)

Report

You don't need (and you can't) compile the deployable packages after installing them. They are dlls that the build created from source code.

Deployable packages don't contain source code. There's nothing to compile.

By the way here are instructions on how to handle third party models and binaries in your source control. You should really add the isv solutions to source control, too. Even if they are binaries only.

[View:https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/dev-tools/manage-runtime-packages]

Was this reply helpful? Yes No
Deshpande 216 on at

Like (0)

Report

hi

I am compiling entire application. We have extended ISV solutions in addition to OOB D365. I believe a full compile is necessary. Is this not correct? If our customized model will contain binary as well as source code then probably compile will not be needed?

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,162 Moderator on at

Like (0)

Report

Compile is not needed if you already have deployable packages. They are the result of the compilation!

There's no compiler and no source code in test and prod environments, either. And you can deploy packages in those environments. The packages contain the compilation result = dll assemblies.

Was this reply helpful? Yes No
Deshpande 216 on at

Like (0)

Report

Thanks for the link by the way. It seems if we check-in ISV models then problem is completely solved. I dont know why at go-live Microsoft recommended not to do that. :( I have opened a discussion with Microsoft support to clarify this issue.

Was this reply helpful? Yes No