Base Template — Parameters
Authoritative definitions: .template.config/template.json in ConnectSoft.BaseTemplate. This page summarizes user-visible parameters engineers rely on when scaffolding or extending the kernel.
Discovery
After installing ConnectSoft.BaseTemplate.Installer:
dotnet new connectsoft-base -h
lists current CLI flags for your package version. MSBuild symbols in generated repos may also appear in build/*.props and project conditions.
Naming and ports
| Symbol / area |
Type |
Role |
| Solution / project name |
CLI |
Renames ConnectSoft.BaseTemplate prefix via sourceName |
| HttpPort / HttpsPort |
int |
launchSettings.json bindings (optional; ports can be auto-generated) |
| buildDefinitionNumber |
string |
Optional CI build stamp |
Container and local dev
| Symbol |
Default |
Role |
| Docker |
true |
Dockerfile, compose, k8s samples, Docker-specific appsettings when included |
Observability and health
| Symbol |
Notes |
| Logging |
Choice: Serilog, Log4Net, None |
| OpenTelemetry |
bool; enables instrumentation pipeline |
| ObservabilityStack |
OtelCollector vs DirectExport |
| ObservabilityBackend |
Multi-choice: ELK, Prometheus+Grafana, Seq, Azure Monitor, App Insights, Jaeger, All, … |
| UseApplicationInsights |
Azure Application Insights integration |
| ResourceMonitoring |
Resource utilization metrics |
| HealthCheck |
ASP.NET health checks |
| HealthCheckPath |
Custom path (default /health) |
| HealthCheckPublisher |
Push model to Seq / Application Insights |
| HealthCheckUI |
Dashboard + storage |
| HealthCheckUIStorageProvider |
InMemory or SqlServer |
Configuration providers and feature flags
| Symbol |
Notes |
| FeatureFlags |
Microsoft.FeatureManagement |
| FeatureFlagsProvider |
AppSettings or AzureAppConfiguration |
| AdditionalConfigurationProvider |
e.g. Azure App Configuration |
Persistence
| Symbol |
Notes |
| PersistenceModelType |
None, NHibernate, MongoDb (multi-select in template) |
| NHibernateDialectType |
SqlServer, PostgreSQL, MySql |
| NHibernateSecondLevelCacheType |
None or Redis |
| DatabaseName |
DB / catalog name token in connection strings |
| Migrations |
Structured schema migrations when persistence is on |
| UseAuditNet |
Audit trail |
Service surfaces and integration
| Symbol |
Notes |
| UseRestApi |
REST host / OpenAPI stack |
| UseGrpc |
gRPC service model |
| UseMassTransit |
Messaging (with transport choices in template) |
| UseHangFire |
Background jobs / scheduling |
| ActorModelType |
None, Orleans, Dapr, Akka |
| OrleansGrainPersistence |
e.g. AdoNet vs Azure Blob (when Orleans on) |
AI and data (optional stacks)
When enabled, the template includes AIModel, options, and acceptance features for embeddings, vector stores, ingestion, OpenAI / Azure OpenAI / Ollama, etc. Symbols follow patterns UseOpenAI, UseVectorStore, UseVectorIngestion, and provider-specific flags—see template.json sources.modifiers for exact exclusion lists.
Sample domain scaffolding
The template can generate sample feature and use-case names (FeatureAName, AggregateRootName, actor names, …) for learning and tests. Layer 3 product templates typically replace or extend these with real domain language.