More in this section
Forums / Deployment / Uploading controls and modules

Uploading controls and modules

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
3 posts, 0 answered
  1. Dino
    Dino avatar
    24 posts
    20 Dec 2008
    07 Jan 2009
    Link to this post
    When developing controls and modules locally and it is time to move to the production server, is it not good practice to move the control/module files that point to code behind files to the server?  I am kind of a newbie with .net.  I was always told to compile my pages to make separate dll's for each page, and move the dll to production.  Does it not matter to upload code behind files on the production server with sitefinity?
  2. SelAromDotNet
    SelAromDotNet avatar
    912 posts
    18 Jul 2012
    07 Jan 2009
    Link to this post
    i believe there isn't that much of a difference between the two. if you compile your own controls into a dll, then you simply reference the assembly to load them into sitefinity. if you upload the ascx/codebehind, then you point to the ascx file instead. either one will work and the end result should be the same. compiles the individual pages automatically when they are first run, so the performance lost by leaving the code behind is minimal. leaving the code behind makes updates easier, since to update a specific page or user control, you just upload the necessary code behind, instead of compiling the whole site and redeploying the dll (which would force the entire application to restart).

    that's my understanding of how it works anyway!
  3. Slavo
    Slavo avatar
    295 posts
    24 Sep 2012
    08 Jan 2009
    Link to this post
    Hello Dino,

    Josh is right - both ways are fine. The codebehind files are there for your ease of development, this is the whole point behind user controls, too. If you would always deploy a compiled assembly, then you would develop custom controls. In this case Sitefinity only allows you to easily upload and register controls, the rest of the work is done by ASP.NET anyway. 

    For building modules you have two options. I don't know which one you're referring to - intra-site or pluggable - but the case is the same. With intra-site you upload user controls and code files, with pluggable - whole assemblies.

    So I would recommend to do whatever is more comfortable for you.

Register for webinar
3 posts, 0 answered