locked
Azure - Web Application - Publish RRS feed

  • Question

  • User-1724551695 posted

    Hi,

    We have created a web application by using the below step in C# Dot Net (Not used MVC).

    Open Visual Studio 2013 --> File --> New --> Project --> Visual C# --> Select ASP.NET Web Application --> Select Web Forms

    After completing the development, we have published our project. While publishing we have select the below option.

    "Do not merge. Create a separate assembly for each page and control"

    After publishing we have checked the published files, there is no separate assembly (separate DLLs) for each web forms.

    Please help us to get the separate DLLs for each web forms while publishing the project.

    Thank you in advance.

    Tuesday, January 23, 2018 7:25 AM

All replies

  • User283571144 posted

    Hi sierrateccloud,

    sierrateccloud

    We have created a web application by using the below step in C# Dot Net (Not used MVC).

    Open Visual Studio 2013 --> File --> New --> Project --> Visual C# --> Select ASP.NET Web Application --> Select Web Forms

    After completing the development, we have published our project. While publishing we have select the below option.

    "Do not merge. Create a separate assembly for each page and control"

    After publishing we have checked the published files, there is no separate assembly (separate DLLs) for each web forms.

    Please help us to get the separate DLLs for each web forms while publishing the project.

    According to your description, I guess you used web application to publish to the azure web app.

    As far as I know, if you using web application projects some of the advantages of dynamic compilation are lost, it will just generate one assembly.

    If you using Web site projects, it will separate DLLs for each web forms while publishing the project.

    The difference between web application projects and  web site projects:

    For web application projects, you typically build the project in Visual Studio or by using the ASP.NET batch compiler on a computer that is not the production IIS server. All code-behind class files and standalone class files in the project are compiled into a single assembly, which is then put in the web application project's Bin folder. (The .aspx and .ascx files are compiled dynamically in a manner similar to what is done for web site projects.)

    For web site projects, you do not have to manually compile the project. web site projects are typically compiled dynamically by ASP.NET (on both the development computer and the production IIS server). You can choose between batch compilation mode, which typically produces one assembly per folder, and fixed compilation mode, which typically produces one assembly for each page or user control.

    More details, you could refer to this article.

    Best Regards.

    Brando

    Wednesday, January 24, 2018 3:00 AM