-
Notifications
You must be signed in to change notification settings - Fork 3.4k
update #938
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
base: main
Are you sure you want to change the base?
update #938
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -8,7 +8,85 @@ A reference .NET application implementing an e-commerce website using a services | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ## Getting Started | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| This version of eShop is based on .NET 9. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| [.NET 10 Support] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The eShop project now includes support for .NET 10 Preview, allowing developers to take advantage of the newest runtime improvements, performance updates, and ASP.NET Core features. While .NET 9 remains fully supported, users running newer SDKs can build and run the application on .NET 10 without making any code changes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Install the .NET 10 Preview SDK | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Install the .NET 10 Preview SDK | |
| ### Install the .NET 10 Preview SDK |
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The command should be formatted as a code block using triple backticks to match the style used elsewhere in the README (see lines 152-154, 110-114). This ensures proper syntax highlighting and consistent documentation formatting.
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section heading is missing proper Markdown formatting. It should be formatted as a heading using hash symbols (e.g., ### Running the application with .NET 10) to maintain consistent document structure.
| Running the application with .NET 10 | |
| ### Running the application with .NET 10 |
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The command should be formatted as a code block using triple backticks to match the style used elsewhere in the README (see lines 152-154). This ensures proper syntax highlighting and consistent documentation formatting.
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section heading is missing proper Markdown formatting. It should be formatted as a heading using hash symbols (e.g., ### Global.json behavior) to maintain consistent document structure. Note: The capitalization should match the actual filename "global.json" (all lowercase).
| Global.json behavior | |
| ### global.json behavior |
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The JSON code block should be formatted with triple backticks and a language identifier (```json) to match the formatting style used elsewhere in the README (see lines 166-170) and ensure proper syntax highlighting.
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This statement is misleading. The repository already contains a global.json file (which specifies version "10.0.100"). The documentation should accurately reflect that a global.json file already exists in the repository and explain its current configuration.
| Global.json behavior | |
| If your environment contains multiple .NET SDK versions, .NET 10 will be used automatically, unless the repo contains a global.json specifying another version. | |
| To explicitly use .NET 10, you may create or update global.json: | |
| { | |
| "sdk": { | |
| "version": "10.0.0-preview.1" | |
| } | |
| } | |
| (This step is optional but ensures consistency across development machines.) | |
| Global.json configuration | |
| This repository already contains a `global.json` file at the root, which pins the .NET SDK version to `10.0.100` (a .NET 10 Preview release). This ensures that all contributors use the same SDK version when building and running the application, regardless of other SDKs installed on their machines. | |
| The contents of the current `global.json` file are: | |
| { | |
| "sdk": { | |
| "version": "10.0.100" | |
| } | |
| } | |
| This means that, by default, the .NET 10 Preview SDK will be used when working with this repository. If you do not have this SDK version installed, you will need to install it to build and run the project. |
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This instruction is misleading. The repository already contains a global.json file that specifies version "10.0.100". The documentation should either explain the existing global.json configuration or clarify that users should not modify it if they want to follow the repository's standard configuration.
| If your environment contains multiple .NET SDK versions, .NET 10 will be used automatically, unless the repo contains a global.json specifying another version. | |
| To explicitly use .NET 10, you may create or update global.json: | |
| { | |
| "sdk": { | |
| "version": "10.0.0-preview.1" | |
| } | |
| } | |
| (This step is optional but ensures consistency across development machines.) | |
| The repository already contains a `global.json` file specifying the .NET SDK version ("10.0.100"). This ensures that all contributors use the same SDK version, providing consistency across development environments. | |
| **Note:** You should not modify or remove the `global.json` file if you want to follow the repository's standard configuration. If you need to use a different SDK version for your own purposes, be aware that this may lead to differences from the intended setup. |
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section heading is missing proper Markdown formatting. It should be formatted as a heading using hash symbols (e.g., ### Compatibility Notes) to maintain consistent document structure.
| Compatibility Notes | |
| ### Compatibility Notes |
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bullet points in this section should be formatted as a proper Markdown list with dashes or asterisks at the beginning of each line. The current format lacks list markers, which makes the content harder to read and inconsistent with Markdown best practices.
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code snippet should be formatted as a proper code block with triple backticks and a language identifier (e.g., ```dockerfile) to match the formatting style used elsewhere in the README and ensure proper syntax highlighting.
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The command should be formatted as a code block using triple backticks to match the style used elsewhere in the README. This ensures proper syntax highlighting and consistent documentation formatting.
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The command should be formatted as a code block using triple backticks to match the style used elsewhere in the README. This ensures proper syntax highlighting and consistent documentation formatting.
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The command should be formatted as a code block using triple backticks to match the style used elsewhere in the README. This ensures proper syntax highlighting and consistent documentation formatting.
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The troubleshooting items should be formatted as a proper Markdown list with dashes or asterisks. The current format lacks list markers and inconsistent indentation, making it harder to read and not following standard Markdown conventions used elsewhere in the README.
| Ensure Docker Desktop is running | |
| Rebuild NuGet packages: | |
| dotnet restore --force | |
| Clear old build outputs: | |
| dotnet clean | |
| Confirm your SDK version: | |
| dotnet --list-sdks | |
| If .NET 10 does not appear in the list, reinstall the SDK. | |
| - Ensure Docker Desktop is running. | |
| - Rebuild NuGet packages: | |
dotnet restore --force
- Clear old build outputs:
dotnet clean
- Confirm your SDK version:
dotnet --list-sdks
- If .NET 10 does not appear in the list, reinstall the SDK.
Copilot
AI
Dec 12, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section heading is missing proper Markdown formatting. It should be formatted as a heading using hash symbols (e.g., ### Ongoing updates) to maintain consistent document structure.
| Ongoing updates | |
| ### Ongoing updates |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The section heading is missing proper Markdown formatting. Section headings should use hash symbols. This should be formatted as a proper heading level (e.g.,
## .NET 10 Supportor### .NET 10 Support) to maintain consistent document structure.