Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

SharePoint site hierarchy for company intranet - multiple sites or sub-sites with one root? -


i'm manager @ mid-size manufacturing company. getting our feet wet sharepoint - far we're got 1 blog in production use> it's ceo's.

we have use cases couple of list-based "applications" simple workflow implemented 1 of our developers. want give our users (at least more tech-savvy ones) ability create , work own departmental sites.

we're concerned, however, might starting out of control if it's adopted (which thing). since don't understand architectural trade-offs, end massive amounts of user data in structure bites down road.

our biggest question whether have multiple sites each use vs. single root site else descends. multiple sites give flexibility make changes or develop new features without creating problems users. however, multiple sites might harder back-up, search, , maintain user profiles/security. single massive site seems reverse cost/benefits.

i'd appreciate insight on 1 vs. many trade-offs, or links resources discuss it. links general sharepoint "enterprise best practices" (sorry) appreciated.

thanks.

however, multiple sites might harder back-up, search, , maintain user profiles/security. single massive site seems reverse cost/benefits.

i consider incorrect. first need clarify when multiple sites, mean multiple site collections or multiple sites - 2 entirely different things.

now if multiple different site collections, in sql database, 1 database, since database created web application level , not site level.

that regarding backup.

coming search , user profiles, again assumption wrong. search , user profiles shared services , work fine long reside in single shared services provider. both farm level services.

a single massive site (if mean site here not site collection) complete no-no , bad design.

i recommend having multiple site collections (something overall department in company hr, finance , it) , have subistes under it. way have 1 database in sql manage , still can scale adding content database existing web application.

again here, assume creating topology @ company level. if @ lower level needs refined.

read articles on taxonomy , site architecture on technet before going ahead one.

planning worksheets sharepoint server 2010 http://technet.microsoft.com/en-us/library/cc262451.aspx  plan sites , site collections http://technet.microsoft.com/en-us/library/cc263267.aspx  sites , site collections overview http://technet.microsoft.com/en-us/library/cc262410.aspx  plan site navigation http://technet.microsoft.com/en-us/library/cc262951.aspx 

Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -