Service Configuration

CODE Framework does its best to apply smart default settings to services (both server-side and client-side) for the typical type of application build with CODE Framework (business applications). Nevertheless, it is often desirable and necessary to change settings for services. This topic provides an overview of settings applicable to services.

Note that nearly all service settings (which are applied through the standard CODE Framework Configuration System) can be made globally for all services, or individual on a per-service basis. For instance, it is possible to set the allowable message size for all services through the ServiceMessageSize setting, and it is possible to apply that setting for a single service (example: ICustomerService) by adding a ServiceMessageSize:ICustomerService setting.

It is also possible to add settings programmatically in various ways. The most common approach is to use static events fired by the ServiceGarden (server-side) and ServiceClient (client-side) classes. These events grant access to all the low level WCF objects, so any conceivable WCF setting or manipulation can be made. A very common use of this feature is to arbitrarily change the URL a service is hosted at.

Note: This topic was originally called “WCF Service Configuration” when all CODE Framework Services Features were based on WCF. This has not been true for a long time now, since CODE Framework has supported hosting environments such as WebApi and .NET Core. However, the link to this topic has retained the "WCF" moniker in its name for consistency and backwards compatibility.

Server-Side Settings

These settings can be applied in server-side projects (these settings are used by the ServiceGarden class, which in turn is used by all CODE Framework WCF hosting environments):

Client-Side Settings

These settings can be applied in client-side projects (these settings are used by the ServiceClient class)

Defines the security mode for TCP/IP (NetTcp) services. Allowed settings are None, Message, Transport, and TransportWithMessageCredentials.

.NET Core Configuration

In .NET Core, configuration is often done through appsettings.json files. The syntax in those is slightly different as all settings with a colon (:) in them are expressed as hierarchical settings like so:

{
  "ApplicationSettings": {
    "RestServiceUrl": {
      "ICustomerService": "http://localhost:5008/api/customers",
      "IUserService": "http://localhost:5008/api/users"
    }
  }
}

To use this sort of configuration (which is dependency-injected in ASP.NET Core), add the following code to the Startup.cs file's constructor:

public Startup(IConfiguration configuration)
{
    Configuration = configuration;

    var appSettings = ApplicationSettingsJsonHelper.GetDictionaryFromSection(configuration);
    ConfigurationSettings.Sources.Insert(1, new DictionarySettings(appSettings));
}