Custom Coded Applications and ASP.NET Applications

If you have custom applications that consume the AgilePoint APIs, the code used to connect to the AgilePoint API will not work after migrating from IIS mode to Windows Service mode. These include custom applications such as web services, console application, windows services, or ASP.Net applications.

Consuming windows services requires adding few extra lines of code to make the application work with AgilePoint Server running in Windows Service mode.

Prerequisites

These instructions do not apply for applications connecting through SharePoint.

Good to Know

Custom AgileParts, AgileWorks, AgileConnectors and AgileExtenders not require any changes when migrating from IIS mode to Windows Service mode.
AgilePoint recommends you contact Professional Services for help analyzing the custom coded application.
If you followed the AgilePoint coding best practice to consume AgilePoint APIs, then few changes are required to support Windows Service mode.
Follow the same procedures for all of your custom applications.