-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Page needs clarity for people brand-new to .NET Core #13
Comments
Related: |
@cartermp, I took a stab at making these updates. The only one I couldn't find better wording for was the relationship between .NET Core and .NET Framework. I'll keep thinking about how to explain that better. |
(It's interesting reading this now that I'm no longer new to the team/project) @BethMassi 's blog post about understanding .NET was very helpful to me in terms of understanding what things looked like for the last release. Perhaps a similar sort of diagram would suit this section well? |
I know personally that the teams on some sub projects to the dotnet oss push have strong pythonic backgrounds, and the new direction seems to emulate a lot of aspects of the pyenv philosophy. Perhaps that would be a good angle to reference/allude to |
@cartermp can we close this one? Or move it to dotnet/core-docs? |
Scratch closing: I think we can leave it open for now. We can copy stuff from docs into here. |
I will close this one as we have the docs. |
Listing the issues here on a per-section basis.
Get Started
What is .NET Core? link leads to another landing page, not something that tells me what .NET Core is.
.NET Core Platform
Text here references BCL - a newcomer to .NET probably doesn't understand the acronym (I didn't until I looked it up online)
License
This section describes multiple licenses, so the plural form should probably be used here.
Understand the relationship between .NET Core and the .NET Framework.
Learning about ASP.NET and .NET Core
"ASP.NET is the new cross-platform version of ASP.NET" is confusing. I understand that one is a link to the "new" ASP.NET, but referring to two different things with the same name is confusing.
The text was updated successfully, but these errors were encountered: