Publishing a website in a visual studio: use "Corrected names and individual page assemblies"?

Question

When you start a website from Visual studio 2008, you get a dialog box with some options. One of them is Use Fixed Names and Separate Nodes.

We do not have this, but what is the pro and con of this parameter? Is there a difference in performance or something else? Should or should not this be used?

Without this option, we get 774 files in the bin folder after publication, when we check it, we get 1320 files, because each ascx gets its own dll.

If we check this, will fixed names be fixed only on my computer? Or is it the same when a colleague publishes a website?

Answer 1

Corrected named assemblies provide flexibility for page-level updates. Since each page will have its own named assembly (instead of a random name), it is easy to update the application by simply updating the necessary assembly. The disadvantage is the large number of assemblies (they are difficult to maintain), as well as a slight decrease in performance.

More about this article: http://msdn2.microsoft.com/en-us/library/ms229863(VS.80).aspx

Source of answer: http://forums.asp.net/t/1057767.aspx

From an MSDN article:

, , - MSI Windows, , . , -fixednames , ASP.NET . , , .