inspired by scott hanselmen's post about What Great .NET Developers Ought to Know, as well as the rush of interviews i've been conducting lately to fill sharepoint positions, i started compiling a list of questions for what a sharepoint
consultant developer/architect (or fill in your own title) ought to know...here it is...
please comment on more questions -- this was my 30 second list that i'll be adding to.
What SharePoint consultants Ought to Know
Everyone who can spell SharePoint
what is SharePoint?what is the difference between SharePoint Portal Server and Windows SharePoint Services? what is a document library? what is a meeting workspace? what is a document workspace? what is a web part?
Mid-level SharePoint Consultant
- what is the difference between a document library and a form library?
- what is a web part zone?
- how is security managed in SharePoint?
- how are web parts developed?
- what is a site definition?
- what is a template?
- how do you install web parts?
- what is the difference between a site and a web?
- what are the differences between web part page gallery, site gallery, virtual server gallery and online gallery?
- what is the GAC?
- what is a DWP?
- what is CAML?
- what are themes?
- what is presence?
- can web parts be connected? if so, how?
- what is a personal view and what is a shared view?
- what is an STP file?
- what is an FWP file?
- can you upload MP3's to SharePoint?
- how does SharePoint support MS Outlook integration?
- how can you extend lists in SharePoint?
- explain the document versioning in SharePoint document libraries
Senior SharePoint Consultant
- where are web part resources contained?
- what are the different installation methods for deploying web parts? and what are the pros/cons?
- what is a ghosted/unghosted page?
- how is site data stored?
- where is metadata for a web stored?
- what is an audience and describe the use?
- what are the trust levels and what is the default trust associated with SharePoint?
- what are the two logging mechanisms for usage statistics?
- what functionality does owssup.dll provide for client side activities?
- what is the difference between a site owner and a site administrator?
- what is STSAdm and what can it be used for?
- can WSS search subsites?
- can you register alerts for users?
- are PDFs searchable?
- what is a SharePoint farm?
- describe a large deployment
- how can you synchronize custom Active Directory attributes to SharePoint?
- if it is anticipated that our organization would need to store 1 terrabyte of documents, what is the recommended configuration and storage requirement?
- describe the implementation of SharePoint and Project Server
- what are the BKMs for workflow and SharePoint?
- explain how you would deploy SharePoint on an extranet
- what is the BKM for maximum number of virtual servers configured for SharePoint on a single box?
- what are the migration strategies for moving sites around?
- what are the archiving strategies?
- describe the search strategies
- can you implement forms-based authentication with SharePoint?
- describe how single sign-on works
after looking at build automation tools like BuildIt.NET and others and looking at the tasks of configuring, etc. as well as the rigidness of what they were build *for*, i began searching elsewhere.
i was referred to finalbuilder (www.finalbuilder.com)
i've been playing around with it for a while and really like it. it integrates with almost all major source control providers as well as common .net “stuff” (like vs.net and reversioning the assemblyinfo file).
it is really full-featured and i've created automated scripts that get the latest from source control, reversion based on certain variables (timestamps and input params--but this could also be script-based), reversions the assemblyinfo classes for a solution (or individual projects), compiles in a configurable build, copies the new build to a version folder, labels the source control build, uploads the completed (successful) build to a server and notifies someone of completion.
really cool stuff and super easy to setup and configure.
if you are looking for build automation, check out www.finalbuilder.com
frans takes a lash at the argument...good position on both sides: http://www.theserverside.net/news/thread.tss?thread_id=31953
don't know what bamf is -- apologies if you are offended...not always the “safest” content on the site (bamf link) but the guy (sharkey) works in the industry and occaisionally has great rants about common things we all face.
at any rate...i had a project i worked my tail off to finish...delivered 2 days early thinking the client really needed it to test.
that was a week ago.
client needs to deliver to their customer tomorrow am.
guess when they started testing.
guess what i'll be doing all night.
i got a question from robertk just a while ago asking where the presence info was when viewing sharepoint with firefox.
what?! you can view sharepoint with firefox?! calm down, yes you can.
ideally the owsbrows.js should be written to check for functionality rather than versions -- maybe render the browseris from the server based on using the .net framework libraries that would be able to determine the “abilities” better.
so if you want it to work, you'll have to jack with ows.js and some other areas as well -- i started looking real quick, but there are other places where it doesn't work and renders the non_ie.js file as well which causes other issues.
wait a minute, get back to getting firefox and sharepoint working...
okay, so it works...most of it. do you get the cool dhtml menu options? no. but it renders and you can modify web parts, etc...just different look...try it and you'll see the changes: some here: http://timheuer.com/images/wssffx1.jpg