SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When to use code based applications and when to use composite application?

share|improve this question
Aren't all applications built on SharePoint effectively composite applications? – SPDoctor Apr 5 '11 at 9:50

If I understand the context of your question, you probably want to work with external data not stored in Sharepoint content database. And the question is whether to build ASP.NEt application and host it under SharePoint web applicatin or do it with BCS which is native to SharePoint. The word "Composite" is being used in SharePoint documentation a lot and it refers you to BCS.

If the functionality can be achieved using BCS, I would stay away from custom code.

I came across a good article in SharePoint Pro magazine and I hope its relevant here:

share|improve this answer
Less custom code == Less maintenance! It will also be easier to migrate any current BCS application to any future version of SharePoint then it might be with custom code. – Gabriel Mongeon Jul 14 '11 at 13:28

Simple really: when a solution built as a Composite Application no longer suits the business requirement, modify components used in the composite application using code.

SPDoctor is right though, anything built on SharePoint is effectively a composite application. Even code-based modifications are used in the context of a composite application.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.