More in this section
Forums / Developing with Sitefinity / Sharing modules across multiple projects

Sharing modules across multiple projects

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.
2 posts, 0 answered
  1. Glen Loupias
    Glen Loupias avatar
    2 posts
    12 Apr 2006
    29 May 2009
    Link to this post

    I have several websites (projects) running using Sitefinity. I'm developing a custom module that I would like to use amongst all those different websites. I could implement the module into each and every website but that would be a lot of work maintaining updates etc because I would have to update it several times across the various websites.

    Would there be a way to create some sort of one shared repository where I would store custom modules and controls which can be used across all the different websites? That way I only have to update one version which would update all my websites.

    Another thing is ofcourse that the module must be able to identify which website is calling the module, because the usage of the module within every website generates unique content.

    I was thinking about a WebService that renders controls, but that doesn't really work well with Ajax.

    Kind regards,

    Glen Loupias
  2. Ivan
    Ivan avatar
    478 posts
    16 Jun 2015
    01 Jun 2009
    Link to this post
    Hello Glen Loupias,

    we are dividing modules on "pluggable" and "intrasite modules". The idea behind the pluggable modules is that you can take them and easily "plug" into another site. Usually when clients are asking us what kind of module should they develop our first question is on how many websites they plan to use this module.

    You can find more about the module development and these differences in our developer manual in the modules overview section.

    Now, to your question. If the websites don't have to be aware of each other, I suggest you develop a pluggable module and deploy it simply through a single .dll file (take a look at the new approach introduced in Sitefinity 3.6 for this). Then on each update all you need to do is upload a .dll file to the bin folder of the websites.

    If the websites have to be aware of each other, I would still go with this approach, but shared the data via the provider model pattern. More info on provider model pattern and Sitefinity can be found here.

    Any other approach in my opinion may cause more problems and complications than it would bring benefits.

    I hope you'll find this information helpful. Let us know if there is anything else we can do for you.

    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
2 posts, 0 answered