# How we build Targetprocess

DevFeed: [How we build Targetprocess](<https://devfeed.tech/articles/how-we-build-targetprocess-38422.md>)

Original publisher: [Read original article](<https://khmylov.com/2015/06/how-we-build-targetprocess/>)

Author: Andrew Khmylov

Published: 2015-06-18T00:00:00Z

Content type: tutorial

Language: en

Sources: [Despite the odds](<https://devfeed.tech/sources/despite-the-odds.md>)

Topics: [Web Development](<https://devfeed.tech/topics/web-development.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Single-page application (SPA)](<https://devfeed.tech/topics/spa.md>), [ASP.NET](<https://devfeed.tech/topics/aspnet.md>), [C#](<https://devfeed.tech/topics/csharp.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [Back end](<https://devfeed.tech/topics/backend.md>)

Tags: [asp-net](<https://devfeed.tech/tags/asp-net.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [client](<https://devfeed.tech/tags/client.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [routing](<https://devfeed.tech/tags/routing.md>)

## AI overview

A developer explains how Targetprocess is built as a large single-page web application, focusing on its JavaScript frontend, C# server APIs, and ASP.NET application startup. The article introduces authentication, authorization, routing, and ASPX-generated configuration.

## Source excerpt

Preface For the last 2 years my professional career have been diverging further and further away from the path it was set on early. I've started as a desktop application developer a long time ago, occasionally building web APIs on the server-side and doing some mobile app development, and then slowly getting into the frontend web development. Nowadays, working at Targetprocess, I think I'm spending roughly 70% of the time on the frontend (mostly general presentation logic and client-side business rules, not the crazy HTML markup/positioning/styling stuff) and 30% on server-side APIs. This is not a marketing post, but I'd like to give you some context on the things I'll be talking about. Targetprocess is an agile and visual project management tool [1], so you may expect it to be a fairly sophisticated on the visual interface side. Indeed, it's a massive single page web application written mostly in JavaScript on the client-side and C# on the server. At the same time, I see that some fellow developers still don't believe that it's possible to build anything beyond a simple product promotion website or a landing page with a toy language with JavaScript, which is only good for document animation. That's a common misconception I hear quite often from the friends doing mostly server-side and mobile things, and I'd like them (and any other reader) to see how the things look from my point of view. I also think that the details on how we build a large product may be interesting for anyone in the web development business. [2] With no further delay, let's dive right into the technical details! Application startup The entry point to the client app is a usual ASP.NET web application, which handles authentication, authorization and a top-level routing. Those things should be of no surprise for anyone familiar with building web applications with ASP.NET or any similar technology, so I won't go into details here. The authorized user is redirected to the main ASPX file. If you're no