When does one use Web Parts vs. Full blown ASP.NET application in SharePoint? -


i'm still struggling question i'm trying speed sharepoint, coming asp.net web forms. we're looking use sharepoint exclusively several reasons; 1 of main selling points consolidate our development efforts. example, today have several one-off websites anywhere 1-5 pages (smallish) on several servers, iis installs, etc. , seem bit fragmented.

let's have requirement smallish site (1-5) pages. sharepoint way handle situation? create several web parts, create pages in sharepoint , plug them in or create asp.net web forms application , provide link within sharepoint it?

thanks!

update

i'm going neither. based on feedback , additional research seems application pages i'm looking for. here's article: http://grounding.co.za/blogs/brett/archive/2008/07/13/sharepoint-the-role-of-a-web-part-vs-using-application-pages.aspx

what kind of user experience looking for? makes sense have static page, , it's better allow users ability move things around , create own page. creating web part isn't bad, saw somewhere in time crunch, might take little while on initial learning hump.

it's tough me estimate learning curve because visual studio 2010 make things lot easier available when new sharepoint.


Comments

Popular posts from this blog

c# - How to set Z index when using WPF DrawingContext? -

razor - Is this a bug in WebMatrix PageData? -

visual c++ - Using relative values in array sorting ( asm ) -