(I think my question is sufficiently different from this question to justify asking it. My question is not about useful SharePoint resources, but what technical skills you actually need...)
I'm a developer (from a Linux background...) and will soon be getting my hands dirty with SharePoint (as both a developer and to some extent an infrastructure guy.) I'm interested to learn what I should brush up on. Just a simple question -- what technical skills do you find you need to know a lot about as someone who develops/deploys SharePoint?
From what I've gathered so far, I would guess at the following list:
What do others think?
As you are doing both dev and admin that is a pretty good list.
In my opinion you missed out the following:
You mentioned XML. It's SharePoint equivalent is CAML. (Collaboration Application Markup Language). You'll need this when creating list/site definitions and deployments (features and solutions). When creating CAML queries LINQ will also be handy as this is the way it's done in SharePoint 2010, whereby it writes the CAML query for you under the LINQ covers. Also REST. And CSS if you are branding. Phew.
In order I would say...
Developers don't typically have to think about AD/LDAP, and most don't touch PowerShell yet.
SharePoint is a very, very large and complex product. You can, like a lot of us, get the basic overview of a lot of the features that are used to run it (such as IIS, ASP.NET, AD, NLB, SQL Server), but in order to do it well you need to be particularly experienced and an expert in these areas.
Becoming an expert in all areas is extremely difficult without having years upon years of experience (see what's required for Microsoft Certified Master SharePoint Server 2007 certification), so what you'll need are many experts in the various areas that make SharePoint the best platform (arguably) there is (specific features like Database Mirroring and Clustering with RBS in SQL Server 2008, to name but one).
Additional: I've just read that you are asking what's needed specifically for a development role, I missed that as you said at first "to some extent infrastructure". My bad, but I think what I say above is still relevant to keep in mind.
As has already been stated SharePoint is a very broad technology stack. If it's a web based technology which is supported on ASP.Net applications then you may need to know it.
Some things not already covered:
Just for reference, the MS TechNet SharePoint 2007 section has a page called "Technologies used by Office SharePoint Server 2007."
It's not a great list to be honest, but here's the bullet points:
this question so we can create a central repository for renaming the various databases. I will try to find as many answers as possible myself, but would appreciate answers from the community as well... multiple SharePoint 2010 farms connected to a single database server then you can see which databases belong to a farm on the following Central Administration screen: http://[Your CA Server]/_admin...SharePoint 2010 appears to continue SharePoint 2007's tradition of automatically creating horribly named SQL Databases. Like many companies we have multiple farms and developer workstations
I am developing a company website/portal in SharePoint, and am trying to figure out the best way to organise it into site collections, sites and subsites -- I'm confused by the terminology I think..., to have each one as a 'subsite' feels like overkill, but that may just be because I'm not used to the terminology. I would ordinarily just think of them as subsections of a website. The 'Support... again be in a separate site collection. I guess my general question is, what are the rules of thumb for when to use a site, when to use a subsite, and when to use a site collection?
) Board description (editable) My questions: What tool is most appropriate for making the forms? Infopath? SPD? VS2010? How do I handle rights to make sure only the board can access the board edit form? What kind of workflow do I use? When do I start the workflow(s)? What do I use to develop the workflow(s)? How do I handle rights when showing the listview with all requests? How can I build...I'm a starting sharepoint developer asked to implement the following scenario in sharepoint 2010. We're a bit lost on the best approach to get started.. I'm really struggling to find the best
I currently have a normal SharePoint list with about 15 columns or so. I need one of the columns to have a list of links. I know SharePoint lets you have 1 link and it also lets you have multiple lines of text... So I thought it would be there as an option, but no such luck. Anyone knows a solution for this? I wasn't able to find any info online, which doesn't happen often. I guess I wasn't looking for the right keywords? If anyone can point me into the right direction, it would be great! Thanks -V p.s. I'm reposting this question in this site due to a suggestion from someone
on the BCS level within Sharepoint then, but I'd still need my rich custom controls, that would display data in unusual ways. What about sandboxed solutions? Is this something I should use... applications inside Sharepoint), but I wouldn't want to do it that way even though it would be much easier for me to develop such applications, because I'm primarily hardcore Asp.net MVC developer... any development experience in Sharepoint I can't really say which ones are going to be imperative for my application. I would like to do it on Foundation, because I can re-sell the app without
added another server to the farm, moved the central admin with the stsadm tool, and removed the old server from the farm. Here is what I have tried: Deployed to two other farms: successfully deployed..., we were lucky enough to still have the soon to be decommisioned server that previously ran Central Admin (Server1). So, I added the server to the farm. Removed the Central Admin from the new Server... appropriately. I can see the status change on the Solution Management page from deploying to deployed. There are no errors in the trace logs or event viewers. However, the 12 hive only contains files
I've been hitting my head against a wall on this one for the last couple of days. I have a pretty simple requirement but I cant see how it can be achieved within a Sandboxed solution. I'm depressed..., and then as part of that activation, drop web parts onto some specific pages. In my case I want to be able to drop it onto the "AllItems.aspx" page of a list, but I'm equally having trouble adding it to the default.aspx home page. I would be happy either way. Note: I want to be able to activate this on existing site, I dont want to create a new Site Definition. Here is what I have tried: Feature Receiver
still point to central admin on WSS3. We tried deleting the alternate access mappings, but SharePoint won't let you delete central admin's mapping. Later, we removed central admin from all of our... a certificate for the server. Why is SharePoint creating alternate access mappings routing an https internal URL by default? How can we move central administration to a new server? We are using...We have several WSS Servers: WSS1 WSS2 WSS3 WSS4 SharePoint thinks that Central Administration is on WSS3 and that it can be access via SSL on port 22641. The problem is that central
I'm trying to understand the SharePoint hierarchy of objects and don't understand SPWebService . Here is what I have: SPFarm contains One or (usually) multiple WebApplications, each contains One or more SPSites which then contain one or more SPWebs I know that each SPWebApplication can have one or more SPContentDatabases and that SPSite is really a child of a Content Database which...? And under what circumstances would someone have more that one SPWebService?