We no longer require Cake build nor we use it extensively!
Update Azure Pipelines (CI YAML) Script to be more modern and runnable across platforms.
Replaced the headers check with a PowerShell script mimicking the Cake script's `UpdateHeaders` task functionality.
* Use an emoji for Contributors title
Emoji Used: Champion Cup
Aligns with the rest of the titles
Why Champion Cup you ask? Well, Contributors are champions too! 😎
* Don't use inline HTML in markdown
Always use markdown format if possible.
This format to represent image with a link is supported by most markdown parsers.
* Fix grammatical errors in markdown
These were reported by Spell Checker extension (by EWSoftware) in VS IDE.
* Use canonical language-agnostic URLs
Microsoft Docs provide language-specific content for docs published
to the website but in-order for devs in specific region to get locally
translated content, we need to put language-agnostic canonical URLs.
This is usually done by removing any language and region specific info from URLs.
Reported by Docs markdown linter in VSCode.
It was decided that the term 'Basic' is new and
has no established meaning in the software community.
So, Replacing the term 'Basic' with 'Common'. To disambiguate
multiple instances of 'Common', we use an already existing term
'Primitive' and we also append the Platform to which the package targets.
The package title doesn't follow a particular format and is not machine readable.
Thus, I propose the following format: "'Product' - 'Area' - 'Specifics' ('Source/Target')"
Remove redundant MSBuild logic
Consolidate common MSBuild logic
Reorder code-blocks for better readability
Fix-up comments and new-lines across project files
Improve support for Visual Studio 2022:
Since VS IDE 2022 (17.0) is 64-bit only, replace all 32-bit specific MSBuild properties with generic ones.
To make diff understandable through blame and across similar project files,
I have re-organized some lines in these project files. This also improves
readability. Previously, the focus is per-project file but now—to maintain
project logic across repos and several similar logic across project files,
new way of authoring project files is required.
This refactor is the start of it.
Format comments to be legible.
- Place comment start and end tags on a new line for multi-line comments.
- Have space between start and end tags in a single line comment.
Place comments where appropriate.
- If an entire block is common to the comment then place it above the block.
- Only place a comment near or after the block, if it refers exclusively.
Sources are not formatted!
Both VS IDE Code Clean-up and dotnet-format applies this formatting.
Only Code labels and Code within pre-processor blocks are affected.
The reason may be that the indentation wasn't read/written properly
by the formatter within or around those code blocks.
Both VS IDE Code Clean-up and dotnet-format applies this formatting.
Only Code labels and Code within pre-processor blocks are affected.
The reason may be that the indentation wasn't read/written properly
by the formatter within or around those code blocks.
NOTE: We could ignore this commit but we keep it as a reference point
for the VS C# Editor and .NET format team to diagnose this issue.
Update and follow EditorConfig settings.
BOM: Byte Order Mark (Used to identify UTF-8 encoding).
We don't need BOM specified as the latest editors can work without it.
