Skip to content

[Content]: Integration guidance for .NET is outdated #3299

@Swimburger

Description

@Swimburger

What article on segment.com/docs is affected?

https://segment.com/docs/connections/sources/catalog/libraries/server/net/

What part(s) of the article would you like to see updated?

The document describes how to integrate Segment into ASP.NET Web Forms which while it is still a product supported by Microsoft, developers generally don't use Web Forms anymore for quite some time. Since Web Forms is still supported, I would still keep the Web Forms guidance, but we need more modern guidance.

There's client-side .NET platforms like WPF, WinForms, Xamarin, MAUI, Blazor WebAssembly, and 3rd party platforms like Avalonia,
and there's server-side .NET platforms ASP.NET Web Forms, ASP.NET MVC, and ASP.NET Core (Minimal APIs, MVC, Razor Pages, Blazor Server).
This is quite a lot of platforms, so I don't know if they all need guidance. ASP.NET Web Forms and MVC are on .NET Framework which is still supported, but Microsoft recommends moving to and starting new projects with the newer .NET (Core).

In my opinion, the highest priority would be to add guidance for ASP.NET Core MVC, and any other platform guidance is nice to have.

I'm sharing this in the community in case they want to pitch in. They may not agree with my opinion.

Additional information

No response

Metadata

Metadata

Assignees

Labels

contentWhen the bug is about content that needs to get fixedtriaged

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions