replace .NET 8 with .NET 10

Author: mythz

MyApp.sln

@@ -0,0 +1,3 @@
+<Solution>
+  <Project Path="MyApp/MyApp.csproj" />
+</Solution>

MyApp.sln.Source

@@ -21,12 +21,12 @@
   </Target>
 
   <ItemGroup>
-    <PackageReference Include="Markdig" Version="0.43.*" />
-    <PackageReference Include="ServiceStack" Version="8.*" />
-    <PackageReference Include="ServiceStack.Mvc" Version="8.*" />
+    <PackageReference Include="Markdig" Version="0.44.*" />
+    <PackageReference Include="ServiceStack" Version="10.*" />
+    <PackageReference Include="ServiceStack.Mvc" Version="10.*" />
 
     <!-- Required for Razor compilation on change: https://docs.microsoft.com/en-us/aspnet/core/mvc/views/view-compilation?view=aspnetcore-5.0 -->
-    <PackageReference Include="Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation" Version="8.*" />
+    <PackageReference Include="Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation" Version="10.*" />
   </ItemGroup>
 
 <!--  <ItemGroup>-->

MyApp.slnx

@@ -9,7 +9,7 @@ If you don't have the [x dotnet tool](/dotnet-new) installed, the quickest way t
 
 There are a few different ways you can create empty ServiceStack projects ordered by their level of emptiness.
 
-To write a minimal .NET 8 Web App to your current directory, [mix](/mix-tool) in the **[init](https://gist.github.com/gistlyn/8026c4c2a7202b99885539109145e12b)** gist files to your current directory:
+To write a minimal .NET 10 Web App to your current directory, [mix](/mix-tool) in the **[init](https://gist.github.com/gistlyn/8026c4c2a7202b99885539109145e12b)** gist files to your current directory:
 
 :::sh
 npx add-in init

MyApp/MyApp.csproj

@@ -24,13 +24,13 @@ IPs where most traffic generates:
 ### Getting Started
 
 As they offer significant and valuable insights they're now built into all new ASP.NET Core IdentityAuth templates, 
-existing .NET 8 IdentityAuth templates can enable it with: 
+existing .NET 10 IdentityAuth templates can enable it with: 
 
 :::sh
 npx add-in sqlitelogs
 :::
 
-.NET 8 Templates that are not configured to use [Endpoint Routing](/endpoint-routing)
+.NET 10 Templates that are not configured to use [Endpoint Routing](/endpoint-routing)
 and [ASP.NET Core IOC](/net-ioc) will need to explicitly register `SqliteRequestLogger`
 as a singleton dependency in addition to configuring it on the `RequestLogsFeature` plugin:
 

MyApp/_includes/empty-projects.md

@@ -170,7 +170,7 @@ HttpClient profiling is implemented a little differently then other events in th
 
 ### JsonApiClient Profiling
 
-Although we're able to provide richer profiling for our .NET 8+ [JsonApiClient](/csharp-client#jsonapiclient) which has access to typed Request DTOs for submitting API Requests:
+Although we're able to provide richer profiling for our .NET 10+ [JsonApiClient](/csharp-client#jsonapiclient) which has access to typed Request DTOs for submitting API Requests:
 
 <div class="block flex justify-center items-center">
     <img class="max-w-screen-md" src="/img/pages/admin-ui/profiling-client-api-request.png">

MyApp/_pages/admin-ui-analytics.md

@@ -10,7 +10,7 @@ i.e. the primary API used to access Large Language Models (LLMs).
 
 ## Install
 
-AI Chat can be added to any .NET 8+ project by installing the **ServiceStack.AI.Chat** NuGet package and 
+AI Chat can be added to any .NET 10+ project by installing the **ServiceStack.AI.Chat** NuGet package and 
 configuration with:
 
 :::copy

MyApp/_pages/admin-ui-profiling.md

@@ -1,9 +1,9 @@
 ---
-title: Simple Auth for .NET 8 Apps
+title: Simple Auth for .NET 10 Apps
 ---
 
 With ServiceStack now fully [integrated with ASP.NET Identity Auth](/auth/identity-auth),
-our latest [.NET 8 Tailwind Templates](/start) offer a full-featured Auth Configuration complete with User Registration, 
+our latest [.NET 10 Tailwind Templates](/start) offer a full-featured Auth Configuration complete with User Registration, 
 Login, Password Recovery, Two Factory Auth, and more.
 
 Whilst great for Web Applications that need it, it neglects the class of Apps which don't need User Auth and
@@ -12,11 +12,11 @@ the additional complexity it brings inc. Identity and Password Management, EF Mi
 For these stand-alone Apps, Microservices and Docker Appliances that would still like to restrict Access to their APIs
 but don't need the complexity of ASP .NET Core's Authentication machinery, a simpler Auth Story would be preferred.
 
-With the introduction of API Keys in this release we're able to provide a simpler Auth Story for .NET 8 Microservices 
+With the introduction of API Keys in this release we're able to provide a simpler Auth Story for .NET 10 Microservices 
 that's easy for **Admin** Users to manage and control which trusted clients and B2B Integrations can access their functionality.
 
 :::youtube 0ceU91ZBhTQ
-Simple Auth Story with API Keys ideal for .NET 8 Microservices
+Simple Auth Story with API Keys ideal for .NET 10 Microservices
 :::
 
 The easiest way to get started is by creating a new Empty project with API Keys enabled with your preferred database to store the API Keys in. SQLite is a good choice for stand-alone Apps as it doesn't require any infrastructure dependencies.
@@ -353,6 +353,6 @@ PreRequestFilters.Add((req, res) =>
 
 ### Summary
 
-We hope this shows how stand-alone .NET 8 Microservices and self-contained Docker Apps can use the 
+We hope this shows how stand-alone .NET 10 Microservices and self-contained Docker Apps can use the 
 simple **Admin** and **API Keys** configuration to easily secure their APIs, complete with **Management UI** 
 and **typed Service Client** integrations.

MyApp/_pages/ai-chat-api.md

@@ -19,12 +19,12 @@ another Auth Provider that provided another way to authenticate a single user. T
 
 Given the primary use-case for API Keys is for machine-to-machine communication where the client is not a User,
 nor do they want systems they give out their API Keys to, to have access to their User Account, we've changed
-how API Keys work in .NET 8.
+how API Keys work in .NET 10.
 
-## .NET 8 API Keys Feature
+## .NET 10 API Keys Feature
 
 :::youtube U4vqOIHOs_Q
-New .NET 8 API Keys Feature with Built-In UIs!
+New .NET 10 API Keys Feature with Built-In UIs!
 :::
 
 The first design decision to overcome the above issues was to separate API Keys from Users and Authentication itself,