Can I deploy my core developments directly to the Production Instance?

(0) Share

Report

Posted on by Dilanka H.

116

Previous question subject was: "Does Docker Sandbox Container support Deployments to Production Instance somehow?"

Hello, I am mostly new to the Development things on Business Central, although I'd eagerly like to know the possibility of Deploying my Developments to the Production Instance directly / indirectly (somehow), which I've carried out on the Sandbox Container Provided by BC itself.

For the record, my SB Container is locally hosted.

Microsoft & Docker says, "Develop things only for Testing & Evaluation purposes. Don't use on Production Instance". I completely understand the use of SB Container and Online Sandbox, but if I need to alter something in the Core or BC how can I do it? The actual question is how do I publish/deploy it even if I am able to do so?

Please correct me if I am following a wrong path. I'm just a newbie roaming around this new product.

Thanks, and please forgive my area of research.

Categories:

Financial Management

I have the same question (0)

All responses (9)

Answers (0)

Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (1)

Report

No you cannot directly deploy and debug from VS Code to a production tenant. Deployment from VS Code is supported only on a local sandbox or a cloud sandbox.

For a production environment you need to load the .app file from Extension Management page and (actually) you cannot debug on it.

Was this reply helpful? Yes No
Dilanka H. 116 on at

Like (0)

Report
Hi Stefano,

Honestly, I am thankful for you, for giving a stable resolution to my biggest doubt with these deployment-related things.

Additionally, could you please correct me on the following process (as per my knowledge and research done on the internet) regarding Production Instance Extension Deployment?

I need to develop Extensions on Cloud/Local sandbox with VSCode.

Test the development on Sandbox.

Export the development as APP package.

Sign the exported package with either a self-signed certificate or paid signing solution.

Import the package to Production Instance as an Extension.

Deploy!

Thanks a lot!

Was this reply helpful? Yes No
Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (1)

Report

It’s all correct except step 4. You have to sign the app only if you want to go to AppSource. For a per-tenant Extension (directly deployed to your customer’s production tenant) you don’t need to sign it, just a direct upload of the app package.

Was this reply helpful? Yes No
Dilanka H. 116 on at

Like (0)

Report

Thank you for the quick response in the most precise way. Now all my doubts are cleared with perfection. It's time to try these practically.

Was this reply helpful? Yes No
Darens Vans 90 on at

Like (0)

Report

Hi All,

sorry for raising up these issue again, i have one question regarding how to prevent directly deployment to production environment, can BC has setup to prevent this? so developer cannot use vs code directly instead of using package.

Thanks

Was this reply helpful? Yes No
Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

As said above, this is not possible on SaaS. You receive an error.

Was this reply helpful? Yes No
Darens Vans 90 on at

Like (0)

Report

Hi Demiliani,

Thank you for your quick response, i forgot to say that our environment is on-premise version.

Best Regards

Was this reply helpful? Yes No
Suggested answer

Inge M. Bruvik 1,111 Moderator on at

Like (0)

Report

On prem you can disable the "Enable Developer Service Endpoint" option" on the BC service.

Please refer to this documentation:

docs.microsoft.com/.../configure-server-instance

Was this reply helpful? Yes No
Suggested answer

Darens Vans 90 on at

Like (0)

Report

Hi Inge,

Ah perfect, thank you for your hints. that's worked.

Best Regards

Was this reply helpful? Yes No