More in this section
Forums / General Discussions / Visaul Studio 2015 build time so slow for Sitefinity CMS

Visaul Studio 2015 build time so slow for Sitefinity CMS

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. JP
    JP avatar
    0 posts
    13 Sep 2017
    13 Sep 2017
    Link to this post

    We have an existing website with 56 dependence DLLs, it's take 6 minutes to finish a fully build, cause we want sitefinity CMS site and our existing website share same domain name, so we merge our website with a Sitefinity CMS site (extra 208 DLLs  added in bin folder) together, after merge, it take nearly 1 hours to finish a fully build, it's extremely slow, nearly 10 times slower then before. We expect it will be slow that before, but not that much.

    Any idea and/or advice are appreciate,






  2. Jonathan
    Jonathan avatar
    119 posts
    19 Dec 2012
    26 Sep 2017 in reply to JP
    Link to this post
    Can you provide for details about the build process? Are you doing this locally or with a build server (Jenkins, TFS, etc.)? What does the system resources look like? Are they being maxed? Can you increase it?
  3. Darrin Robertson
    Darrin Robertson avatar
    105 posts
    18 Jul 2004
    26 Sep 2017
    Link to this post

    The number of dlls referenced by Sitefinity are just that references. They are not compiled as part of your build. They are just file copied so that won't be your issue.

    You need to look at your build steps and what ones are taking the time. For me, I run my builds in the cloud on VSTS and the longest process is restoring the Sitefinity nugget packages as these have to be downloaded from the Sitefinity nugget service and this can take 3 or 4 minutes.

    I agree with Jonathan and you need (start) to look more at your build system\process first.

3 posts, 0 answered