x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 2 replies
  • Subscribers 74 subscribers
  • Views 261 views
  • Users 0 members are here
Browse Forums
Announcements
106
topics
32
replies
General Discussion
6k
topics
18k
replies
bradd_1

.net solution project best practice question

Posted By

Just wondering if there is a best practice surrounding custom .net projects. Please note I'm not asking about .net practices, but best practice with regards to Sage CRM customization specifically. Is it better to put each custom set of pages in its own project and generate a dll for each customization? Or is it ok to have them all in the same project sharing the same dll? Just didn't know if one or the other had an affect on Sage CRM, specifically with regards to performance.

  • 0

    Bradd

    I think the largest factor in designing your .Net projects is actually maintenance. It makes sense to me to create my own projects focussed around a particular functional area. So if I work on creating a new entity or group of entities (for example Project with Project Phases and Project Objectives) then I would create that in a distinct project.

    If you think about a Sage CRM instance that has implemented the Sage Yammer component and the Facebook integration then these are delivered each with their own assemblies. It allows each to be maintained/patched/upgraded separately without affecting the other.

  • 0

    This would be my preferred solution design, was just curious as I'd not seen any articles specifically mentioning this subject. Thanks Jeff!

*Community Hub is the new name for Sage City