views:

689

answers:

5

I recently stepped into a project that is using Telerik Sitefinity CMS with custom user controls. I would like to get the developers off of the production server. Does anyone have any experience with deploying a Sitefinity site by means of publication (precompiled .DLL)?

Any discussion of benefits, disadvantages, or potential issues would be welcome.

+1  A: 

Hi Jim,

Could you expand on what you mean by "get the developers off the production server"? I'm not sure how that relates to the site being precompiled... that sounds like two separate issues to me.

We use Sitefinity at our site for a few projects, at least two of which have a bunch of custom user controls, yet we don't allow any developers access to the production servers. Also, our sites aren't pre-compiled.

(we would very much prefer that Sitefinity allowed Web Applications rather than Website projects, but alas no..)

Scott Ferguson
Thanks, Scott. On further investigation, it turns out that some custom security work done by a past consultant, and various misconfigurations, have the site jacked up to the point that it will not run in Visual Studio (more's the wonder that it is working on server, actually).
Jim Snyder
A: 

Take a look at the user manual under the topic "Migrating Projects to the Production Web Server"

http://www.sitefinity.com/documents/UserManual_3_5.pdf

That should walk you through the process of deploying to a production server.

BeaverProj
The link above appears to be out of date (Telerik: you might want a redirect in there) - the URL for their current user manual is this:http://www.sitefinity.com/documents/UserManual_3_7.pdf
arrocharGeek
Thanks James for the update!
BeaverProj
A: 

Hi,

For one of the projects, we are using sitefinity 3.7. Again we couldnot find any documentation regarding to how to deploy a sitefinity side to a production server. does anyone have any experience?

Thanks a lot .

Best Regards

ugur acar
A: 

In a couple of projects we have used sitefinity installations as web application projects -> precompiled.

We have had good experiences with do that. Sometimes even seen performance increases over a non precompiled version especially on sub pages that are not frequently visited (think of all the sitefinity backed sub pages that are usually visited only a few times, they suddenly just appear without any loading time).

After a redeployment you should definitely trigger a page load yourself since the first time it has to load the assembly, rather than just the requested page and you don't want any of your users to experience that loading time.

There a couple of guides how to convert sitefinty to a web application that can be precompiled. I have found that this one is the most accurate one and even has a backreference to older versions: Installing Sitefinity as a Web Application in Visual Studio:

ntziolis
A: 

The most up-to-date User Manual can be found in the Sitefinity Developer Network here: http://www.sitefinity.com/devnet/user-manual.aspx

Telerik | Sitefinity Team

Anton