Template does not work with .NET SDK 8.0.406 due to missing global.json version control

[ekiyak]

Steps to reproduce

1-Download and install the "Sneat Asp.Net Mvc Admin - Free" template.
2-Ensure that .NET SDK 8.0.406 (latest available version) is installed on your machine.
3-Open the template in Visual Studio and try to run it.
4-The application fails with the following error:
An unhandled exception occurred while processing the request. InvalidOperationException: The view 'Index' was not found. The following locations were searched: /Views/Dashboards/Index.cshtml /Views/Shared/Index.cshtml
5-Downgrade the .NET SDK by adding a global.json file to the solution with the following content:
{ "sdk": { "version": "8.0.100" } }
6-Run the project again in Visual Studio, and the issue is resolved.

What is expected?

The template should work with the latest .NET 8 version without requiring additional manual configuration.
If the template is only tested with specific .NET 8 versions, it should include a global.json file in the solution to specify the supported version.

What is actually happening?

The template fails to run with the latest .NET SDK 8.0.406.
Users who update their SDK to the latest version cannot use the template without debugging the issue, which is time-consuming.
The issue is resolved only after manually setting a global.json file to force an older .NET 8 SDK version.

Suggested Fix:
Include a global.json file in the solution to specify the supported SDK version.
Update the documentation or description to warn users about potential compatibility issues with future .NET 8 updates.

Additional data

[Vatsal6288]

Hello @ekiyak,

Thank you for bringing this to our attention.

We appreciate your feedback and will certainly consider adding this in one of our upcoming releases.

If you have any further questions or suggestions, feel free to let us know!

[github-actions]

This issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Thank you for raising the concern.

[github-actions]

This issue has been automatically marked as closed because it has no recent activity.