Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 5 of 5

Thread: Update individual ASPX file after the first deployment

  1. 10-07-2009, 04:57 PM #1
    laomao is offline Member
    Join Date
    Jan 2009
    Posts
    36

    Default Update individual ASPX file after the first deployment

    Compiling individual ASP.NET pages

    Hi,

    ASPDNSF is a big application and I usually publish it to a "BUILD" folder to precompile it (single dll for a single page: second option in VS8).

    Sometimes I change only one or two ASPX files and even then it may be some HTML within the file. I would like to be able to just precompile this one page in VS rather than republishing the whole site which takes quite a while.

    I would then place the new precompiled ASPX and related Page DLL to the online server.

    How would you recommend I do this at a "per page" level?

    Thanks,
  2. 10-09-2009, 09:36 AM #2
    MarkC is offline Developer
    Join Date
    Aug 2006
    Posts
    166

    Default

    you can use Precompiling with Updatable UI, that way you will still be able to do modifications to the aspx pages.
    just leave the "allow this procompiled site to be updatable" checked on the publish form or -u if you use the command line compiler

    here's a good resource:
    http://www.asp.net/learn/hosting/tutorial-15-cs.aspx
  3. 10-15-2009, 07:11 AM #3
    laomao is offline Member
    Join Date
    Jan 2009
    Posts
    36

    Default The site becomes very slow after "Precompiling with Updatable" option is added

    Hi,

    This is what I did at the Publish Web Site in VS2008:

    I checked the first 2 checkboxes:

    • Allow this precompiled site to be updatable
    • Use the fixed naming and single page assemblies

    and then compiled the site into the "BUILD" folder and copied it over to the web server.

    After that the site becomes very slow (not the first time but always slow).

    Please help!
    Last edited by laomao; 10-15-2009 at 01:20 PM. Reason: typo
  4. 10-15-2009, 02:19 PM #4
    laomao is offline Member
    Join Date
    Jan 2009
    Posts
    36

    Default Does it has something to do with VSS (Visual Source Safe)?

    One thing to add:

    the site is hooked with the VSS -- it is pointed to a Shadow Folder in the VSS.

    Do you think the VSS keeps triggering the recompilation of the site so as to cause its slow performance?

    Thanks
  5. 10-16-2009, 08:34 AM #5
    MarkC is offline Developer
    Join Date
    Aug 2006
    Posts
    166

    Default

    precompiling with updatable ui will still incur a slight overhead but definitely faster than the default.
    Have you checked the web.config, maybe you left the debug=true or something.
    With regards to VSS, why do you have the live site hooked up with VSS. Although i'm not sure if that's the one that triggered the precompilation, one thing you can use to determine that is to use a tool like filemon to monitor changes to the file.
    Are you sure that it was precompilation that made a the perf difference, it could be other factors as well.