Sharepoint Foundation is free, while both Standard and Enterprise possess the ability to make your wallet shriek in terror.A Sharepoint site or application is comprised of a handful of components: A typical Sharepoint application may contain many sites and/or search sites, which may in turn contain many sub-sites.It’s not as useful when used as an internet site, due to many of its features being geared towards document sharing and collaboration.If you’re familiar with web development using any other CMS or collaborative web application platform, such as Wordpress, Drupal, Umbraco, Dot Net Nuke, Magento, and so on, you’ll be able to grasp Sharepoint conceptually without too much difficulty.Technically, lists and libraries don’t have the same capabilities as databases, despite their contents being stored via SQL Server.Their capabilities and differences are a bit outside the scope of this book, but if you’re interested, you can find more information here: In an extremely general sense, that’s a brief overview of Sharepoint and how a Sharepoint application or intranet site would be constructed.It can all become quite a behemoth, as you can likely imagine.Add to this the fact that users of the Sharepoint application may be able to create their own sub-sites, and you begin to see just how enormous the sheer scope of a Sharepoint application could become, especially for a larger corporation with thousands of employees.
Though a Sharepoint site or application can be used as either an internet or intranet site, it’s most common for businesses to use it as an intranet portal, allowing employees to communicate with one another and collaborate on documents and wiki pages.This publication is intended as a useful quick-start guide for front-end developers delving into the realm of Sharepoint development. If you do happen to stumble across any information in this book that you feel should be corrected post-haste, please don’t hesitate to email me: I will thusly research the correction in question, and assuming it passes my rigorous, time-tested set of qualifications (read: “me lazily Googling for a few minutes”), I will amend this book and credit you somewhere in kind. Furthermore, Sharepoint’s default front-end code (that is, the HTML, CSS, and JS that are used by default within a fresh install of Sharepoint) is so horrific that you’ll likely begin immediately assessing how to rewrite or overhaul the existing code in a desperate attempt to bring it in line with modern web development standards. We’ll also walk through common vocabulary used during Sharepoint development. The answer to all of these questions is “Sharepoint.” Look, I’m not a scientist.As such, a few assumptions will be made about you throughout the book: If any of these assumptions are falsy in nature with regards to your person, you may consider putting this book down and attempting to remedy them. Hell, I’ll even be so kind as to give you a whole truckload of tips and tricks for developing in a more agile manner, and with considerably less mind-numbing agony. First things first, let’s have a short Q-and-A session to clear a few things up: This question stands alongside many of life’s most fundamental questions: what makes the sky blue? I couldn’t possibly be, anyway; I’m here attempting to assist you, while those motherfuckers lyin’ and gettin’ you pissed.In my experience, these are some of the most common terms used on an everyday basis.For a more complete selection of Sharepoint terminology, I highly recommend scouring the following resources: A software framework that runs on Windows. NET applications utilize the Common Language Runtime virtual machine. NET developers to more easily integrate asynchronous calls into their web applications. NET developers that “AJAX” simply describes a technique for building asynchronous web applications, they’ll look at you weird, only having been exposed to the . Resist your urge to punch them and call them mean names.