none
ASP.Net - Advanced Precompile Settings - Code Behind not in DLL RRS feed

  • Question

  • Hi there,

    We are experimenting using the Advanced Precompile Settings whilst publishing a website (e.g. WebApplication1 for testing). We would like to have the code behind each page compiled to a separate DLL. We choose the option 'Do not merge. Create a separate assembly ..... '  which looks like it does, but when we change the code behind (e.g. WebForm4.aspx.vb) , and re-publish, we have to ship the WebApplication1.dll to get the code changes. We thought that it would just be the DLL associated with the page that we would have to ship to IIS.

    However if we put the code behind in the actual .aspx file itself, we do indeed get the code in the DLL associated with WebForm4.

    I hope i have made myself clear and is there any way around this?

    Many thanks

    Julian Tucker

    Tuesday, October 1, 2013 12:41 PM

All replies

  • Hi Julian,

    Thank you for posting in the MSDN forum.

    Based on your description, this issue is related to ASP.Net. You could post this issue in http://forums.asp.net where asp.net experts live in, and there you would get dedicated support. If it is related to the web deployment, this forum would be better:

    http://forums.asp.net/1020.aspx/1?VS+Web+Deployment+Projects

    Best Regards,


    Jack Zhai[MSFT]
    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support
    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Wednesday, October 2, 2013 6:15 AM