Clearly separate static and instance API

[verdie-g]

Describe the issue or suggestion

Process.Start() is an instance method and Process.Start(ProcessStartInfo) is a static method. Though, they are displayed exactly the same in the Process class.

Could we have two sections in the class page, one for the static API (include fields, properties, methods, const, static extensions) and one for the instance API?

[adamsitnik]

Hello @verdie-g

I am afraid this is how the docs portal work in general. @gewarren could you please comment on that?

Thanks,
Adam

[verdie-g]

Yes I took Process as an example but I wanted to suggest changing that on the entire doc.

[gewarren]

Thank you for the suggestion. I'll leave this issue open to let others weigh in or perhaps thumbs up it. Given that we haven't received this feedback before, the platform team won't make the change unless it gets more requests.

[adamsitnik]

Yes I took Process as an example but I wanted to suggest changing that on the entire doc.

@eiriktsarpalis this is a general suggestion, that is why I've removed the Process area label (there is nothing actionable for me as the owner of this area)

[tannergooding]

I'll leave this issue open to let others weigh in or perhaps thumbs up it.

This is notably something that I've wanted before as well. Having a clear separation between static vs instance members can make it easier to understand what is available under various contexts and how an API might be used.