Unmanaged Solution for August Release

[sperry1625]

The downloads for the August release are different then previous releases. I do not see an unmanaged solution download for August. Can one be provided, or am I missing something?

Thank you.

-S

[denise-msft]

We have decided not to release an unmanaged solution to align with Microsoft's recommended best practices defined in the solution concepts documentation. Unmanaged solutions are not intended to be distributed to users who are not implementing changes to the components, and we run into issues for things like updates and deprecations. The intention is to make a more seamless experience. However, we are always open to hearing any reasons why you want to use unmanaged, so if our reasoning does not resonate with you, please let us know!

[sperry1625]

I leverage Azure DevOps to manage all solutions and deployments within our environments. The ALM flows we have established assume a starting point of an unmanaged solution. From there we deploy the solutions to other environments where they are needed. Without that starting point our flows are broken. Also, even though we do not directly modify the code we do have a requirement to have the source in case this is ever discontinued, we will have what we need to maintain our applications if necessary. Sort of like having the code placed in escrow. Regards,

…

-S

On Fri, Sep 2, 2022, 5:12 AM Denise Moran ***@***.***> wrote: We have decided not to release an unmanaged solution to align with Microsoft's recommended best practices defined in the solution concepts documentation <https://docs.microsoft.com/en-us/power-platform/alm/solution-concepts-alm#managed-and-unmanaged-solutions>. Unmanaged solutions are not intended to be distributed to users who are not implementing changes to the components, and we run into issues for things like updates and deprecations. The intention is to make a more seamless experience. However, we are always open to hearing any reasons why you want to use unmanaged, so if our reasoning does not resonate with you, please let us know! — Reply to this email directly, view it on GitHub <#96 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFNR6PS64Y43F7VSGZNINKTV4HAJNANCNFSM6AAAAAAQCH7ETM> . You are receiving this because you authored the thread.Message ID: <microsoft/powercat-creator-kit/repo-discussions/96/comments/3534609@ github.com>

[denise-msft]

I'm sorry that your DevOps process was broken without an unmanaged solution. Unfortunately, the costs of maintaining an unmanaged version of the components are too high for our dev team to support, which is why we are forced to make that decision for the immediate time being. We can consider this or other ways to support unmanaged solutions when more resources are available for our team. Would a pac cli command to install the latest version of the kit in your devops process be an option for you if we could support that?

For now, is it possible for you to update your DevOps process to read the managed CreatorKitCore solution?

Regarding the source code, everything is available in the GitHub repository and will be available in the history, even in the case the kit is discontinued. You can rebuild the code components into your own solutions and manage them separately (as unmanged solutions) if that makes more sense.