I’ve attended many Microsoft conferences in the past, but this is the first conference where I can honestly say I didn’t attend a single disappointing session. After attending the conference, I thought it would make sense to distill some of the highlights.
In my previous blog post, I explained SharePoint Content types. Taking that one step further, let’s now examine SharePoint’s out of the box capability of defining content types on external data in SharePoint. Once the external data is in SharePoint, we can leverage SharePoint’s standard set of functionality, such as defining an out of the box workflow, or the referential relationship between lists, etc.
This is a simple representation of the SharePoint Object Hierarchy. Each of the constituents is described below.
As per MSDN documentation, a content type is a reusable collection of metadata, workflow, behaviour, and other settings for a category of items or documents in a Microsoft SharePoint Foundation 2010 list or document library. Content types enable you to manage the settings for a category of information in a centralized, reusable way.
If there was one overriding theme to the comments that I heard, and made, about Microsoft’s Build 2013 Conference, it was about the lack of session details available to attendees prior to the event. At registration, the only information provided were the titles, times, presenters and the notoriously subjective and ambiguous “level.” Detailed descriptions were not available until an update to the Channel 9 Events app that occurred late on the first day. Deciding between “New Platform Capabilities for Advancing Web Development” and “Improving Developer Productivity and Software Quality and Software Quality with Visual Studio Application Lifecycle Tools” is a Rorschach’s test in nerd perception.
This is the final part of a four-part series on using Team Foundation Server and Team Build to set up a continuous deployment environment.
This is the third part of a four-part series on using Team Foundation Server and Team Build to set up a continuous deployment environment.
This is the second part of a four-part series on using Team Foundation Server and Team Build to set up a continuous deployment environment.