Single page assembly in asp.net

Each page will have its own named assembly (instead of a random name) it is easy to update the application by just updating the required assembly. Disadvantage is the large number of assemblies leading to difficulty in maintainence) and performance hit.

Quote:

From the MSDN article:

Fixed Assembly Names Some scenarios, such as deploying a Web application using the MSI Windows Installer, require the use of consistent file names and contents, as well as consistent directory structures to identify assemblies or configuration settings for updates. In those cases, you can use the -fixednames option to specify that the ASP.NET Compilation tool should compile an assembly for each source file instead of using the where multiple pages are compiled into assemblies. This can lead to a large number of assemblies, so if you are concerned with scalability you should use this option with caution.

Source:
http://forums.asp.net/t/1057767.aspx[^]
http://msdn.microsoft.com/en-in/library/bb398860(v=vs.100).aspx[^]
http://msdn.microsoft.com/en-us/library/ms229863(VS.80).aspx[^]
http://stackoverflow.com/questions/5675228/publish-website-in-visual-studio-use-fixed-naming-and-single-page-assemblies[^]