Deploying an ASP.NET Web Service

The generated files and infrastructure files must be compiled before being deployed. The generated files can be compiled by running the CompileWebService.bat file, which is located in the views directory of the bundle. The batch file must specify the correct name of the dynamic linked library of the Web Service being created. Before running the batch file for the first time, open the file and check that the parameter [BundleName] has been replaced with the name of the bundle being generated. This is normally done by the InitializeBundleView.vbs script as described earlier in this section.

When you execute the CompileWebService.bat file it compiles all the C# source files (files with a CS extension) in the <root>\Views folder. These files include the infrastructure files, and the files created by the ASP.NET Web Services generator. The output of the compile process is a .NET dynamic linked library file. The filename is based upon the Bundle name entered when the InitializeBundleView.vbs script was run.

At times, .NET Web Services transactions take more time to complete.

To speed up the .NET Web Services performance on Windows 2012 R2 web server, perform the following:

  1. In CEWindowsAPIPool, set the Activation Type as Library application.

  2. Configure the Component Enabler runtime files on the web server to run as 64-bit applications.

  3. Turn off Windows Authentication on the ASP.NET configuration (if Web Services are not authenticated).

  4. Add the following in Web.config file to bypass the default proxy settings.

    <system.net>
      <defaultProxy>
            <proxy bypassonlocal="true" usesystemdefault="false" />
      </defaultProxy>
</system.net>