Geek asks and answers

ASP.NET is precompiled into a single assembly

I have an ASP.NET 4.0 web application that needs to be precompiled into a single assembly . I played with the available options and I get the following:

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

  1. When I compile, I get one assembly of the web application, but on a real server, each page is dynamically compiled and a temporary file is created.

Dynamic compiling

  1. I need a way to compile my web application into a single assembly, which allows updating user interfaces (HTML does not change the code) and does not create temporary files.

enter image description here

+3
source share
3 answers

- ( ) () - Asp.Net, "- Asp.Net".

, dll, "dll per page" "dll per directory", -. (IE: 6 Default), , , .

(build script) dll /bin .

- ILMerge, /bin dll, , . , , - .NET libs, , .

+2

AFAIK you cannot update UI / html without recompiling the server using temporary files

All .aspx, .ascx, etc. files converted to source code and then compiled. The only method that ASP.NET provides is to eliminate the possibility of compiling pages and controls, but then your site is no longer being updated. In this case, you always need to redistribute the binaries for each update.

Any specific reason you don't want ASP.NET to create temporary files? This is a perfectly acceptable practice, I think.

0
source

More articles:


All Articles