• required IMS to spend thousands of dollars on initial price, support and yearly upgrades,
• required IMS developers to spend several days or even weeks configuring them and changing build processes and deployment,
• highly increased IMS developments support requests and decreased client satisfaction by introducing unknown and hardly traceable errors,

... IMS decided to create its own solution.

The goals were clear, the solution had to...

• have very low impact on the original application so no potentially support increasing errors were added,
• have very low impact on the deployment of applications,
• be easy to use and require minimal configuration so it could be easily integrated into many developments,
• be easily integrated into different build processes,

The developed solution: CodeWall (internally known as .NET Source Protector), the first solution to fulfill IMS requirements.

In 2006, after using it to successfully protect several custom .NET Developments, IMS realized its effectiveness and decided to make it commercially available starting CodeWall Technologies.