

Typically the source code for these assets is not deployed to the server. when on a continuous integration or build server.Īssets such as page, user control, and handler code-behind classes, controllers and embedded resources are built using project compilation. Note this assembly could also be built from the command line using msbuild directly, e.g. This assembly is then deployed to your web server along with your application and is loaded by the ASP.NET runtime when your application starts. It compiles any C# or VB files in your project and produces an assembly in the project’s bin folder. Project compilation typically takes place in Visual Studio via the project system and msbuild.

This type of compilation is used by ASP.NET applications built using the project system approach, i.e. There are generally two types of compilation that typically take place in an ASP.NET application: project compilation, and runtime compilation. You can download a preview including new compilers and Visual Studio tooling that enable you to explore upcoming features in the languages and Visual Studio editor, but how do you use these new features in an ASP.NET application? Compilation in ASP.NET applicationsįirst, let’s take a moment to revisit compilation in the context of ASP.NET applications. NET “compiler as a service” that represents the future of languages and compilation for. NET languages team recently announced the availability and open sourcing of a public preview of “Roslyn”, the new.
