Upgrading From Legacy to .NET Core
Follow the instructions below to upgrade existing Provided Web Services to .NET Core using CoreWCF.
| Note |
|---|
| If using an AMT version with a preview of CoreWCF: Open an existing Generation Set in the AMT Developer Studio and add the parameter COREWCF=TRUE. |
- Open the AMT Developer Studio and generate the Provided Web
Services.
info The new Provided Web Services are located in the application's SoapProvider directory (..\Binaries\Common\SoapProvider). - Copy the all .ini files from the WebProvider directory (..\Binaries\Common\WebProvider) to the new SoapProvider directory.
- Open the IIS Manager to create a new application pool for the Web Service and a new associated application. Point the physical path of the Provided Web Service website to point to the new SoapProvider directory.
- The Provided Web Service needs to be configured using the appsettings.json file found in the
new SoapProvider directory.
Detailed information about configuring the appsettings.json file can be found on the Configuring the Web Service
Files page. - After configuring the appsettings.json, it is necessary to Recycle the Application Pool associated with the Provided Web Service in the IIS Manager.
| Note |
|---|
|
► If HTTP Error 400 occurs when browsing a Web Service, a likely cause is that both "HttpGetEnabled" and "HttpsGetEnabled" are set to False in the appsettings.json file. |
|
► The AmtSoapHost will crash if the appsettings.json file contains an enabled entry with a HTTPS binding (Transport) without a valid security certificate bound to the HTTPS port in the IIS. |
Logfiles are written to the App_Data\Logs subfolder of the SoapProvider folder (..\Binaries\Common\SoapProvider\App_Data\Logs)