Home/ Questions/Q 4610934
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T01:12:01+00:00

I have an ASP.NET 4.0 web application which needs to be pre-compiled into a

  • 0

I have an ASP.NET 4.0 web application which needs to be pre-compiled into a single Assembly. I have played around with the available options and I am getting following:

1. When I compile I get a separate assembly for each page as following:
Multiple assemblies

  1. When I compile I get a single assembly of the web application but on the live server every page is dynamically compiled and a temp file is generated.

Dynamic compiling

  1. I need a way to compile my web application into a single assembly which allows UI updates (HTML changes not the code) and does not generate temporary files.

enter image description here

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The easiest way to do this is to Create (or change) your project as (or to) an “Asp.Net Web Application” rather than the “Asp.Net Web Site”.

    This will cause your project to be compiled into a single dll, rather than the “dll per page” or “dll per directory” scheme that the web sites normally work off of. It will also force you to resolve any type name problems (IE: if you have 6 pages called Default), It’s important when you make a single assembly that fully qualified names be unique.

    This will give you a proper project file (build script) and dump all your dll’s out to the /bin folder when you compile.

    You can then use something like ILMerge to combine all your assemblies in the /bin folder into a single dll if that’s what you want to do. This assumes all your references are managed assemblies, if you have any non .Net libs it’s going to be a lot trickier, although still not impossible.

    • 0