[priscilawebdev]

It seems this platform was missing, which is why it can’t be found when creating a new project, even though we have onboarding documentation for it. I tried to check whether it was removed intentionally, but so far I haven’t found any indication of that.

[ArthurKnaus]

Also noticed that. Before adding it back, I would like to ask someone familiar with .net

[Flash0ver]

Thanks for bringing this up!

I'm a bit uncertain:
We do intend to deprecate official support for UWP

• Deprecate UWP for v6 sentry-dotnet#4497

We plan to ship v6 of the Sentry .NET SDK together with the release of the .NET 10 SDK from Microsoft, which will be around 2025-11-11.
I just realized that we forgot to plan in the deprecation/removal of the onboarding, too.

Also ... do we need to remove other mentions of UWP and `dotnet-uwp ... like links to docs and such.
I updated above issue to consider this too, once we "officially" deprecate support.

Now I'm wondering about this changeset:

• should we fix this now ... and then (within the next month) remove it again "wholesale" together with deprecating the docs and other references
• or not apply this changeset in the first place

@jamescrosswell, what do you think?

[priscilawebdev]

Thanks @Flash0ver ! it makes sense.

I would go with this suggestion:

should we fix this now ... and then (within the next month) remove it again "wholesale" together with deprecating the docs and other references

[jamescrosswell]

It seems like a waste of time to add something now that we'll delete within the month.

The changes (to deprecate UWP) are purely in the documentation... there's no reason we can't do this today, from a technical perspective. Rather than doing work now and undoing it in a month, let's just bring forward the documentation work we have to do to deprecate UWP.

[ArthurKnaus]

I agree with @jamescrosswell, seems weird to bring it back if we remove it in a month.
Also dotnet-uwp has not been available in the project creation since ages...
I think we can close this PR and just remove the remaining traces (like in-product docs) in the product codebase

[priscilawebdev]

@jamescrosswell @ArthurKnaus

I understand the concern, but this one-line change felt more like a quick hotfix. In comparison, the recent effort to convert that platform’s file structure to content blocks (see) ended up being less useful than expected, since we thought it was rendered in the UI.

In any case, I’ve already closed the PR 🙂

[ArthurKnaus]

@jamescrosswell I created a follow-up PR here that marks the platform as deprecated in the produce codebase.
#101715