How do I organize my SharePoint code?

Question

Over time, the code base that I support has grown exponentially. We have many different utility classes, web pages, event receivers, console applications, etc.

Typically, each website lives in a separate DLL (one solution and one project for each web part). Our utility classes have also been largely divided into native DLLs (this includes any specialized list access classes that group together with their beans together in a DLL). This led to a large number of solutions that became more difficult to maintain (updating each solution to Visual Studio 2008 or just trying to find a maze of DLL links).

With my discovery of the SharePoint Guide , I am revising our current code structure. For example, it seems that they recommend merging all your specialized list access classes into a repository (so far we have done the exact opposite, dividing them into DLLs based on what the “solution” for this code is).

Questions: How do I organize my code? How do you decide what is included in the vs project vs folder solution or what happens in the namespace? One solution for each web part?

Answer 1

. , - , Extranet Intranet (eventreceivers, timerjobs, webparts ..) . , () , , , :)