Merge main into live #41528
Merged
Merge main into live #41528
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dotnet-policy-service[bot]](https://github.com/avatars/in/285228?s=60&v=4){kind=small}
* Add Main declarations * Replace signature by declaration * Access modifier rule * Improve main overview * Rework Task boilerplate code part * Fix example * Update main-command-line.md * Remove indication about application isn't Library or Service * fix spellcheck Co-authored-by: Rich Lander <rlander@microsoft.com> * Reverse column order in table * Rever column order that show Main declaration * fix missing empty line * Apply suggestions from code review Co-authored-by: David Pine <david.pine@microsoft.com> * Specify 'any' explictit access modifier Co-authored-by: Bill Wagner <wiwagn@microsoft.com> * Remove boilerplate part * Add info about completed task * Fix link * Remove trailing space * Fix link * Fix link * Fix link * Fix link * Reset boilerplate * Main can be internal * Rework Main access modifier part --------- Co-authored-by: Rich Lander <rlander@microsoft.com> Co-authored-by: David Pine <david.pine@microsoft.com> Co-authored-by: Bill Wagner <wiwagn@microsoft.com>
From anonymous feedback: > This article should state that C# and .NET common coding conventions are not "Code Standards" and should not be treated as such. Code standards would be ANSI, ECMA, ISO, standardized.The common .NET conventions work well for a broad extensive library of .NET API BCL calls but do not scale for a large complex business application. The conventions work against aligning the code with the business processes by emphasizing deconstructing the C# code into a large complex web of short classes and method.Code should encapsulate business logic and algorithms. Rather than address the purpose of different rulesets, I replaced all uses of "standard" with "convention". That reinforces that these are our conventions and any customer team should define their own. Their conventions may choose to use ours as a starting point, but shouldn't feel obligated to do so.
Prompt engineering edits --------- Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
auto-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please don't squash-merge this PR.
Internal previews