Announcements
No record found.
Hi All,
i have LCS deployable packages in asset library that were applied to production, am configuring new local dev enviromnemt and wish to import those deployable packages to this on prem dev machine, how can i do this ?
Thanks a lot.
Check this article: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/manage-runtime-packages
You need to add them in your source control and include them in your build process. Every deployable package that you apply to test/prod should have all your customizations and third party solutions.
I assume that you are talking about third party solutions. If you wish to get your own source code in your dev system, just connect the dev system to ADO and get latest. But deployable packages don't contain any source code.
What are the deployable packages that you are talking about?
Hi Nikolaos, thank you for your reply , the customer have deleted the DEV and UAT environment , and now we have configured new local one for them, but we need to get the customization that we did before that were applied on production so i have them only as deployable packages on LCS that were created before on the deleted Dev environment . so i was wondering how i can use those deployable packages to import the models inside them to the dev environment.
Deployable packages don't contain source code (models), they only contain the .DLL binaries that come out of the build process. This is why it's very important to use source control. Theoretically you can try to reverse engineer the DLLs with ILSpy tool, but you still need to manually re-implement everything that you find with it.
There's no way to get your source code back if you didn't use source control and you have deleted the local copies (that were in the dev system that is already deleted).
I recommend that you start using source control immediately to avoid any such damage in the future.
You can of course install the deployable package on the dev machine and add it to source control, but you don't get source code this way, you only get the binaries and this way you can have your custom functionalities in your dev box. This way you can at least extend your old customizations (by creating a new package and model and referencing your existing custom package). But you can't modify or debug your old customizations without having the source code.
Thanks a lot nikolaos, so i can now install the deployable package and the customizations will be reflected on the local machine ? and how could i install the deployable package for the local dev machine ?
Please read the MS article from my first reply. Now you should handle your deployable package as if it were a third party solution.
Thanks a lot Nikolaos
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
We are thrilled to have these Champions in our Community!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 692
André Arnaud de Cal... 532 Super User 2026 Season 1
CP04-islander 478
