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

Allow for specifying a version of the SDK different from WinUI #18526

Open
jeromelaban opened this issue Oct 21, 2024 · 1 comment
Open

Allow for specifying a version of the SDK different from WinUI #18526

jeromelaban opened this issue Oct 21, 2024 · 1 comment
Labels
area/sdk Categorizes an issue or PR as relevant to the Uno.Sdk kind/enhancement New feature or request project/core-tools 🛠️ Categorizes an issue or PR as relevant to core and tools

Comments

@jeromelaban
Copy link
Member

What would you like to be added

From @mikernet:

I know that currently Uno.Sdk versioning is strongly tied to Uno version, but would be nice if that wasn't the case. When writing libs you want to target lowest Uno version possible for widest reach, but then you miss out on SDK bug fixes/enhancements/etc, and you can't use the Uno SDK with glorious single-project at all if you want to target version < 5.2.

Any chance that the two might get decoupled to allow using newer SDK with older Uno versions?

Why is this needed

No response

For which platform

No response

Anything else we need to know?

No response

@jeromelaban jeromelaban added kind/enhancement New feature or request triage/untriaged Indicates an issue requires triaging or verification difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. project/core-tools 🛠️ Categorizes an issue or PR as relevant to core and tools and removed triage/untriaged Indicates an issue requires triaging or verification labels Oct 21, 2024
@jeromelaban
Copy link
Member Author

We cannot do this at this time, because the contents of the uno.sdk are linked to the uno repository, and we need those two decoupled for providing all the versions of dependencies at once. Disabling implicit packages does not help either, as we have an explicit check to ensure both are aligned.

But you can use newer MS SDKs to target older things just fine, so I feel like there's gotta be some way to decouple those things.

At this time, we can't decouple it. We tried, but there's no way to do it unless msbuild changes, mostly because we need to build the uno.sdk separate from uno.

@MartinZikmund MartinZikmund added area/sdk Categorizes an issue or PR as relevant to the Uno.Sdk and removed difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sdk Categorizes an issue or PR as relevant to the Uno.Sdk kind/enhancement New feature or request project/core-tools 🛠️ Categorizes an issue or PR as relevant to core and tools
Projects
None yet
Development

No branches or pull requests

2 participants