Be prepared to hit numerous brick walls if you try to build something complex and robust using SharePoint.
Also if you want something to work on future devices, be aware that SharePoint is built heavily on aspx, which is pretty much obsolete. You'll have far more flexibility if you built from scratch using something like MVC, Razor and HTML 5 Just my humble opinion :-) Mark On 18/04/12 3:12 PM, "Tom Ng" <ato...@gmail.com> wrote: Thanks Neil for quick reply. I have a couple more custom applications (web based). And they are all complex systems. Using SharePoint lists won't be enough. On Wed, Apr 18, 2012 at 2:54 PM, Neil Haddley <neil.hadd...@darkblueduck.com> wrote: Tom, You should consider how Microsoft has put together Microsoft CRM 2011 and Microsoft Project Server 2010... This should give you a clear ideal of what approach would work best. Kind regards Neil On Tue, Apr 17, 2012 at 11:47 PM, Tom Ng <ato...@gmail.com> wrote: Hi Everyone, Just a quick question. If you were building a complex web system (where you have complex relationships in your database say equivalent to a lightweight CRM system), I am curious if you'd build this in a separate asp.net <http://asp.net> or ALL (many mini web parts) in SharePoint? Do you keep your custom system development inside your SharePoint intranet always? (to take advanteage of user security/profiles etc?) _______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
