Net: You are trying to use a reference variable who’s value is Nothing/null.When the value is Nothing/null for the reference variable, that means it is not actually holding a reference to an instance of any object that exists on the heap. Net, you are trying to access a string that has not been initialized. You can’t even compile code like the following in C# Remember, a string is a reference type (a character array) that has to have a value.This is most common in classes where you are using class-wide instantiated objects.If you create and drop your objects within each method, this isn’t going to be a problem, and you are actually following a better guideline by creating at the last necessary moment, and destroying at the first possible moment, not to mention avoiding possible exceptions like Invalid Reference Exception.Additionally, browser support tends to be a little spotty.Corporations tend to be the most common adopters of Sharepoint, and as many of these organizations explicitly utilize Windows machines, it can be assumed that Internet Explorer will generally be the most common browser used to access the Sharepoint site.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. As one could reasonably assume, though the information contained herein should be largely accurate and trustworthy, it is by no means comprehensive, and various aspects of front-end development for Sharepoint could very well be omitted. If you’re reading this book, it can logically be assumed that you’ve been tasked with completing a project that involves working with Sharepoint; in fact, it’s probably safe to make the assumption that you’re a front-end developer who stumbled upon this text after hysterically Googling “MICROSOFT SHAREPOINT SOME1 PLS HELP,” tears streaming down your pudgy cheeks, fat fists wildly bashing the keyboard of your Mac Book Pro. I found myself in exactly the same position some time ago; well, aside from the crying, anyway. Sharepoint itself is chock-full of bad practices and front-end code taboos that will leave you scratching your head (and potentially crying, since you’ve apparently shown a propensity for doing that, Nancy). This quick-start guide was written to assist you, the mid- to senior-level front-end developer, better understand how Sharepoint is constructed, what its weak points are, and how to develop for it more intelligently and more quickly.
In general, a single Sharepoint site (of which there could be many within the whole application, remember) is composited in the following manner: That is, a list/library full of data is fed into a web part, which displays that data on a page, which is a portion of an overall site or sub-site. If you’ll recall, I mentioned that Sharepoint does bear some similarities to other CMSes you might be familiar with; for example, you’ve probably grasped that this flow of information is pretty similar to the way a CMS like Wordpress would display data via a widget that you’ve placed on the page.
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 can all become quite a behemoth, as you can likely imagine.
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.
However, given its sheer size and complexity, Sharepoint poses a rather interesting set of problems and barriers when it comes to both development and use.