Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the same packager and installer code as the Unified SDK #234

Open
SamVanheer opened this issue Jan 15, 2024 · 0 comments
Open

Use the same packager and installer code as the Unified SDK #234

SamVanheer opened this issue Jan 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@SamVanheer
Copy link
Collaborator

All 3 Updated projects currently use a packager and installer written in C# that is run using dotnet script.

Switching to the Unified SDK's packager and installer code helps to centralize everything and eliminates the need to use dotnet script. It avoids problems where users encounter problems compiling scripts (can happen when the Nuget config file is incorrect) and speeds up execution.

It is recommended to use a separate installer since the ContentInstaller applies map upgrades and copies files which isn't needed for the Updated projects, and some upgrades are specific to the Unified SDK.

@SamVanheer SamVanheer added the enhancement New feature or request label Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant