Upgrade to use recommended Plugin syntax

Author: mythz

MyApp/_pages/autoquery/autogen.md

@@ -21,7 +21,7 @@ You can then add the generated DTOs to your ServiceModel's to quickly enable Aut
 To enable this feature you you just need to initialize `GenerateCrudServices` in your `AutoQueryFeature` plugin, e.g:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     MaxLimit = 1000,
     GenerateCrudServices = new GenerateCrudServices {}
 });
@@ -55,15 +55,12 @@ public class ConfigureDb : IHostingStartup
 {
     public void Configure(IWebHostBuilder builder) => builder
         .ConfigureServices((context, services) => {
-            var dbFactory = new OrmLiteConnectionFactory(
-                context.Configuration.GetConnectionString("DefaultConnection"),
-                SqliteDialect.Provider);
-            container.AddSingleton<IDbConnectionFactory>(c => dbFactory);
+            var ormLite = services.AddOrmLite(options => options.UseSqlite(connString));
 
             services.AddPlugin(new AutoQueryFeature {
                 MaxLimit = 1000,
                 GenerateCrudServices = new GenerateCrudServices {
-                    DbFactory = dbFactory,
+                    DbFactory = ormLite.DbFactory,
                 }
             });
             // ...
@@ -120,7 +117,7 @@ i.e. the same experience as updating normal DTOs.
 After generating `dtos.cs` AutoGen is no longer needed and can now be removed by removing `GenerateCrudServices`
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     MaxLimit = 1000,
     // GenerateCrudServices = new GenerateCrudServices {}
 });
@@ -203,9 +200,11 @@ But we can raise the productivity level even higher by instead of manually impor
 This is what the magical `AutoRegister` flag does for us:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+var ormLite = services.AddOrmLite(options => options.UseSqlite(connString));
+
+services.AddPlugin(new AutoQueryFeature {
     GenerateCrudServices = new GenerateCrudServices {
-        DbFactory = dbFactory,
+        DbFactory = ormLite.DbFactory,
         AutoRegister = true,
         //....
     }
@@ -247,16 +246,12 @@ public class ConfigureDb : IHostingStartup
     {
         builder.ConfigureServices((context,services) =>
         {
-            var dbFactory = new OrmLiteConnectionFactory(
-                context.Configuration.GetConnectionString("DefaultConnection"),
-                SqliteDialect.Provider);
-
-            services.AddSingleton<IDbConnectionFactory>(dbFactory);
+            var ormLite = services.AddOrmLite(options => options.UseSqlite(connString));
 
             services.AddPlugin(new AutoQueryFeature {
                 MaxLimit = 1000,
                 GenerateCrudServices = new GenerateCrudServices {
-                    DbFactory = dbFactory,
+                    DbFactory = ormLite.DbFactory,
                     AutoRegister = true
                 }
             });
@@ -433,8 +428,11 @@ The primary difference is that they only exist in a .NET Assembly in memory crea
 Peeking deeper behind the `AutoRegister` flag will reveal that it's a helper for adding an empty `CreateCrudServices` instance, i.e. it's equivalent to:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+var ormLite = services.AddOrmLite(options => options.UseSqlite(connString));
+
+services.AddPlugin(new AutoQueryFeature {
     GenerateCrudServices = new GenerateCrudServices {
+        DbFactory = ormLite.DbFactory,
         CreateServices = {
             new CreateCrudServices()
         }
@@ -452,9 +450,11 @@ Although should you wish to, you can also generate Services for multiple Databas
 With this you could have a single API Gateway Servicifying access to multiple System RDBMS Tables & Schemas, e.g:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+var ormLite = services.AddOrmLite(options => options.UseSqlite(connString));
+
+services.AddPlugin(new AutoQueryFeature {
     GenerateCrudServices = new GenerateCrudServices {
-        DbFactory = dbFactory,
+        DbFactory = ormlite.DbFactory,
         CreateServices = {
             new CreateCrudServices(),
             new CreateCrudServices { Schema = "AltSchema" },
@@ -505,7 +505,7 @@ var tableRequiredFields = new Dictionary<string,string[]> {
     ["Shipper"] = new[]{ "CompanyName", "Phone" },
 };
 
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     MaxLimit = 100,
     GenerateCrudServices = new GenerateCrudServices
     {
@@ -552,16 +552,16 @@ Plugins.Add(new AutoQueryFeature {
         IncludeType = type => !ignoreTables.Contains(type.Name),
     }
 });
-
-Plugins.Add(new ValidationFeature()); // Enable Validation
 ```
 
 Additionally, the `TableSchemasFilter` can be used to modify the schema used by AutoGen to generate the types associated with your AutoQuery APIs.
 This gives you the opportunity to filter or modify the schema after they are pulled from the database.
 For example, we could `Remove` tables based on naming, or alter column definitions to assist with any schema issues.
 
 ```csharp
+var ormLite = services.AddOrmLite(options => options.UseSqlite(connString));
 GenerateCrudServices = new GenerateCrudServices {
+    DbFactory = ormLite.DbFactory,
     AutoRegister = true,
     AddDataContractAttributes = false,
     TableSchemasFilter = tableSchemas =>
@@ -671,10 +671,12 @@ So if you had an existing table name called `applications` the default conventio
 You can change each of these default conventions with the new `GenerateOperationsFilter`, e.g:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+var ormLite = services.AddOrmLite(options => options.UseSqlite(connString));
+
+services.AddPlugin(new AutoQueryFeature {
     MaxLimit = 1000,
     GenerateCrudServices = new GenerateCrudServices {
-        DbFactory = dbFactory,
+        DbFactory = ormLite.DbFactory,
         AutoRegister = true,
         GenerateOperationsFilter = ctx => {
             if (ctx.TableName == "applications")

MyApp/_pages/autoquery/crud.md

@@ -550,11 +550,7 @@ public class QueryRockstarAudit : QueryDbTenant<RockstarAuditTenant, Rockstar>
 }
 ```
 
-To coincide with AutoCRUD there's also support for [declarative validation](https://github.com/ServiceStack/ServiceStack/blob/master/tests/ServiceStack.WebHost.Endpoints.Tests/AutoQueryCrudTests.Validate.cs) which thanks to [#Script](https://sharpscript.net/) lets you define your Fluent Validation Rules by annotating your Request DTO properties. As it's essentially a different way to define Fluent Validation Rules, it still [needs Validation enabled](/validation#validation-feature) to run:
-
-```csharp
-Plugins.Add(new ValidationFeature());
-```
+To coincide with AutoCRUD there's also support for [declarative validation](https://github.com/ServiceStack/ServiceStack/blob/master/tests/ServiceStack.WebHost.Endpoints.Tests/AutoQueryCrudTests.Validate.cs) which thanks to [#Script](https://sharpscript.net/) lets you define your Fluent Validation Rules by annotating your Request DTO properties. As it's essentially a different way to define Fluent Validation Rules, it still [needs Validation enabled](/validation#validation-feature).
 
 ### AutoMap and AutoDefault Attributes
 
@@ -735,7 +731,7 @@ void MyAuditFilter(AutoCrudMetadata meta)
     }
 }
 
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     AutoCrudMetadataFilters = { MyAuditFilter },
 });
 ```
@@ -745,7 +741,7 @@ Plugins.Add(new AutoQueryFeature {
 AutoQuery includes `OnBefore*` and `OnAfter*` (sync & async) events for `Create`, `Update`, `Patch` & `Delete` that can be used to execute custom logic before or after each AutoQuery CRUD operation. E.g. if your system implements their own Audit history via RDBMS triggers, you can use the `OnBefore` **Delete** event to update the record with deleted info before the AutoQuery CRUD operation deletes it:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     OnBeforeDeleteAsync = async ctx => {
         if (ctx.Dto is DeleteBooking deleteBooking)
         {

MyApp/_pages/autoquery/index.md

@@ -166,7 +166,7 @@ container.AddSingleton<IDbConnectionFactory>(c => new OrmLiteConnectionFactory(
     MapProjectPath("~/northwind.sqlite"), SqliteDialect.Provider));
 
 // Add the AutoQuery Plugin
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     MaxLimit = 1000
 });
 ```
@@ -247,7 +247,7 @@ container.AddSingleton<IDbConnectionFactory>(c => new OrmLiteConnectionFactory(
     MapProjectPath("~/northwind.sqlite"), SqliteDialect.Provider));
 
 // Configure AutoQuery to Generate CRUD services
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     MaxLimit = 1000,
     GenerateCrudServices = new GenerateCrudServices {
         AutoRegister = true

MyApp/_pages/autoquery/rdbms.md

@@ -15,7 +15,7 @@ In addition to leveraging ServiceStack's existing functionality, maximizing re-u
 Like ServiceStack's [other composable features](/plugins), the AutoQuery Feature is enabled by registering a Plugin, e.g:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature { MaxLimit = 100 });
+services.AddPlugin(new AutoQueryFeature { MaxLimit = 100 });
 ```
 
 Which is all that's needed to enable the AutoQuery feature. The AutoQueryFeature is inside [ServiceStack.Server](https://servicestack.net/download#get-started) NuGet package which contains value-added features that utilize either OrmLite and Redis which can be added to your project with:
@@ -658,7 +658,7 @@ Which is why we recommend formalizing your conventions you want to allow before
 When publishing your API, you can also assert that only explicit conventions are ever used by disabling untyped implicit conventions support with:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature { EnableUntypedQueries = false });
+services.AddPlugin(new AutoQueryFeature { EnableUntypedQueries = false });
 ```
 
 ## Raw SQL Filters
@@ -670,7 +670,7 @@ Raw SQL Filters also don't benefit from limiting matching to declared fields and
 If safe to do so, RawSqlFilters can be enabled with:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature { 
+services.AddPlugin(new AutoQueryFeature { 
     EnableRawSqlFilters = true,
     UseNamedConnection = "readonly",
     IllegalSqlFragmentTokens = { "ProtectedSqlFunction" },
@@ -805,7 +805,7 @@ client.Get(new QueryRockstars { Skip=10, Take=20, OrderByDesc="Id" });
 Or remove the default behavior with:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature { 
+services.AddPlugin(new AutoQueryFeature { 
     OrderByPrimaryKeyOnPagedQuery = false 
 });
 ```
@@ -961,7 +961,7 @@ AVG, COUNT, FIRST, LAST, MAX, MIN, SUM
 Which can be added to or removed from by modifying `SqlAggregateFunctions` collection, e.g, you can allow usage of a `CustomAggregate` SQL Function with:
 
 ```cs
-Plugins.Add(new AutoQueryFeature { 
+services.AddPlugin(new AutoQueryFeature { 
     SqlAggregateFunctions = { "CustomAggregate" }
 })
 ```
@@ -1038,7 +1038,7 @@ var response = client.Get(new MyQuery { Include = "Total" });
 Alternatively you can always have the Total returned in every request with:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     IncludeTotal = true
 })
 ```
@@ -1204,7 +1204,7 @@ public class MyReportingServices(IAutoQueryDb autoQuery) : Service
 The Aggregate functions feature is built on the new `ResponseFilters` support in AutoQuery which provides a new extensibility option enabling customization and additional metadata to be attached to AutoQuery Responses. As the Aggregate Functions support is itself a Response Filter in can disabled by clearing them:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     ResponseFilters = new List<Action<QueryFilterContext>>()
 })
 ```
@@ -1236,7 +1236,7 @@ class Command
 With this we could add basic calculator functionality to AutoQuery with the custom Response Filter below:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     ResponseFilters = {
         ctx => {
             var supportedFns = new Dictionary<string, Func<int, int, int>>(StringComparer.OrdinalIgnoreCase)
@@ -1354,7 +1354,7 @@ var autoQuery = new AutoQueryFeature()
       q.And(x => x.LastName.EndsWith("son"))
   );
 
-Plugins.Add(autoQuery);
+services.AddPlugin(autoQuery);
 ```
 
 Registering an interface like `IFilterRockstars` is especially useful as it enables applying custom logic to a number of different Query Services sharing the same interface. 
@@ -1385,7 +1385,7 @@ public abstract class MyAutoQueryServiceBase : AutoQueryServiceBase
 Then tell AutoQuery to use your base class instead, e.g:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature { 
+services.AddPlugin(new AutoQueryFeature { 
     AutoQueryServiceBaseType = typeof(MyAutoQueryServiceBase)
 });
 ```
@@ -1414,7 +1414,7 @@ All AutoQuery CRUD operations support auto batch implementations which will by d
 By default it will generate AutoBatch implementations for all CRUD operations and can be changed to only generate implementations for specific CRUD operations by changing:
 
 ```csharp
-Plugins.Add(new AutoQueryFeature {
+services.AddPlugin(new AutoQueryFeature {
     GenerateAutoBatchImplementationsFor = new() { AutoCrudOperation.Create }
 });
 ```

MyApp/_pages/host-configuration.md

@@ -14,28 +14,25 @@ title: AppHost Configuration
 All ServiceStack App's are configured within an AppHost which typically consists of the following elements:
 
 ```csharp
-public class AppHost 
-  : AppHostBase                       // Type of AppHost used, normally AppHostBase
+// Service Name in Metadata Pages
+public class AppHost() : AppHostBase("MyApp"), IHostingStartup
 {
-    public AppHost() : base(
-      "MyApp",                        // Service Name in Metadata Pages
-      typeof(MyServices).Assembly) {} // The ServiceInterfaces Assemblies where all Services are located
+    public void Configure(IWebHostBuilder builder) => builder
+        .ConfigureServices((context, services) => {
+            // Configure ASP.NET Core IOC Dependencies
+            services.AddSingleton<IRedisClientsManager>(c => new RedisManagerPool());
+
+            // Add Plugins to extend your App with additional functionality
+            services.AddPlugin(new AutoQueryFeature { 
+                MaxLimit = 100  // Feature specific configuration
+            });
+        });
 
     // Configure your AppHost with the necessary configuration and dependencies your App needs
-    public override void Configure(Container container)
+    public override void Configure()
     {
         // Set Global AppHost Configuration
-        base.SetConfig(new HostConfig
-        {
-            DebugMode = AppSettings.Get(nameof(HostConfig.DebugMode), false)
-        });
-
-        //Register IOC Dependencies
-        container.Register<IRedisClientsManager>(c => new RedisManagerPool());
-
-        // Add Plugins to extend your App with additional functionality
-        Plugins.Add(new AutoQueryFeature { 
-            MaxLimit = 100  // Feature specific configuration
+        base.SetConfig(new HostConfig {
         });
     }
 }

MyApp/_pages/locode/auditing.md

@@ -26,13 +26,13 @@ public class ConfigureAutoQuery : IHostingStartup
             // Enable Audit History
             services.AddSingleton<ICrudEvents>(c =>
                 new OrmLiteCrudEvents(c.Resolve<IDbConnectionFactory>()));
-        })
-        .ConfigureAppHost(appHost => {
-            appHost.Plugins.Add(new AutoQueryFeature {
+
+            services.AddPlugin(new AutoQueryFeature {
                 MaxLimit = 1000,
                 //IncludeTotal = true,
-            });
-            
+            });            
+        })
+        .ConfigureAppHost(appHost => {
             // Create CrudEvent if it doesn't exist
             appHost.Resolve<ICrudEvents>().InitSchema();
         });

MyApp/_pages/locode/branding.md

@@ -167,6 +167,7 @@ We can add the `[Tag]` attribute to all our Database-First Request DTOs using [A
 
 ```cs
 GenerateCrudServices = new GenerateCrudServices {
+    DbFactory = dbFactory,
     AutoRegister = true,
     ServiceFilter = (op, req) => {
         // Annotate all Auto generated Request DTOs with [Tag("Northwind")] attribute