-
Notifications
You must be signed in to change notification settings - Fork 899
Correct ".NET" usage #1046
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
Correct ".NET" usage #1046
Conversation
- ".Net" -> ".NET". - Make fully upper-case, which is the correct usage.
While we're talking description: are .NET and Mono distinct? Should this not just be "to .NET"? |
/cc @Therzok ? |
@richlander Thanks! Repository description has been updated. |
@nulltoken It's actually dependent on what you're trying to say. If you're trying to mention a runtime, then it's Mono/CoreCLR/CLR. If you're trying to mention the .NET stack, it's .NET. |
@Therzok Hmmm... So, what would be a correct wording to express that the library is compatible with both the Mono project and Microsoft implementations of the runtime? /cc @ethomson @richlander |
I suggest removing Mono from the repo description at the top, just to make it simpler. it's really a statement about this project being the language bindings for .NET at large. It is important to be clear about .NET and Mono in the readme, since that describes a particular usage scenario. @migueldeicaza is free to overrule me. |
Isn't .NET a Microsoft trademark for a particular implementation? Perhaps a task for the .NET foundation to bless various VMs implementing some/parts of the spec as being .NET or not? But in the meantime, I do not think it hurts to put both Mono and .NET there. |
Works for me! |
/cc @martinwoodward Meanwhile, let's merge this in. Cheers! |
Thanks for the CC - I'll add certification to my list of things to look into. |
Note: Would be great if a project owner could make the same change in the repo description. PRs cannot affect that.