Everything Sharepoint

Passed the Security+ SY0-501 Exam

2018-09-29T12:11:00.001-06:00

I recently passed the Security+ SY0-501 Exam.

Here are some study materials that I used to pass the exam..

Practice exam questions here.
Transcender exam questions, not free but available for purchase from here.
The CompTia Certification Exam Objectives document available here.
I also purchased ($14.99) a Security+ Practice tests on an iPhone app available here.

The test started with 4-5 simulation type questions that required dragging and dropping list items, the items were similar to these:

Biometric reader
Mantrap
Cable lock
Safe
Locked cabinet
Proximity reader

The simulations displayed diagrams where you could assign the appropriate list items.

One of the simulations involved configuring a wifi setup choosing from items like WPA2, Radius and having to configure the selection.

One showed an office and a data center and had options for things like proximity reader, cctv, biometric reader, etc.

There were a few questions showing log files and asked things like what is the vulnerability in the log file.

One had a help desk ticket with no text data, it just showed it was TCP and port 686 and asked what it pertained to.

One asked what was the best way to sanitize a removable device and had options like low level format, overwrite, etc. it didn't have options like degauss or purge or destroy.

One question asked about netcat and how to connect to ports. Know how to make a connection (nc -4 [host] [port number])

One asked the difference between arp poisoning and mac flooding, one answer was mac flooding works across routers.

These are some of the questions and topics that I remember from the exam, there is such a broad amount of material to study, it makes this exam pretty difficult.

Good Luck!

SharePoint 2019 Public Preview

2018-09-06T08:15:00.000-06:00

Follow the link below to read the blog about the preview...

SharePoint 2019 Preview

Download

Download the SharePoint 2019 Public Preview

SPFX Host a SharePoint solution's files in a SharePoint Online Document Library CDN

2017-04-06T12:03:00.000-06:00

Introduction

In my previous post

'SPFX SharePoint Online Responsive Web Part using the SharePoint Framework, Bootstrap, JQuery, JQuery Datatables and Toastr'

I demonstrated using the SharePoint Framework (SPFx) to create and deploy a solution to SharePoint Online (SPO), the solution referenced several JavaScript libraries that once deployed to SPO, would look back to the localhost dev environment for these libraries and other required files. This means that in order for the web part to be added to the page or viewed correctly the Gulp serve command must be initiated before you can successfully access the web part.

To cut this cord and make the solution self sufficient, a Content Delivery Network (CDN) must be provided to enable SharePoint to access the solution resources it needs to correctly render. All of the JavaScript libraries have externally hosted CDN's and these can be added to the project using the method below for bringing in the libraries.

For example, in the webpart.ts file adding the following lines will allow the web part to reference css and 'js files.

import { SPComponentLoader } from '@microsoft/sp-loader';

SPComponentLoader.loadCss('https://maxcdn.bootstrapcdn.com/font-awesome/4.6.3/css/font-awesome.min.css');
SPComponentLoader.loadCss('https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css');

SPComponentLoader.loadScript('https://cdnjs.cloudflare.com/ajax/libs/jquery/3.1.1/jquery.min.js', { globalExportsName: 'jQuery' }).then((jQuery: any): void => {
SPComponentLoader.loadScript('https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/js/bootstrap.min.js',  { globalExportsName: 'jQuery' }).then((): void => {        
    });
});

But if we are referencing external JavaScript libraries and want these libraries un-bundled during the development process, which I prefer, these references would be included in the config.json file using the method below.

For example, to bring in JQuery and Toastr libraries, the following lines can be added to the config.json file in the externals section.

{
  "entries": [
    {
      "entry": "./lib/webparts/spfx/SpfxWebPart.js",
      "manifest": "./src/webparts/spfx/SpfxWebPart.manifest.json",
      "outputPath": "./dist/spfx.bundle.js"
    }
  ],
  "externals": {
    "jquery": {
      "path": "node_modules/jquery/dist/jquery.min.js",
      "globalName": "jQuery"
    },
     "toastr": {
      "path": "node_modules/toastr/toastr.js",
      "globalName": "jQuery"
    }
   },
  "localizedResources": {
    "spfxStrings": "webparts/spfx/loc/{locale}.js"
  }
}

Then in the webpart.ts file we can reference these external libraries using the following lines.

import * as jQuery from 'jquery';
import * as toastr from 'toastr';


This will cause the web part thats added to SharePoint Online to look back to the localhost 
development machine for these files. To change that, we'll make the following configuration updates.

Prerequisites


SharePoint Online Tenant
SharePoint Online Document Library Location for CDN/Files
SharePoint Online Management Shell - Download




Create a CDN hosted on your SharePoint Online Tenant

Launch the SharePoint Online Management Shell and enter the following commands replacing 

contoso with your tenant name.



#Authenticate to your tenant
$creds = Get-Credential
Connect-SPOService -Url https://contoso-admin.sharepoint.com/ -Credential $creds

#Enable Public CDN in the tenant
Set-SPOTenant -PublicCdnEnabled $true

#Create CDN to your SPO document library
New-SPOPublicCdnOrigin -Url "https://contoso.sharepoint.com/siteassets/folder1"

#Verify CDN successfully created
Get-SPOPublicCdnOrigins





Configure SharePoint Solution for CDN

Locate the write-manifest.json file in the config folder of the SharePoint solution



Update the file from this

{
  "cdnBasePath": "<!-- PATH TO CDN -->"
}




To this 



{
  "cdnBasePath": "https://contoso.sharepoint.com/siteassets/folder1"
}




Create files for deployment
From the integrated terminal window type the following
Gulp --ship

This will create the files for deployment in the temp - deploy folder


Copy Files to SharePoint Online

Copy all of these files into the CDN folder at - https://contoso.sharepoint.com/siteassets/folder1

The document library should look similar to this



From the integrated terminal window type the following

Gulp package-solution --ship

Deploy the solution to the SharePoint App Catalog - Instructions for this can be found in my

previous post Here

You should no longer need to run Gulp serve for your web part to correctly render.

SPFX SharePoint Online Responsive Web Part using the SharePoint Framework, Bootstrap, JQuery, JQuery Datatables and Toastr

2017-04-05T23:05:00.000-06:00

SPFx - Responsive Web Part

Introduction

In this blog post I'll describe how to get going with the new SharePoint Framework and take an existing SharePoint Add-In detailed in a previous blog post Here and package this up using the recently released SharePoint Framework (SPFx).

This post describes building a SharePoint solution that includes a web part that reads data from a custom SharePoint list and allows full Create Read Update Delete (CRUD) functionality from a JQuery Datatables responsive client side grid. The SharePoint solution defines a custom list which will be provisioned with some default data and deployed to SharePoint using a feature. The responsive grid also uses Bootstrap for styling and modal dialogs presented when adding, deleting, editing and updating list data. In addition Toastr is used to display notifications when items are successfully deleted from the list.

There are some differences between the previous SharePoint Add-Inn and the new SPFx technique, for starters, I had to drop bootstrap-dialog because I could not get this working in the SPFx context. Instead I'll be using the Bootstrap Modal method which looks and feels the same.

The SharePoint Add-In will be modified using the latest tools and development techniques into a web part and deployed to SharePoint Online. A custom list will also be deployed to the SharePoint online site called SpfxFiles, the list will be pre-populated with 5 entries to display in the JQuery DataTables Grid. A SharePoint feature will be used to deploy the custom list.

Prerequisites

Install NodeJS
Install Visual Studio Code
Install Yeoman and gulp
Install Yeoman SharePoint generator
SharePoint Online Tenant
SharePoint Online App Catalog Site
SharePoint Online Developer Site

Setup your SharePoint Development Environment

Download Visual Studio Code Solution - Here

Steps

Create a new folder using Windows Explorer - name: Spfx

Launch Visual Studio Code and open the folder you just created

Open Folder

Select View | Integrated Terminal to allow running NodeJs commands from Visual Studio Code

View - Integrated Terminal

From the Integrated Terminal Type: Yo to start the Yeoman SharePoint Generator and create a new project for this demonstration.

Note: This is very similar to selecting File | New Project in Visual Studio, this will create the boiler plate code for getting a SharePoint solution created.

Type: yo

Select @microsoft/sharepoint

Enter a solution name: spfx

Select use the current folder for location to put the files

Select current folder

Select No JavaScript web framework

Enter a web part name: spfx

The project will take several minutes to complete, once this process is complete type the following commands - one at a time from the Integrated Terminal command line.

Node Packages/Types (Install these individually)

npm install jquery --save
npm install @types/jquery --save-dev
npm install tether --save
npm install @types/tether --save-dev
npm install bootstrap --save
npm install @types/bootstrap --save-dev
npm install datatables.net --save
npm install @types/datatables.net --save-dev
npm install datatables-select --save
npm install @types/datatables.net-select --save
npm install toastr --save
npm install @types/toastr --save

Verify jquery was installed correctly by expanding the node_modules folder in the spfx folder structure and scrolling down to the jquery folder, inside this folder should be a dist folder and inside that folder should be the file that will be referenced in the config.json file jquery.min.js. The remainder of the downloaded packages can be verified using this same method.

Include Node Packages in solution

Now that all of the required node packages have been installed, alter the web part code to include these packages in the solution.

Modify config.json

Starting with Jquery add the following lines to the config.json file in the config folder - externals section. These two libraries will be bundled separately from the other libraries in the project.

{
  "entries": [
    {
      "entry": "./lib/webparts/spfx/SpfxWebPart.js",
      "manifest": "./src/webparts/spfx/SpfxWebPart.manifest.json",
      "outputPath": "./dist/spfx.bundle.js"
    }
  ],
  "externals": {
    "jquery": {
      "path": "node_modules/jquery/dist/jquery.min.js",
      "globalName": "jQuery"
    },
     "toastr": {
      "path": "node_modules/toastr/toastr.js",
      "globalName": "jQuery"
    }
   },
  "localizedResources": {
    "spfxStrings": "webparts/spfx/loc/{locale}.js"
  }
}


There are multiple methods for including JavaScript libraries and css into a SharePoint solution, 
I'll demonstrate a couple of different ones. The first is to add the external library as a
non-bundled library by including an entry in the config.json externals shown above and then in the 
SpfxWebPart.ts file adding the following entries.

In the project folder structure expand the src folder, expand the webparts folder, expand the spfx
folder. In the spfx folder select the SpfxWebPart.ts file and add the following lines to near the 
top of the file.

import { SPComponentLoader } from '@microsoft/sp-loader';

import * as jQuery from 'jquery';
import * as toastr from 'toastr';

require('node_modules/tether/dist/js/tether.min.js');
require('node_modules/bootstrap/dist/js/bootstrap.min.js');
require('node_modules/datatables.net');
require('node_modules/datatables-select/dist/js/datatables.select.min.js');

SPComponentLoader.loadCss('https://cdnjs.cloudflare.com/ajax/libs/tether/1.4.0/css/tether.min.css');
SPComponentLoader.loadCss('https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.min.css');
SPComponentLoader.loadCss('https://cdn.datatables.net/1.10.13/css/jquery.dataTables.min.css');
SPComponentLoader.loadCss('https://cdnjs.cloudflare.com/ajax/libs/toastr.js/latest/toastr.min.css');

The first statement imports the SPComponentLoader which can be used to bring in javascript and css files from external sources.


The import statements above for jquery and toastr will bring in the files referenced in the config.json 


externals section.



The second method for bringing in external JavaScript libraries is to use the require statement

used above and this will ensure the node modules that were pulled down earlier will be available 

for use within the solution.

for both methods used above the css files will be referenced using the SPComponentLoader shown 

above.

The entire SpfxWebPart.ts file will be shown here below
import { Version } from '@microsoft/sp-core-library';
import {
  BaseClientSideWebPart,
  IPropertyPaneConfiguration,
  PropertyPaneTextField
} from '@microsoft/sp-webpart-base';
import { escape } from '@microsoft/sp-lodash-subset';
import { SPComponentLoader } from '@microsoft/sp-loader';
import styles from './Spfx.module.scss';
import * as strings from 'spfxStrings';
import { ISpfxWebPartProps } from './ISpfxWebPartProps';

import * as jQuery from 'jquery';
import * as toastr from 'toastr';

require('node_modules/tether/dist/js/tether.min.js');
require('node_modules/bootstrap/dist/js/bootstrap.min.js');
require('node_modules/datatables.net');
require('node_modules/datatables-select/dist/js/datatables.select.min.js');

SPComponentLoader.loadCss('https://cdnjs.cloudflare.com/ajax/libs/tether/1.4.0/css/tether.min.css');
SPComponentLoader.loadCss('https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.min.css');
SPComponentLoader.loadCss('https://cdn.datatables.net/1.10.13/css/jquery.dataTables.min.css');
SPComponentLoader.loadCss('https://cdnjs.cloudflare.com/ajax/libs/toastr.js/latest/toastr.min.css');

export default class SpfxWebPart extends BaseClientSideWebPart<ISpfxWebPartProps> {

  public render(): void {
    this.domElement.innerHTML = `
    
     <div class="container">
        <h1><span class="label label-primary">SPFX Grid Data Consumed via SharePoint Rest API</span></h1>
        <div id="toolbar">
            <button type="button" value="Files" class="btn btn-info" onclick="Javascript: location.href = '../Lists/SpfxFiles'"><span class='glyphicon glyphicon-upload'></span> File List</button>
            <button type="button" class="btn btn-success addNewFile"><span class='glyphicon glyphicon-plus'></span> Add New File</button>
        </div>
   <p></p>
 <div id="FilesPanel">
 <table style="width: 100%;">
 <tr>
     <td>
        <div id="FilesGrid" style="width: 100%"></div>
     </td>
 </tr>
 </table>
 </div>
  
 <!-- Bootstrap Modal Dialog for new/edit files-->
<div class="modal fade" id="myModalNorm" tabindex="-1" role="dialog" aria-labelledby="myModalLabel" aria-hidden="true">
    <div class="modal-dialog">
        <div class="modal-content">
            <!-- Modal Header -->
            <div class="modal-header">
                <button type="button" class="close" data-dismiss="modal">
                       <span aria-hidden="true">&times;</span>
                       <span class="sr-only">Close</span>
                </button>
                <h4 class="modal-title" id="myModalLabel">
                    Add New File
                </h4>
            </div>
            <!-- Modal Body -->
            <div class="modal-body" id="modalBody">
                <form role="form" id="fileForm">
                  <div class="form-group">
                    <label>File Title</label>
                      <input class="form-control" id="fileTitle"/>
                  </div>
                  <div class="form-group">
                    <label>File Name</label>
                      <input class="form-control" id="fileName"/>
                  </div>
                  <div class="form-group">
                    <label>File Type</label>
                      <input class="form-control" id="fileType"/>
                  </div>
                     <div class="form-group">
                    <label>Team</label>
                      <input class="form-control" id="team"/>
                  </div>
                  <!-- hidden controls -->
                  <div style="display: none">
                      <input id="etag" />
                      <input id="fileId" />
                  </div>
                  </form>
                  <div class="modal-footer">
                      <button type="button" class="btn btn-danger" data-dismiss="modal" onclick='updateFormLabel();'>
                        Cancel
                      </button>
                      <button type="submit" class="btn btn-primary" id="fileFormSubmit">
                        Submit
                      </button>
                  </div>
            </div>
        </div>
    </div>
</div>
</div>
 <!-- Bootstrap Modal Dialog for delete files-->
<div class="modal fade" id="deleteFiles" tabindex="-1" role="dialog" aria-hidden="true">
    <div class="modal-dialog">
        <div class="modal-content">
            <!-- Modal Header -->
            <div class="modal-header">
                <button type="button" class="close" data-dismiss="modal">
                       <span aria-hidden="true">&times;</span>
                       <span class="sr-only">Close</span>
                </button>
                <h4 class="modal-title" id="myModalLabel2">
                    Delete Confirmation
                </h4>
            </div>
            <!-- Modal Body -->
            <div class="modal-body" id="modalBody2">
                <p>Are you sure you wish to delete this item?</p>
                 <form role="form" id="deleteForm">
                  <!-- hidden controls -->
                  <div style="display: none">
                      <input id="deleteId" />
                  </div>
                  </form>
                  <div class="modal-footer">
                      <button type="button" class="btn btn-danger" data-dismiss="modal" '>
                        Cancel
                      </button>
                      <button type="submit" class="btn btn-primary" id="deleteConfirmationSubmit">
                        Submit
                      </button>
                  </div>
            </div>
        </div>
    </div>
`;
    var RestUrl = "../_api/lists/getbytitle('SPFxFiles')/items";
    $(document).ready(function () {
        PopulateGrid();
        $('#fileFormSubmit').click(function (e) {
            //Check for edit or new and call update or add function
            if ($('#myModalLabel').html() == 'Add New File') {
                addFile($('#fileTitle').val(), $('#fileName').val(), $('#fileType').val(), $('#team').val());
            } else {
                UpdateFiles($('#fileId').val());
            }
        });
        $('#deleteConfirmationSubmit').click(function (e) {
          var restUrl = "../_api/web/lists/GetByTitle('SPFxFiles')/items(" + $('#deleteId').val() + ")";
          jQuery.ajax({
              url: restUrl,
              type: "DELETE",
              headers: {
                  Accept: "application/json;odata=verbose",
                  "X-RequestDigest": $("#__REQUESTDIGEST").val(),
                  "IF-MATCH": "*"
              }
          });
          toastr.success("File Successfully Deleted.", "Success");
          //PopulateGrid();
        });
    });
  
function PopulateGrid() {
    //Clear datatables
    $('#FilesGrid').empty();
    //Get File list items
    $.ajax({
        url: RestUrl,
        method: "GET",
        headers: {
            "accept": "application/json;odata=verbose"
        },
        success: function (data) {
            if (data.d.results.length > 0) {
                //construct HTML Table from the JSON Data
                $('#FilesGrid').append(GenerateTableFromJson(data.d.results));
                //Bind the HTML data with Jquery DataTable
                var oTable = (<any>$('#FilesTable')).DataTable({
                    //control which datatable options available
                    dom: 'Bfrltip',
                    //add select functionality to datatable
                    select: true,
                    //adjust column widths
                    "columns": [
                    null,
                    null,
                    null,
                    null,
                    null,
                    { "width": "8%" }
                    ],
                    //remove sort icon from actions column
                    "aoColumnDefs": [
                    { "bSortable": false, "aTargets": [5] }
                    ]
                });
            } else {
                $('#FilesGrid').append("<span>No Files Found.</span>");
            }
        },
        error: function (data) {
            $('#FilesGrid').append("<span>Error Retreiving Files. Error : " + JSON.stringify(data) + "</span>");
        }
    });
};
//Generate html table values
function GenerateTableFromJson(objArray) {
    var tableContent =
        '<table id="FilesTable" class="table table-striped table-bordered" cellspacing="0" width="100%">' +
            '<thead><tr>' + '<th>ID</th>' + '<th>Title</th>' + '<th>FileName</th>' + '<th>FileType</th>' +
            '<th>Team</th>' + '<th>Actions</th>' + '</tr></thead>';
    for (var i = 0; i < objArray.length; i++) {
        tableContent += '<tr>';
        tableContent += '<td>' + objArray[i].Id + '</td>';
        tableContent += '<td>' + objArray[i].Title + '</td>';
        tableContent += '<td>' + objArray[i].SPFxFileName + '</td>';
        tableContent += '<td>' + objArray[i].SPFxFileType + '</td>';
        tableContent += '<td>' + objArray[i].SPFxTeam + '</td>';
        tableContent += "<td><a id='" + objArray[i].Id + "' href='#' style='color: orange' class='confirmEditFileLink'>" +
            "<i class='glyphicon glyphicon-pencil' title='Edit File'></i></a>&nbsp&nbsp";
        tableContent += "<a id='" + objArray[i].Id + "' href='#' style='color: red' class='confirmDeleteFileLink'>" +
            "<i class='glyphicon glyphicon-remove' title='Delete File'></i></a>&nbsp&nbsp";
        tableContent += "<a id='" + objArray[i].Id + "' href='#' class='confirmListItemDetailsLink'>" +
            "<i class='glyphicon glyphicon-cog' title='Link to List Item'></i></a></td>";
        tableContent += '</tr>';
    }
    return tableContent;
};
// Edit button click event
$(document).on('click', '.confirmEditFileLink', function (e) {
    e.preventDefault();
    var id = this.id;
    var requestUri = "../_api/web/lists/getByTitle('SPFxFiles')/items(" + id + ")";
    $.ajax({
        url: requestUri,
        method: "GET",
        contentType: "application/json;odata=verbose",
        headers: { "accept": "application/json;odata=verbose" },
        success: function (data) {
            $('#fileTitle').val(data.d.Title);
            $('#fileName').val(data.d.SPFxFileName);
            $('#fileType').val(data.d.SPFxFileType);
            $('#team').val(data.d.SPFxTeam);
            $('#fileId').val(data.d.Id);
            $('#myModalLabel').html('Edit File');
            (<any>$('#myModalNorm')).modal('show');
            $("#etag").val(data.d.__metadata.etag);
        }
    });
});
//Link to files list item
$(document).on('click', '.confirmListItemDetailsLink', function (e) {
    e.preventDefault();
    var id = this.id;
    var requestUri = "../Lists/SPFxFiles/DispForm.aspx?ID=" + id;
    window.location.href = requestUri;
});
// Delete button click event
$(document).on('click', '.confirmDeleteFileLink', function (e) {
    e.preventDefault();
    var id = this.id;
    $('#deleteId').val(id);
    (<any>$('#deleteFiles')).modal({
            show: true
        })
});
//Update Model Label
function updateFormLabel() {
    $('#myModalLabel').html('Add New File');
};
//Populate then display modal dialog for add file button clicked
$(document).on('click', '.addNewFile', function (e) {
    $('#myModalLabel').html('Add New File');
    $('#fileTitle').val('');
    $('#fileName').val('');
    $('#fileType').val('');
    $('#team').val('');
    $('#fileId').val('');
    (<any>$('#myModalNorm')).modal('show');
});
//Edit file function
function UpdateFiles(id) {
    var fileTitle = $("#fileTitle").val();
    var fileName = $("#fileName").val();
    var fileType = $("#fileType").val();
    var team = $("#team").val();
    var eTag = $("#etag").val();
    var requestUri = "../_api/web/lists/getByTitle('SPFxFiles')/items(" + id + ")";
    var requestHeaders = {
        "accept": "application/json;odata=verbose",
        "X-HTTP-Method": "MERGE",
        "X-RequestDigest": $('#__REQUESTDIGEST').val(),
        "If-Match": eTag
    }
    var fileData = {
        __metadata: { "type": "SP.Data.SPFxFilesListItem" },
        Title: fileTitle,
        SPFxFileName: fileName,
        SPFxFileType: fileType,
        SPFxTeam: team
    };
    var requestBody = JSON.stringify(fileData);

    return $.ajax({
        url: requestUri,
        type: "POST",
        contentType: "application/json;odata=verbose",
        headers: requestHeaders,
        data: requestBody
    });
}

//Add File function
var addFile = function (fileTitle, fileName, fileType, team) {
    var requestUri = "../_api/web/lists/getByTitle('SPFxFiles')/items";
    var requestHeaders = {
        "accept": "application/json;odata=verbose",
        "content-type": "application/json;odata=verbose",
        "X-RequestDigest": $('#__REQUESTDIGEST').val()
    }
    var fileData = {
        __metadata: { "type": "SP.Data.SPFxFilesListItem" },
        Title: fileTitle,
        SPFxFileName: fileName,
        SPFxFileType: fileType,
        SPFxTeam: team
    };
    var requestBody = JSON.stringify(fileData);
    return $.ajax({
        url: requestUri,
        type: "POST",
        headers: requestHeaders,
        data: requestBody
    });

};
  }
  protected get dataVersion(): Version {
    return Version.parse('1.0');
  }

  protected getPropertyPaneConfiguration(): IPropertyPaneConfiguration {
    return {
      pages: [
        {
          header: {
            description: strings.PropertyPaneDescription
          },
          groups: [
            {
              groupName: strings.BasicGroupName,
              groupFields: [
                PropertyPaneTextField('description', {
                  label: strings.DescriptionFieldLabel
                })
              ]
            }
          ]
        }
      ]
    };
  }
}

Eventually I will split out the javascript code into a separate module that I reference so it will clean up this file greatly but for now I'm just trying to get the demonstration working and published.

Adding the SharePoint List

For this demonstration to work, a custom list needs to be provisioned with some default data so the jquery datatables grid will render some content.

In Visual Studio Code from the project explorer right click below the last file name displayed and select New Folder.

Name the folder sharepoint. Right click on the sharepoint folder and create another folder called assets. Right click on the assets folder and select new file, name the first file elements.xml and the second file schema.xml.

Open the Elements.xml and paste the following code into the file, this code defines 3 custom field types a content type that groups these field types and a list instance. The list instance that will be the actual instantiation of our list will include some default sample data shown in the <Data> node.

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

    <Field ID="{060E50AC-E9C1-4D3C-B1F9-DE0BCAC300F6}"
            Name="SPFxFileType"
            DisplayName="File Type"
            Type="Text"
            Required="FALSE"
            Group="SPFx Columns" />

    <Field ID="{943E7530-5E2B-4C02-8259-CCD93A9ECB18}"
            Name="SPFxFileName"
            DisplayName="File Name"
            Type="Text"
            Required="FALSE"
            Group="SPFx Columns">
    </Field>
    <Field ID="{943E7530-5E2B-4C02-8259-CCD93A9ECB19}"
            Name="SPFxTeam"
            DisplayName="Team"
            Type="Text"
            Required="FALSE"
            Group="SPFx Columns">
    </Field>

    <ContentType ID="0x010042D0C1C200A14B6887742B6344675C8B" 
            Name="SpfxFiles" 
            Group="SPFx Content Types" 
            Description="Sample content types from web part solution">
        <FieldRefs>
            <FieldRef ID="{060E50AC-E9C1-4D3C-B1F9-DE0BCAC300F6}" /> 
            <FieldRef ID="{943E7530-5E2B-4C02-8259-CCD93A9ECB18}" />
            <FieldRef ID="{943E7530-5E2B-4C02-8259-CCD93A9ECB19}" />
        </FieldRefs>
    </ContentType> 

    <ListInstance 
            CustomSchema="schema.xml"
            FeatureId="00bfea71-de22-43b2-a848-c05709900100"
            Title="SPFxFiles" 
            Description="SPFx Files"
            TemplateType="100"
            Url="Lists/SPFxFiles">
            <Data>
                <Rows>
                    <Row>
                    <Field Name="Title">Autoexec</Field>
                    <Field Name="SPFxFileName">Autoexec</Field>
                    <Field Name="SPFxFileType">bat</Field>
                    <Field Name="SPFxTeam">Microsoft</Field>
                    </Row>
                    <Row>
                    <Field Name="Title">Config</Field>
                    <Field Name="SPFxFileName">Config</Field>
                    <Field Name="SPFxFileType">sys</Field>
                    <Field Name="SPFxTeam">EMC</Field>
                    </Row>
                    <Row>
                    <Field Name="Title">Hosts</Field>
                    <Field Name="SPFxFileName">Hosts</Field>
                    <Field Name="SPFxFileType">exe</Field>
                    <Field Name="SPFxTeam">Dell</Field>
                    </Row>
                    <Row>
                    <Field Name="Title">Bootstrap</Field>
                    <Field Name="SPFxFileName">Bootstrap</Field>
                    <Field Name="SPFxFileType">js</Field>
                    <Field Name="SPFxTeam">EMC</Field>
                    </Row>
                    <Row>
                    <Field Name="Title">Startup</Field>
                    <Field Name="SPFxFileName">Startup</Field>
                    <Field Name="SPFxFileType">css</Field>
                    <Field Name="SPFxTeam">Dell</Field>
                    </Row>
                </Rows>
            </Data>
    </ListInstance>
</Elements>

Open the Schema.xml file and paste the following code into the file. The schema file will define the custom list including the content type defined above and the fields to be included in the default view.

<List xmlns:ows="Microsoft SharePoint" Title="Basic List" EnableContentTypes="TRUE"

FolderCreation="FALSE" Direction="$Resources:Direction;" Url="Lists/Basic List"

BaseType="0" xmlns="http://schemas.microsoft.com/sharepoint/">
  <MetaData>
    <ContentTypes>
      <ContentTypeRef ID="0x010042D0C1C200A14B6887742B6344675C8B" />
    </ContentTypes>
    <Fields></Fields>
    <Views>
      <View BaseViewID="1" Type="HTML" WebPartZoneID="Main"

      DisplayName="$Resources:core,objectiv_schema_mwsidcamlidC24;"

      DefaultView="TRUE" MobileView="TRUE" MobileDefaultView="TRUE"

      SetupPath="pages\viewpage.aspx"

      ImageUrl="/_layouhttps://devofficecdn.azureedge.net/sharepointdocumentation/images/generic.png" Url="AllItems.aspx">
        <XslLink Default="TRUE">main.xsl</XslLink>
        <JSLink>clienttemplates.js</JSLink>
        <RowLimit Paged="TRUE">30</RowLimit>
        <Toolbar Type="Standard" />
        <ViewFields>
          <FieldRef Name="LinkTitle"></FieldRef>
          <FieldRef Name="SPFxFileName"></FieldRef>
          <FieldRef Name="SPFxFileType"></FieldRef>
          <FieldRef Name="SPFxTeam"></FieldRef>
        </ViewFields>
        <Query>
          <OrderBy>
            <FieldRef Name="ID" />
          </OrderBy>
        </Query>
      </View>
    </Views>
    <Forms>
      <Form Type="DisplayForm" Url="DispForm.aspx" SetupPath="pages\form.aspx" WebPartZoneID="Main" />
      <Form Type="EditForm" Url="EditForm.aspx" SetupPath="pages\form.aspx" WebPartZoneID="Main" />
      <Form Type="NewForm" Url="NewForm.aspx" SetupPath="pages\form.aspx" WebPartZoneID="Main" />
    </Forms>
  </MetaData>
</List>

In the config folder open the package-solution.json file and paste the following code in the file. The package-solution file defines the solution and the feature that will be used to provision the custom list defined above. In the paths node the output directory is defined where the packed solution (.sppkg) file will be outputted.

{
  "solution": {
    "name": "spfx-client-side-solution",
    "id": "08244525-0fcd-4651-bef4-41aedba1dc47",
    "version": "1.0.0.0",
     "features": [{
      "title": "spfx-2-client-side-solution",
      "description": "spfx-2-client-side-solution",
      "id": "523fe887-ced5-4036-b564-8dad5c6c6e25",
      "version": "1.0.0.0",
      "assets": {        
        "elementManifests": [
          "elements.xml"
        ],
        "elementFiles":[
          "schema.xml"
        ]
      }
    }]
  },
  "paths": {
    "zippedPackage": "solution/spfx.sppkg"
  }
}

Package the solution

Before packaging the solution select the Save All button, notice in the upper left corner the file icon with a 3 indicates there are 3 files that have been modified but not saved.

From the Integrated Terminal window type Gulp bundle

From the Integrated Terminal window type Gulp package-solution

Note - look for any red text when these commands are executed that indicate errors and ensure that Gulp bundle is executed before Gulp package-solution because Gulp bundle creates the dist folder with the bundle.js and other files that Gulp package-solution require.

From the Integrated Terminal window type Gulp serve. This command will start the local web site that will be accessed by SharePoint Online to render the web part. Note - If Gulp serve is not running before the web part is added to the page or viewed an error will be displayed.

Deploy Web Part to SharePoint Online

Because this solution relies on a SharePoint hosted list, running the web part in the local SharePoint Workbench tool will not work. I may change this later to add mock SharePoint list data when running the solution locally but for now I'll just deploy the solution to SharePoint Online.

Now that the Gulp package-solution command has been executed a sppkg file will be created in the sharepoint | solution directory.

For this demonstration ensure you have an application catalog site created in SharePoint Online and navigate to that site and select Apps for SharePoint

Drag and drop the spfx.sppkg file into the Apps for SharePoint library. Select Deploy to trust the solution and deploy it into SharePoint.

Verify the solution displays that the app package is valid and it is deployed

Launch a separate browser session or tab and access your SharePoint Online Developer site. From the top toolbar select the gear icon and Add an App.

Select From Your Organization to filter the list of apps and select spfx-client-side-solution.

The Site Contents page will be displayed and the spfx-client-side-solution will display and "We're adding your app" message. This will take a few minutes to complete.

Once the "We're adding your app" message disappears the app installation is complete, refresh the page and if the list is deployed successfully a SPFxfiles list will be included in the site contents. Notice that under the list title 5 items is displayed, this verifies that the data specified in the list definition was successfully provisioned.

The web part should be correctly displayed on the page, select Save.

Test the Web Part

Select the Add New File Button, fill out fields and select Submit

Select the pencil (Edit) icon on the newly added item in the grid, alter one of the fields and select Submit.

Select the X (Delete) icon on the newly added item in the grid, a confirmation dialog will appear, select Submit to delete the item from the list. The item should be removed from the list.

A File Successfully Deleted Toast will be displayed in the upper right corner.

This completes the SPFX Solution demonstration.

Please take a look at my follow up post Here for instructions on hosting solution files via a CDN from a SharePoint Online document library. With this in place you will no longer need to run Gulp serve to correctly view the web part.

Responsive SharePoint Online Hosted Add-In using Bootstrap, Bootstrap Dialog, JQuery Datatables and Toastr

2017-02-16T11:37:00.000-07:00

In this blog post I'll demonstrate how to create a SharePoint Online Hosted Add-In that uses the SharePoint REST API to interact with a custom SharePoint list to Create, Read, Update and Delete records from this list in a responsive fashion.

The project contains a custom SharePoint List called Files that will be populated using sample data, this list will provide the data to the JQuery datatables grid.

Prerequisites

Office 365 Tenant
Visual Studio 2015 or Visual Studio Code
SPFastDeploy (optional) - if you haven't used this tool before please take a look at my blog post on this Here

Javascript Libraries

Install the following Javascript libraries via NuGet

Bootstrap v3.3.7 (Don't install v4+ for this demo)
Bootstrap.dialog
~~JQuery (installed by default)~~
Jquery Datatables
~~Jquery Datatables.select (Installed with JQuery Datatables NuGet package)~~
Toastr

Download Visual Studio Solution - Here

Terminology

The words Apps and Add-Ins can be a little confusing, Microsoft has officially renamed SharePoint Apps to SharePoint Add-Ins. In Visual Studio and SharePoint Online the dialogs still use the old term Apps.

Original name	New name
apps for SharePoint	SharePoint Add-ins
app part	add-in part
app web	add-in web

Instructions

This demonstration will be done using Visual Studio 2015 Update 3.

Open Visual Studio 2015 and Select File | New Project

Under the New Project | Installed | Templates |Office/SharePoint | Select App for SharePoint

Enter a SharePoint site where this application will be published

Select SharePoint Hosted and Select Next

Select SharePoint Online for the target version and Select Finish

Installing NuGet packages

Right click on the project name and Select Manage NuGet Packages. Select the Browse link and search for Bootstrap. Select Bootstrap from the list and choose version 3.7 in the dropdown. Select the Install Button.
Repeat this process for the remaining Javascript libraries listed above.

Create the SharePoint Files List to host the data for the datatables grid

Right Click on the project name and select Add | New Item

Under the Office/SharePoint Items | Select List and type 'Files' as the name

Enter 'Files' for the name to display and Select Create a customizable list template and a list instance of it Radio Button. Select Finish

The Files | Schema.xml file should automatically open (if not simply double click on the Files List from the solution explorer. On the Columns tab, create columns for FileName, FileType and Team, each column will have a Type of Single Line of Text. Save and Close the Schema.xml File

Note: At any point you may be prompted to sign in to Office 365, enter your credentials and select Sign In

Populate Sample Data into Files List

Open the Elements.xml file beneath Files | FilesInstance. Delete everything in this file, copy and paste the following code into this file:

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <ListInstance Title="Files" OnQuickLaunch="TRUE" TemplateType="100" Url="Lists/Files" Description="Files List Instance">
    <Data>
      <Rows>
        <Row>
          <Field Name="Title">Autoexec</Field>
          <Field Name="FileName">Autoexec</Field>
          <Field Name="FileType">bat</Field>
          <Field Name="Team">Dell</Field>
        </Row>
        <Row>
          <Field Name="Title">Config</Field>
          <Field Name="FileName">Config</Field>
          <Field Name="FileType">sys</Field>
          <Field Name="Team">EMC</Field>
        </Row>
        <Row>
          <Field Name="Title">Hosts</Field>
          <Field Name="FileName">Hosts</Field>
          <Field Name="FileType">exe</Field>
          <Field Name="Team">Dell</Field>
        </Row>
        <Row>
          <Field Name="Title">Bootstrap</Field>
          <Field Name="FileName">Bootstrap</Field>
          <Field Name="FileType">js</Field>
          <Field Name="Team">EMC</Field>
        </Row>
        <Row>
          <Field Name="Title">Startup</Field>
          <Field Name="FileName">Startup</Field>
          <Field Name="FileType">css</Field>
          <Field Name="Team">Dell</Field>
        </Row>
      </Rows>
    </Data>
  </ListInstance>
</Elements>

Note: After saving the list and deploying to SharePoint I noticed that the filetype

column was displaying 'undefined'. I looked at the schema.xml file for the Files list

and noticed the filetype had been changed to filetype1 in the <fields><field></field></fields>

node. A simple search in this file for filetype helped identify 2 places where I needed to

change the name back to filetype. Not sure why this occurred.

Add Javascript to App.js file

The following javascript contains functions to populate the datatables grid, provide

All of the Create, Read, Update and Delete (CRUD) methods, creating the Bootstrap

model dialog for creating and editing files and delete file confirmation dialog.

'use strict';
var RestUrl = "../_api/lists/getbytitle('Files')/items";
$(document).ready(function () {
    PopulateGrid();
    $('#fileFormSubmit').click(function (e) {
        //Check for edit or new and call update or add function
        if ($('#myModalLabel').html() == 'Add New File') {
            addFile($('#fileTitle').val(), $('#fileName').val(), $('#fileType').val(), $('#team').val());
        } else {
            UpdateFiles($('#fileId').val());
        }
    });
});
function PopulateGrid() {
    //Clear datatables
    $('#FilesGrid').empty();
    //Get File list items
    $.ajax({
        url: RestUrl,
        method: "GET",
        headers: {
            "accept": "application/json;odata=verbose"
        },
        success: function (data) {
            if (data.d.results.length > 0) {
                //construct HTML Table from the JSON Data
                $('#FilesGrid').append(GenerateTableFromJson(data.d.results));
                //Bind the HTML data with Jquery DataTable
                var oTable = $('#FilesTable').dataTable({
                    //control which datatable options available
                    dom: 'Bfrltip',
                    //add select functionality to datatable
                    select: true,
                    //adjust column widths
                    "columns": [
                    null,
                    null,
                    null,
                    null,
                    null,
                    { "width": "8%" }
                    ],
                    //remove sort icon from actions column
                    "aoColumnDefs": [
                    { "bSortable": false, "aTargets": [5] }
                    ]
                });
            } else {
                $('#FilesGrid').append("<span>No Files Found.</span>");
            }
        },
        error: function (data) {
            $('#FilesGrid').append("<span>Error Retreiving Files. Error : " + JSON.stringify(data) + "</span>");
        }
    });
};
//Generate html table values
function GenerateTableFromJson(objArray) {
    var tableContent =
        '<table id="FilesTable" class="table table-striped table-bordered" cellspacing="0" width="100%">' +
            '<thead><tr>' + '<th>ID</th>' + '<th>Title</th>' + '<th>FileName</th>' + '<th>FileType</th>' +
            '<th>Team</th>' + '<th>Actions</th>' + '</tr></thead>';
    for (var i = 0; i < objArray.length; i++) {
        tableContent += '<tr>';
        tableContent += '<td>' + objArray[i].Id + '</td>';
        tableContent += '<td>' + objArray[i].Title + '</td>';
        tableContent += '<td>' + objArray[i].FileName + '</td>';
        tableContent += '<td>' + objArray[i].FileType + '</td>';
        tableContent += '<td>' + objArray[i].Team + '</td>';
        tableContent += "<td><a id='" + objArray[i].Id + "' href='#' style='color: orange' class='confirmEditFileLink'>" +
            "<i class='glyphicon glyphicon-pencil' title='Edit File'></i></a>&nbsp&nbsp";
        tableContent += "<a id='" + objArray[i].Id + "' href='#' style='color: red' class='confirmDeleteFileLink'>" +
            "<i class='glyphicon glyphicon-remove' title='Delete File'></i></a>&nbsp&nbsp";
        tableContent += "<a id='" + objArray[i].Id + "' href='#' class='confirmListItemDetailsLink'>" +
            "<i class='glyphicon glyphicon-cog' title='Link to List Item'></i></a></td>";
        tableContent += '</tr>';
    }
    return tableContent;
};
// Edit button click event
$(document).on('click', '.confirmEditFileLink', function (e) {
    e.preventDefault();
    var id = this.id;
    var requestUri = "../_api/web/lists/getByTitle('Files')/items(" + id + ")";
    $.ajax({
        url: requestUri,
        method: "GET",
        contentType: "application/json;odata=verbose",
        headers: { "accept": "application/json;odata=verbose" },
        success: function (data) {
            $('#fileTitle').val(data.d.Title);
            $('#fileName').val(data.d.FileName);
            $('#fileType').val(data.d.FileType);
            $('#team').val(data.d.Team);
            $('#fileId').val(data.d.Id);
            $('#myModalLabel').html('Edit File');
            $('#myModalNorm').modal('show');
            $("#etag").val(data.d.__metadata.etag);
        }
    });
});
//Link to files list item
$(document).on('click', '.confirmListItemDetailsLink', function (e) {
    e.preventDefault();
    var id = this.id;
    var requestUri = "../Lists/Files/DispForm.aspx?ID=" + id;
    window.location.href = requestUri;
});
// Delete button click event
$(document).on('click', '.confirmDeleteFileLink', function (e) {
    e.preventDefault();
    var id = this.id;
    BootstrapDialog.show({
        size: BootstrapDialog.SIZE_SMALL,
        type: BootstrapDialog.TYPE_DANGER,
        title: "Delete Files Confirmation",
        message: "Are you sure you wish to Delete this File?",
        buttons: [
            {
                label: "Confirm",
                cssClass: 'btn-primary',
                action: function (dialog) {
                    dialog.close();
                    var restUrl = "../_api/web/lists/GetByTitle('Files')/items(" + id + ")";
                    jQuery.ajax({
                        url: restUrl,
                        type: "DELETE",
                        headers: {
                            Accept: "application/json;odata=verbose",
                            "X-RequestDigest": $("#__REQUESTDIGEST").val(),
                            "IF-MATCH": "*"
                        }
                    });
                    toastr.success("File Successfully Deleted.", "Success");
                    PopulateGrid();
                }
            },
            {
                label: "Cancel",
                action: function (dialog) {
                    dialog.close();
                }
            }
        ]
    });
});
//Update Model Label
function updateFormLabel() {
    $('#myModalLabel').html('Add New File');
};
//Populate then display model dialog for add file button clicked
function addNewFile() {
    $('#myModalLabel').html('Add New File');
    $('#fileTitle').val('');
    $('#fileName').val('');
    $('#fileType').val('');
    $('#team').val('');
    $('#fileId').val('');
    $('#myModalNorm').modal('show');
};
//Edit file function
function UpdateFiles(id) {
    var fileTitle = $("#fileTitle").val();
    var fileName = $("#fileName").val();
    var fileType = $("#fileType").val();
    var team = $("#team").val();
    var eTag = $("#etag").val();
    var requestUri = "../_api/web/lists/getByTitle('Files')/items(" + id + ")";
    var requestHeaders = {
        "accept": "application/json;odata=verbose",
        "X-HTTP-Method": "MERGE",
        "X-RequestDigest": $('#__REQUESTDIGEST').val(),
        "If-Match": eTag
    }
    var fileData = {
        __metadata: { "type": "SP.Data.FilesListItem" },
        Title: fileTitle,
        FileName: fileName,
        FileType: fileType,
        Team: team
    };
    var requestBody = JSON.stringify(fileData);

    return $.ajax({
        url: requestUri,
        type: "POST",
        contentType: "application/json;odata=verbose",
        headers: requestHeaders,
        data: requestBody
    });
}
//Add File function
var addFile = function (fileTitle, fileName, fileType, team) {
    var requestUri = "../_api/web/lists/getByTitle('Files')/items";
    var requestHeaders = {
        "accept": "application/json;odata=verbose",
        "content-type": "application/json;odata=verbose",
        "X-RequestDigest": $('#__REQUESTDIGEST').val()
    }
    var fileData = {
        __metadata: { "type": "SP.Data.FilesListItem" },
        Title: fileTitle,
        FileName: fileName,
        FileType: fileType,
        Team: team
    };
    var requestBody = JSON.stringify(fileData);
    return $.ajax({
        url: requestUri,
        type: "POST",
        headers: requestHeaders,
        data: requestBody
    });

};

Modify the Default.aspx page with the following code

In the <asp:content> section all of the css and script references are added, ensure these match the

file locations from the downloaded NuGet packages, if they don't they will be underlined indicating

there is an issue.

<%-- The following 4 lines are ASP.NET directives needed when using SharePoint components --%>

<%@ Page Inherits="Microsoft.SharePoint.WebPartPages.WebPartPage, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" MasterPageFile="~masterurl/default.master" Language="C#" %>

<%@ Register TagPrefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%-- The markup and script in the following Content element will be placed in the <head> of the page --%>
<asp:Content ContentPlaceHolderID="PlaceHolderAdditionalPageHead" runat="server">
        <!-- CSS styles added to the following file -->
    <link type="text/css" href="../Content/App.css" rel="Stylesheet"/>
    <link type="text/css" href="../Content/toastr.css" rel="stylesheet" />
    <link type="text/css" href="../Content/bootstrap.css" rel="stylesheet" />
    <link type="text/css" href="../Content/bootstrap-dialog.css" rel="stylesheet" />
    <link type="text/css" href="../Content/DataTables/css/select.bootstrap.min.css" rel="stylesheet" />
    <link type="text/css" rel="stylesheet" href="https://cdn.datatables.net/1.10.8/css/jquery.dataTables.css">
     <!-- javascript references added to the following file -->
    <script type="text/javascript" src="../Scripts/jquery-1.9.1.min.js"></script>
    <script type="text/javascript" src="../Scripts/bootstrap.js"></script>
    <script type="text/javascript" src="../Scripts/bootstrap-dialog.js"></script>
    <script type="text/javascript" src="../Scripts/toastr.min.js"></script>
    <script type="text/javascript" src="../Scripts/App.js"></script>
    <script type="text/javascript" src="https://cdn.datatables.net/1.10.8/js/jquery.dataTables.min.js"></script>
    <script type="text/javascript" src="../Scripts/DataTables/dataTables.select.min.js"></script>
</asp:Content>

<%-- The markup and script in the following Content element will be placed in the <body> of the page --%>
<asp:Content ContentPlaceHolderID="PlaceHolderMain" runat="server">
    <div class="container">
        <h1><span class="label label-primary">Grid Data Consumed via  SharePoint Rest API</span></h1>
        <div id="toolbar">
            <button type="button" value="Files" class="btn btn-info" onclick="Javascript: location.href = '../Lists/Files'"><span class='glyphicon glyphicon-upload'></span> File List</button>
            <button type="button" class="btn btn-success" onclick='addNewFile();'><span class='glyphicon glyphicon-plus'></span> Add New File</button>
        </div>
   <p></p>
 <div id="FilesPanel">
 <table style="width: 100%;">
 <tr>
     <td>
        <div id="FilesGrid" style="width: 100%"></div>
     </td>
 </tr>
 </table>
 </div>
 <!-- Bootstrap Modal Dialog-->
<div class="modal fade" id="myModalNorm" tabindex="-1" role="dialog" aria-labelledby="myModalLabel" aria-hidden="true">
    <div class="modal-dialog">
        <div class="modal-content">
            <!-- Modal Header -->
            <div class="modal-header">
                <button type="button" class="close" data-dismiss="modal">
                       <span aria-hidden="true">&times;</span>
                       <span class="sr-only">Close</span>
                </button>
                <h4 class="modal-title" id="myModalLabel">
                    Add New File
                </h4>
            </div>
            <!-- Modal Body -->
            <div class="modal-body" id="modalBody">
                <form role="form" id="fileForm">
                  <div class="form-group">
                    <label>File Title</label>
                      <input class="form-control" id="fileTitle"/>
                  </div>
                  <div class="form-group">
                    <label>File Name</label>
                      <input class="form-control" id="fileName"/>
                  </div>
                  <div class="form-group">
                    <label>File Type</label>
                      <input class="form-control" id="fileType"/>
                  </div>
                     <div class="form-group">
                    <label>Team</label>
                      <input class="form-control" id="team"/>
                  </div>
                      <!-- hidden controls -->
                  <div style="display: none">
                      <input id="etag" />
                      <input id="fileId" />
                  </div>
                  </form>
                  <div class="modal-footer">
                      <button type="button" class="btn btn-danger" data-dismiss="modal" onclick='updateFormLabel();'>
                        Cancel
                      </button>
                      <button type="submit" class="btn btn-primary" id="fileFormSubmit">
                        Submit
                      </button>
                  </div>
            </div>
        </div>
    </div>
</div>
</div>
</asp:Content>

Verify Solution - a list of items in the Visual Studio Solution






Deploy SharePoint Add-In to SharePoint Online

Right click on the project name and Select Deploy

In the Output Tab ensure that the SharePoint Add-in deploys successfully. During deployment there will be a message: Installation is in progress (00:00:00) with a timer to show the amount of time it takes for deployment.

Note: If you have installed and configured SPFastDeploy you will no longer have to wait for this lengthy deployment process after the initial deployment. If you make a simple change to a single file you can just right click on the file and select SPFastDeploy.

View the SharePoint Add-In in SharePoint Online

Navigate to the SharePoint site configured in your SharePoint Add-In properties

Select the ResponsiveSharePointHostedAddin link from the left navigation

Note: In the action column if you hover over the icons you will see a description for each icon, from left to right there is edit, delete and link to list item icons. Bootstrap is used here to render these icons using a regular <a href> tag with a class='glyphicon glyphicon-pencil' for the edit icon for example.

Testing SharePoint Add-In Functionality

Select the Add New File Button, this will present the Bootstrap Model Dialog prompting the user to create a new file. Select Cancel.

Select the Pencil icon from one of the items in the grid. Notice the row selected changes colors (JQuery.Datatables.Select library) indicating this row is selected and then Bootstrap dialog opens allowing the user to edit the selected file. Select Cancel.

Select the Delete icon from one of the items in the grid. A Bootstap dialog will be displayed asking for confirmation of the file deletion. Select Cancel.

Select the order by column headers for some of the columns in the grid, notice how there are no post-backs for any of this functionality and its very fast. Type something in the search box that appears in the grid, notice how it quickly filters items to the text you type again with no post-backs.

Select Delete on an item in the grid, confirm the deletion. A Toast will fire indicating the file was successfully deleted.

This completes this demonstration.

Download Visual Studio Solution - Here

Microsoft SQL Server 2016 Installation

2017-02-15T11:14:00.000-07:00

This post will provide the necessary prequisites, steps and configuration settings for a Stand-Alone SQL Server 2016 Environment. The Stand-Alone tier of service consists of a single SQL Server with a baseline configuration.

Prerequisites

Windows Server installation
Storage provisioning allocated with disk partitions outlined
Instance and Shared Features required for this implementation of SQL Server, i.e. Reporting, Analysis, Integration
Domain Service accounts (recommended)
Instance Type identified, Default.
SA account password
Specific SQL Server administrator accounts.
Default Collation identified for instance type and purpose.
.Net 3.5 framework feature enabled
Setup file for SQL Server 2016
Licensing keys for SQL Server 2016
Adequate user account permissions to complete the installation

Note: The SQL installation is based on this drive configuration, please configure these drives on the Windows Server before continuing

SQL Server Hard Drive Configuration

Drive Letter	Functions	Size (GB)	Notes
C	System	80GB	80
D	Binaries	200GB
G	Data	2TB
L	Logs	400GB	(data * 20%)
T	TempDB Data & Logs	100GB
R	Backups	2.5TB

SQL Server Account Configuration

Component	SQL Server 2014/2014	Notes
Database Engine	sqlsvc01
SQL Server Agent	sqlsvc02
SSAS	Local Service
SSIS	Local Service
SSRS	Local Service
Distributed Replay Controller	Local Service
FD Launcher (Full-text Search)	Local Service
SQL Server Browser	Local Service
SQL Server VSS Writer	Local Service

Installation

Logon to server, locate the installation media and ensure the media is presented to the operating system.

Double-Click the setup.exe file to launch the SQL Server 2016 Installation Center

Select Installation from the left menu items and the click on the New Server stand-alone installation or add features to an existing installation link.

Enter the product key for the SQL edition that is being installed.

Accept the product license terms.

Select Use Microsoft Update checkbox.

Select the Include SQL Server product updates checkbox and select the Next button.

Ensure no failures are identified on the Install Rules check and select the Next button.
Note: the correct firewall rules may need to be created for the SQL Server, refer to the following Microsoft table for the list of ports and protocols used by SQL Server.

Service / Purpose	Protocol	Port
Analysis Services connections via HTTP (default)	TCP	80, 2383 Default Instance
Analysis Services connections via HTTPS (default)	TCP	443
Microsoft Distributed Transaction Coordinator (MS DTC)	TCP	135
Reporting services Web Services	TCP	80
Reporting Services configured for use through HTTPS	TCP	1433
Service Broker	TCP	4022
SQL Server 2014 Analysis Services	TCP	2382 (SQL Server Browser Services for SSAS port) 2383 (Clusters will listen only on this port)
SQL Server Browser Service (Database Engine)	UDP	1434
SQL Server Browser Service	TCP	2382 (Only Needed for named instance)
SQL Server default instance running over an HTTPS endpoint.	TCP	443
SQL Server Instance (Database Engine) running over an HTTP endpoint.	TCP	80,443 (SSL)
SQL Server Integration Services	TCP	135
SQL over TCP (default instance)	TCP	1433

The Feature Selection dialog will be displayed. Select All SQL Instance and Shared Features except PolyBase Query Service for External Data, R Services (In-Database) and R Server (Standalone). Adjust the Instance Root Directory, Shared Feature Directory and Shared Feature Directory (x86) to the configured data drive D:\ then select the Next button.

Note: If you have a requirement for R Services, select the appropriate items.

The Feature Rules dialog will be displayed. Click the Show details button and ensure all operations complete successfully then select the Next button.

The Instance Configuration dialog will be displayed. Select the instance type, Default is the most common. If Default, leave the instance name as MSSQLSERVER and verify the SQL Server, Analysis Services and Reporting Services directories are set to the D: volume then click the Next button.

The Server Configuration dialog will be displayed. Enter the appropriate service accounts and passwords in the Service Accounts section. Set the SQL Server Agent startup type to Automatic. Select the Grant Perform Volume Maintenance Task privilege to SQL Server Database Engine Service. This option allows for much faster data file allocations (CREATE AND ALTER FILE) but does not work for log file allocations. This is enabled for each instance via the "Perform volume maintenance tasks" local security policy. In a cluster you have to grant the right on all nodes. If there are multiple instances on a server or cluster, you should grant this right to each instance’s security group.

Select the Collation tab. Verify collation setting and set appropriately for installation by clicking the Customize… button. When satisfied with setting click the Next button to continue.

NOTE: Most installations use the default setting of Latin1_General_CI_AS. If a collation setting has not been provided, leave the default setting.

The Database Engine Configuration dialog will be displayed. Under the Server Configuration tab set the Authentication Mode to Mixed, enter the (sa) account password and add Specific SQL Server administrators then click the Data Directories tab.

Note: See the Service Accounts section in the table above for account specifications.

Set the Data, Log and Backup directories as depicted in the following figure then select the TempDB tab. These directories will align directly with the configuration specified in the drive table above .

NOTE: If this is a named instance installation, <MSSQLSERVER> will be replaced with the provided instance name. MSSQL12 equates to SQL Server 2014, MSSQL13 equates to SQL Server 2016.

Set the TempDB directories as depicted in the following figure.

Note: To set the TempDB data directory, select the remove button to clear the default directory, select the add button and select new folder to create the following directory structure.

The structure should be T:\MSSQL13.MSSQLSERVER\MSSQL\TEMP as depicted in the following figure. Select Next.

The Analysis Services Configuration dialog will be displayed. Accept the default Server Mode and specify which users have administrative permissions for analysis services.

Select the Data Directories tab and Set the Data, Log, TempDB and Backup directories as depicted in the following figure.

The Reporting Services Configuration dialog will be displayed. Accept the default settings and select Next.

The Distributed Replay Controller dialog will be displayed. Use the Distributed Replay Controller Configuration page to specify the users you want to grant administrative permissions to for the Distributed Replay controller service. Users that have administrative permissions will have unlimited access to the Distributed Replay controller service. Select Next.

The Distributed Replay Client dialog will be displayed. Use the Distributed Replay Client Configuration page to specify the users you want to grant administrative permissions to for the Distributed Replay client service. Users that have administrative permissions will have unlimited access to the Distributed Replay client service. Accept the default settings including leaving the optional controller name blank. If there is a later requirement for using the distributed replay client and server, the controller name can be updated in the client configuration file. Select Next.

The Feature Configuration Rules dialog will be displayed. Ensure that every rule shows a status of passed. Select Next.

The Ready to Install dialog will be displayed. Select Next.

After the installation has completed the Complete dialog will be displayed. Ensure there are no errors or issues with the features installed. If there are any issues the log file link can be selected to view detailed information about the installation.

Select the Close button to complete the installation.

INSTALL SQL SERVER MANAGEMENT TOOLS

The next step will require downloading the latest version of the SQL Server Management Studio. The link from the Installation Center will launch a browser to download the executable. Before this link is selected disable the IE Enhanced Security Configuration. From the Windows Start Menu select Server Manager.

The Server Manager – Local Server dialog will be displayed. Select the On link next to IE Enhanced Security Configuration. Under Administrators select Off and select Ok.

With the SQL Server Installation Center still open select Install SQL Server Management Tools. Close the Server Manager Applet.

Note: Unlike previous versions of SQL Server, the SQL Server Management Studio (SSMS) is not part of the SQL Server Installation and must be downloaded and installed manually.

Select the Download SQL Server Management Studio link.

After the download is complete, launch the executable to install SSMS. Select Install. Restart after the installation.

SQL SERVER CONFIGURATION MANAGER SETTINGS.

Launch the SQL Server Configuration Manager

Expand the SQL Server Network Configuration Node

Select the Protocols for the newly installed Instance <MSSQLSERVER>

Ensure TCP/IP is enabled

Highlight the SQL Server Services Node

Ensure the SQL Server and SQL Server Agent services are Running and the Start Mode is set to Automatic. Close the SQL Server Configuration Manager.

Open SQL Server Management Studio

Connect to the SQL instance just installed.

Highlight the Root Node, right click and select Properties

Select the Memory page and set the Maximum memory appropriate to server memory. The default memory setting of 2147483647 allows the SQL Server to consume all of the memory on the machine, the operating system should be allocated 10% of total memory at a minimum.

NOTE: For 32GB Machines set to 25600MB, for 64GB machines set to 54272MB.

Select the Advanced page and set the Cost Threshold for Parallelism to 20. By setting this to a larger setting you ensure the SQL Server only tries to parallelize larger queries. Parallelism only makes sense when you deal with larger queries – like in a reporting or Data Warehousing scenario.

Set the Max Degree of Parallelism to half the number of cpu cores (8) on the current virtual machine would be set to (4). The Max Degree of Parallelism defines how many worker threads each parallel operator in the execution plan can use.

This completes the SQL Server 2016 installation.

SharePoint SPFastDeploy

2017-02-13T11:09:00.000-07:00

SharePoint SPFastDeploy is a must have tool for developing solutions in SharePoint Online. This tool can be downloaded from Here and installed into Visual Studio. Without this tool it can take several minutes to deploy a SharePoint Add-In to SharePoint Online.

Note: You will still have to initially deploy the solution to SharePoint Online using the traditional methods however once this tool is installed and the SharePoint Add-In has been deployed, you can simply right click a file after making changes and select Fast deploy to SP App. Using this method takes only seconds to save the new file.

Once this tool is installed it will add a new shortcut to the tools menu

There are a couple of way to configure this tool for simpler use

Enable SPFastDeploy on Save - Select Tools | Options | SPFastDeploy, under Misc Select True for Deploy when saving. This will use SPFastDeploy each time a file is changed and saved.

Add SPFastDeploy to Right Click Context Menu - Select Tools | Customize | Commands Tab | Select the Context Menu radio button and choose Project and Solution Context Menus | Item from the dropdown control.

Next select the Add Command Button and choose Tools under Categories and select SPFastDeploy from the list of commands.

Ensure the right click functionality is now available by selecting a file in your SharePoint Add-In project and right clicking to view the context menu

ASPNET Core MVC display database connection string to page

2017-01-27T13:41:00.001-07:00

ASPNET Core MVC display database connection string on page

I was recently asked how to display the database connection string for an ASPNET Core MVC application. This is not as straight forward as it was with previous version of ASPNET when you could just use the ConfigurationManager to read settings from the applications web.config file.

In ASPNET Core MVC there is no web.config, usually custom settings will be created in a appsettings.json file. To get access to the appsettings file, first there are some configuration settings that will need to be changed.

First this is how the current connection string is defined in the appsettings.json

Connection String

"database": {
"connection": "Data Source=.;Initial Catalog=OdeToFood;Integrated  Security=True;Connect Timeout=15;Encrypt=False;TrustServerCertificate=True;ApplicationIntent=ReadWrite;MultiSubnetFailover=False"

}

Create a class to store the connection string property (AppSettings.cs)

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;

namespace CoreTest
{
    public class AppSettings
    {
        public string connection { get; set; }
    }
}

Update the project Startup.cs file

Ensure the constructor is reading the appsettings.json file

public Startup(IHostingEnvironment env)
    {
        var builder = new ConfigurationBuilder()
            .SetBasePath(env.ContentRootPath)
            .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
            .AddJsonFile($"appsettings.{env.EnvironmentName}.json", optional: true)
            .AddEnvironmentVariables();
        Configuration = builder.Build();
    }

Add these lines to ConfigureServices

 services.AddOptions();
 services.Configure<AppSettings>(Configuration.GetSection("database"));

Update the controller (HomeController.cs)

Create the app settings variable and inject the AppSettings into the constructor

 public class HomeController : Controller
 {
    private AppSettings _AppSettings;

    public HomeController(IOptions<AppSettings> settings)
    {
        _AppSettings = settings.Value;
 }

Add the controller method that will send the connection string to the view

 public async Task ContentAction()
    {
        var constr = _AppSettings.connection;
        var jsonString = "{\"connectionString\""+ constr + "}";
        byte[] data = Encoding.UTF8.GetBytes(jsonString);
        Response.ContentType = "application/json";
        await Response.Body.WriteAsync(data, 0, data.Length);
    }

Call the controller method from the View (Index.cshtml)

 <div>
    <a asp-controller="Home" asp-action="ContentAction" class="btn btn-  success confirmCreate">
        Generate Response
        <i class="fa fa-angle-left"></i>
    </a>
</div>

View Output will display the connection string

{"connectionString"Data Source=.;Initial Catalog=OdeToFood;Integrated     Security=True;Connect Timeout=15;Encrypt=False;TrustServerCertificate=True;ApplicationIntent=ReadWrite;MultiSubnetFailover=False}

What SQL Server is my SharePoint machine pointed to?

2016-11-29T11:47:00.001-07:00

I recently powered on a SharePoint 2016 box that I haven't used in a while, when I powered it on and tried to browse to the default SharePoint site at http://machinename I received the classic .net error:

Server Error in '/' Application.

Runtime Error

I also attempted to open the SharePoint Central Administration page and received the same error.

I opened the web.config for the default SharePoint site at c:\inetpub\wwwroot\wss\VirtualDirectories\80 and searched for the word 'error' located the xml node...

<customErrors mode="On" /> and changed this setting to 'Off'

Refreshing the http://machinename page now displays the hidden error message...

'This operation can be performed only on a computer that is joined to a server farm by users who have permissions in SQL Server to read from the configuration database. To connect this server to a server farm, use the SharePoint Products Configuration Wizard, located on the Start menu in Microsoft Sharepoint 2016 Products.

Unfortunately, if I attempt to run the SharePoint Products Configuration Wizard it also displays an error message 'Failed to detect if this server is joined to a server farm,,,'

Turns out the SQL server was just turned off but in my environment I have many SharePoint Servers, SQL Servers, Web Servers, etc. I wasn't sure which SQL server this SharePoint machine was pointed to and I only wanted to power on this one SQL Server.

There are probably multiple ways to determine which SQL Server the SharePoint box is pointed to but the way I chose to find out was to just reference a registry key that defined the connection string to the configuration database. The key name is dsn and the Data value is populated with the connection string.

My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.O\Secure\ConfigDb

Connect SQL Server 2014 Management Studio to Azure SQL Database

2016-10-06T13:32:00.000-06:00

To connect SQL Server Management Studio (SSMS) to an Azure SQL database log in to the Azure Management Portal

Create a new database or connect to an existing database

For this example I'll create a new SQL database, from Azure home page select SQL Databases and select +Add

Select the database

After the database has been created (may take a few minutes and a refresh to appear), from the SQL databases menu select the database that was just created (MyDb).

Add a firewall rule

In order to connect to the Azure SQL database a firewall rule must be created with the IP address or range of IP addresses that will be allowed to access the database.

After the firewall rule has been created the database can now be connected to using SSMS.

Copy the server name

From the Azure Management Portal Select SQL Databases and select the MyDb database

Copy the server name listed below Essentials for your database

Determine Server Admin username for the Azure SQL Server

From the SQL Databases menu select the database (MyDb)

Select the server name link below Essentials - Note: you must have a username and password that has access to the database to connect using SSMS.

Launch the SSMS Application

Paste the server name that was copied above and enter the username and password

OneDrive for Business

2016-09-28T12:53:00.001-06:00

What is OneDrive for Business?

Let’s start with what OneDrive for Business (ODFB) is not, ODFB is not Microsoft’s service for hosting files in the cloud (OneDrive – previously SkyDrive which is intended for personal storage) that allows users to sync files and later access them from a web browser or mobile device. OneDrive is a completely separate product and has nothing to do with ODFB.

Microsoft OneDrive for Business variations

On Premises SharePoint – OneDrive for Business on premises

OneDrive for Business is a brand, not a product and it consists of three specific things

SharePoint My Site – a site collection that is created by default for every user
My Documents Library in SharePoint My Site - A document library that every user has and OWNS (key point), in addition it allows users to sync any other document library the user has access to
Synchronization Tool for synchronizing between desktop and Document Library. The OneDrive for Business Windows Sync client installs either with Office 2013 Standard or with Office 2013 Professional Plus. Or you can download the stand-alone OneDrive for Business Windows Sync client

ODFB replaces previous Microsoft products Groove (SharePoint 2007) and SharePoint Workspace (Sharepoint 2010)

Prerequisites - To support OneDrive for Business document libraries in SharePoint Server 2013, you must have:

Configured the User Profile Service application
Configured My Sites
For Office 2013 to display the user's My Site as a default save or open location, you must configure SharePoint Server 2013 to use Exchange Autodiscover
To support system generated email notifications from SharePoint Server 2013 when a user shares a document with another user, make sure outgoing email is configured for your SharePoint Server 2013 farm

Library quotas

By default, the quota for each user's My Site in SharePoint Server 2013 is 100 MB. If you plan to use the OneDrive for Business document library for users to store their files, you should increase this default quota limit. If your organization uses SharePoint Online, a user's My Site quota is set to 25 GB and is configurable to 50 GB or 100 GB per user.

Library customization

Although the OneDrive for Business document library supports many of the features of a standard document library, a user shouldn't customize the OneDrive for Business document library because it might affect synchronization.
For example, if a user modifies the document library to require that metadata be filled in, the files are synchronized with SharePoint Server 2013, however, the document remains checked out. To check-in the document, the user has to fill in the required metadata either through SharePoint Server 2013 using the browser, or by opening the file with the Office 2013 client.
In addition, keep permission levels at the default settings of Can edit and Can view.

Office 365 – SharePoint and OneDrive for Business in the Cloud

ODFB provides 1 Terabyte of storage for every user
External sharing works out of the box – share with users outside of the SharePoint environment, they’ll get an email and get access to that single document
Advantage – users can edit Microsoft Office documents directly from the browser without having Microsoft Office installed on the client
Multiple plans available with different storage, encryption and data loss features

Stand alone OneDrive – give users the My Site, the My Site My Documents and the ability to sync

Multiple plans available with different storage, encryption and data loss features

Limitations

ODFB My Documents library in users My Site has an item limit of 20,000 items that can be synced and downloaded locally for offline usage
Additional document libraries within SharePoint can be synced as well but have a limitation of 5,000 items
Sync is by document library and not by files or folders
2GB file size limit
Character limitations in files and folder names
Not available on a Mac – this may have changed
Files don’t have a URL directly to them
Number of items that can be sync’d

Features

The old concept of My Site in SharePoint is going away and being replaced with OneDrive for Business
When a user clicks the OneDrive link in the SharePoint 2013 navigation, the user is redirected to what used to be called My Site, now ODFB
When a user installs Microsoft Office 2013 it installs a client tool called OneDrive for Business which handles the synchronizations of files between SharePoint and the client desktop
There is a Powershell script available to create the ODFB sites for all users programmatically because they are not created by default. By default, when a user first logs in to SharePoint the My Site is created
Mapping a drive to OneDrive for Business from the client, make sure the desktop experience feature is installed on the SharePoint server to allow this

Hybrid OneDrive for Business - Starting with SharePoint 2013 SP1 you can connect on-premises SharePoint 2013 servers to the cloud and turn on OneDrive for Business

Figure 1

In SharePoint Server, you can redirect users to OneDrive for Business stand alone or Office 365 (see figure 2) when they choose OneDrive in the navigation bar (SharePoint Server 2010 and SharePoint Server 2013) or in the app launcher (SharePoint Server 2016). This is known as hybrid OneDrive for Business.
If you want to redirect your users to OneDrive for Business in Office 365, you need an Office 365 tenant where your users are licensed and at least Service Pack 1 installed on your farm.
To avoid user confusion, keep the following in mind when you turn on hybrid OneDrive for Business:

When you turn on this feature, your users will be directed to OneDrive for Business in Office 365 when they click OneDrive in SharePoint Server. Be sure to plan to migrate your users' content from their old SharePoint Server OneDrive for Business to the new one in Office 365.
Because there's no direct link between OneDrive for Business in SharePoint Server and OneDrive for Business in Office 365, users' Shared with me lists in Office 365 won't display documents that have been shared with them from on-premises SharePoint Server.For example, if a user modifies the document library to require that metadata be filled in, the files are synchronized with SharePoint Server 2013, however, the document remains checked out. To check-in the document, the user has to fill in the required metadata either through SharePoint Server 2013 using the browser, or by opening the file with the Office 2013 client.
Keep permission levels at the default settings of Can edit and Can view

Figure 2

Windows Explorer view on client desktop

Figure 3

Coming Soon

New sync capabilities include:

Ability to sync SharePoint Online document libraries and OneDrive folders shared with you (preview available today)
An “activity center” has been added to the OneDrive sync client to allow you to view synchronization and file activity at a glance (preview available today)

New browser capabilities include:

Rich thumbnails and previews for over 20 new file types (rolling out before the end of 2016)
Ability to access and edit all your files in OneDrive and SharePoint Online from the OneDrive browser client (rolling out before the end of 2016)
Capability to download multiple files as a .zip file (rolling out before the end of 2016)

New mobile capabilities include:

Notifications to your iOS or Android device when someone shares a OneDrive file with you (available today)
Access to SharePoint Online files in the OneDrive app on Android (available today)
Multi-page scan enhancements in the OneDrive app on Android (available today)
Ability to see over time how many people have discovered and viewed your files in OneDrive for iOS (available today)

New IT capabilities include:

Enhancements to integration with Office 2016 (available in First Release)
Simple, flexible OneDrive user management in Office 365 (available in First Release)
Dedicated OneDrive administration console in Office 365 (rolling out before the end of 2016)

Entity Framework - Introduction (Part 2 of 3)

2013-04-18T13:01:00.002-06:00

Entity Framework - Introduction (Part 2 of 3)

(Part 1)(Part 3)

Part 2 Model First

In part one we looked at creating a database fist project and generated a model from our pre-existing database, in part 2 we are going to build a model first and then create the database from the model. To begin this part of the tutorial we'll create a new class library project.

Create a new Visual Studio Class Library Project

Once the new project has been created, right click on the project name and select Add | New Item

Under C# Select Data | ADO.NET Entity Data Model

Select Empty Model and Finish

Building the Model

Next we'll add some entity objects on the design surface and start building our model. Entity objects can be created either by dragging and dropping items from the toolbox to the design surface or right clicking on the design surface and selecting Add | New Item.

Add From Toolbox

Add from Designer Surface

First I'll add a new Entity and call it Movie, notice that by default a new ID property is created with an int32 type and set to an identity.

Next, I'll add two more scalar properties to the Movie entity, title and date.

Note: The default for a new scalar property is string and non-nullable. Note: the max length attribute of our scalar property will be used when the database is created for the max length of the column.

Change the type of the date property to DateTime

The next Entity will be called Genre, create one scalar property in the Genre called Category with a default type of string. The last Entity I'll create will be called Actor, I'll create one new scalar property called Name with a default type of string.

The Entity diagram should now look something like this

Create the Entity Relationships (Associations)

Right click on Movie and Select Add | Association

Ensure that Movie and Actor are selected in the dropdown boxes, Change the Multiplicity to Many to Many, this is because there can be many actors in a movie and actors can be in many movies. The new association will create 2 new navigation properties, Actors and Movies.

The Design Diagram has been updated showing the new association, many movies to many actors

Next create another association for Movie to Genre, this association will be many to one because movie can only have 1 genre but genre can be associated with many movies.

Generate the Database from the Model

Next we're going to create our SQL database from our model design.

Note: The database that we are going to create needs to already exist on the SQL Server, just a shell of a database that we can point to. The command to Generate the database from the model actually just generates the schema in the existing database.

Create a new database on the SQL server called MovieLibrary

Before we generate the database from the model, let's take a look at the metadata that describes the database and metadata that describes the mapping between the model and the database.

To view the metadata, right click on the ModelFirst.edmx file in the Visual Studio Solution Explorer and select Open With | XML

There are two highlighted sections in the XML file, the first is the storage schema that describes the database and the second is the mapping layer, these sections are currently empty because we have not generated the database from the model yet.

Next go back to the Designer view of the model and right click on the design surface and select Generate Database From Model.

Create a new connection to the SQL server, select the new MovieLibrary database.

Select Next

Select Finish and the SQL file will be created that can be run against the SQL Server.

Right click anywhere in the file and select Execute. You'll be prompted from the SQL Server to enter credentials. After credentials have been entered you should get a message in the T-SQL window saying the Command Completed Successfully.

Take a look inside the database and see if the tables created in the model are now in the database.

This completes part 2 of the Entity Framework introduction, in part 3 I will discuss using the newly created models to leverage the Entity Framework.

(Part 1)(Part 3)

Microsoft Entity Framework Intro (Part 1 of 3)

2013-04-17T14:12:00.000-06:00

Entity Framework - Introduction (Part 1 of 3)

(Part 2, Part 3)

The following tutorial will explain some basic concepts using the Microsoft Entity Framework, I'll attempt to explain this with a few examples to help demonstrate some of the capabilities.

Recomendations for this tutorial, other versions of these products may work however these are the versions used in this tutorial.

1. Microsoft Visual Studio 2012
2. SQL Server 2008R2
3. AdventureWorks database (2008R2 version) downloaded and installed from http://msftdbprodsamples.codeplex.com/downloads/get/478216

Introduction

The Microsoft Entity Framework (EF) is an object-relational mapper that enables .NET developers to work with relational data using domain-specific objects. It eliminates the need for most of the data-access code that developers usually need to write. This creates, in effect, a "virtual object database" that can be used from within a project to access database objects using C# code instead of having to write a whole lot of SQL queries. In this post we'll add a sample database to our SQL server, create a new Entity Framework model from our existing sample database and try and get an understanding of the model.

Part 1 - Database First

Adding the AdventureWorks Database - If you do not have the demo database attached to your SQL Server you can download the database from the link above. Once downloaded attach the database to SQL Server.

Step 1 - Copy the database files into the correct file locations for your SQL Server. The .mdf file should be copied into the data folder where all the other SQL Databases exist and the .ldf file should be copied into the the Log folder where all the other Log files exist.

Step 2 -From the SQL Server Management Console right click on databases and select Attach.

Step 3 - Select Add and browse to the correct .mdf file located where you copied it on the SQL Server

Step 4 - Select the ellipsis next to the log file and ensure the log file path is correct

Step 5 - Ensure the AdventureWorks database is correctly attached to your SQL Server

Creating the Visual Studio Project - Next we'll create a Visual Studio Project to demonstrate some of the Entity Framework capabilities.

Note: If you are using a version of Visual Studio other than 2012, you may not have the Entit

In this example I'll create a new class library project, I'll be able to add or reference this project in any new solution that I create in order to leverage the Entity Framework.

Create a new class library and name it EFModel

Right click on the project name and select add, add a new ADO.NET Entity Data Model

Create an Entity Data Model From a database

Create a new connection to your database

rename the connection settings AWEntities

Select Tables and Views to be populated from the database into our new Entity Model and select Finish

We can now see a new Entity Framework model has been created called EFModel, this will be instantiated in our project when we want to leverage the Entity Framework.

The designer view of the Entity Model will be displayed, we can view all of the relationships or associations in the designer. Notice the relationship between Customer and SalesOrderHeader is a one to many relationship (depicted by the 1 on customer and the asterisks on SalesOrderHeader)

In our project an App.Config file has been created, within this file an Entity connection string can be found.

If we right click on the white space in the designer view of our Entity Model and select Mapping Details, then select one of the entities in the diagram, the database column to class property mapping can be viewed or modified.

The mapping details shows the relationships between the database columns and the model properties, these are also customize-able.

Conclusion

This wraps up part one of the introduction to the Entity Framework, we covered getting a sample database installed on our SQL Server 2008R2 Database Server, Creating a new Class Library project, adding an Entity Framework model created from our existing AdventureWorks database and briefly looking at our completed Model. In part two we'll cover creating a SQL database from an existing model.

(Part 2, Part 3)

SharePoint, Office 2013 RTM - MSDN

2012-10-25T16:14:00.001-06:00

Microsoft has just added SharePoint 2013, Office 2013, Visio 2013, Project 2013 and Exchange 2013 to MSDN for subscribers to download.

Microsoft MSDN .img file

2012-08-23T21:53:00.000-06:00

Microsoft seems to have switched file formats from .iso to .img for some of the software available on MSDN.

What is an .img file? At first I thought I had to use Nero to burn the image to a disk and then install, but I noticed that in Windows 8 you can natively mount .iso and .img formats.

Since I don't plan on installing these .img files on Windows 8 or Server 2012 yet, you can simply rename the file from .img to .iso and then use the file as you would normally use an .iso

Sharepoint 2013 Preview

2012-08-22T08:50:00.000-06:00

Sharepoint 2013 is just around the corner, full of new features to take the platform to the next level

Here are some of the new features

Visual Experience

Metro Interface
To brand a SharePoint site, designers just create a site design as they typically would, by implementing HTML, CSS, and JavaScript. Designers can create these files by using their design tool of choice, whether that is Adobe Dreamweaver, Microsoft Expression Web, or some other HTML editor. You don't have to use SharePoint Designer or Visual Studio 2013 to brand a SharePoint site

App Store

Everything in Sharepoint 2013 is an App, lists, workflow, site pages, remote web apps, etc.
Make your apps available to everyone to try and buy through the public Store or only available to your employees through the corporate catalog

Social Networking

The introduction of Community Sites offers a forum experience to categorize discussions around subject areas, and connect users who have knowledge or seek knowledge about subject areas
My Sites for micro-blogging, allows likes, hash tags and news feed functionality following content, people and sites.

Integration

Organize all your projects and tasks to get visibility into upcoming deliverables across SharePoint, Outlook and Microsoft Project
Sync your content in SharePoint to your desktop with SkyDrive Pro

Development

Based on common web standards like HTML, CSS, and JavaScript. Furthermore, implementation relies on established protocols like the Open Data protocol (OData), and OAuth
Support for the newly developed web-based tool "Napa" Office 365 Development Tools for developing apps
Visual Studio 2012 now includes a new app project template in the Apps folder named Apps for SharePoint 2013
In addition to the use of Representational State Transfer (REST) endpoints for web services, there is a broad new API for both server and client development. Remote event receivers and now supported in addition to client-side rendering

Cloud

Improved and enhanced to support the new cloud-based architecture and app-driven development framework
Full support for development against the Windows Azure Workflow platform

Content

Many new features for videos and using videos on pages. A new video content type is added, and the video upload process is improved for content authors
Content authors can insert an iframe element into an HTML field on a page. This lets content authors embed dynamic content from other sites, such as videos or map directions
Support for image renditions. Image renditions let you display different sized versions of an image on different pages
Cross-site publishing lets you store and maintain content in one or more authoring site collections, and display this content in one or more publishing site collections
Designate any library or list as a catalog. After the Cross-Site Collection Publishing feature is enabled for a site collection, you can designate any library or list within that site collection as a catalog so that content can be reused on publishing site collections

Localization

Built in integrated translation service that lets content authors select content for export for human translation or specify content for machine translation.

These are only a subset of all of the new and improved features and functionality in the Sharepoint 2013 Preview, for more information check out Microsoft's official Sharepoint 2013 sites at

http://technet.microsoft.com/en-us/library/cc303422(v=office.15)
http://msdn.microsoft.com/en-us/library/jj162979(v=office.15)

Download the preview at:
http://technet.microsoft.com/en-US/evalcenter/hh973397

Microsoft System Center Service Manager 2012 Gotchas

2012-08-15T18:35:00.000-06:00

I have attempted to install SCSM 2012 unsuccessfully multiple times and learned a few things that I'll share that will hopefully save someone hours of time hunting down solutions for these issues.

The first issue I ran into was during the SCSM Data warehouse management server installation, during this install you will be asked for multiple database names, rather than selecting the default names, I chose to append '2012' to all the database names. The install will fail with 2012 in the database names, I tried this in three separate environments and it failed in all three.

The next issue was the SQL instance name, if you create a new instance besides the default MSSQL and include 'MSSQL' in the name of the new instance, the installation will fail. Tried this in a couple of different environments and always a failed installation.

The last issue is during an upgrade from SCSM 2010 to SCSM 2012, about three quarters of the way through the installation it will attempt to make changes to the SSRS server, if there is a web folder on the site with the name 'Data Sources' the installation will fail. This failure will be a catastrophic failure and require a disaster recovery scenario to rebuild/reinstall. The horrible thing about this issue is that if you have been creating reporting solutions using the SQL Business Intelligence Development Studio, when you publish your projects to the SSRS server I believe it will automatically create the Data Sources Folder. For the upgrade, rename this folder, run the upgrade and the change the name back after it succeeds.

SQL 2008 Native Client Installation Error

2012-08-15T18:17:00.005-06:00

I recently worked on a Microsoft System Center Service Manager 2012 upgrade project and on both of the management servers during the prerequisite installation the SQL Server 2008 Native Client installation would fail. After searching around through what seemed like hundreds of sites, I found a solution that works consistently.

Error Message - An error occurred during the installation of assembly 'Microsoft.VC80.CRT...

Export and delete the following registry keys...

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_policy.8.0.microsoft.vc80 & vc90 entries…

[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.8.0.microsoft.vc80 & vc90 entries

[HKEY_LOCAL_MACHINE\COMPONENTS\WINNER\Components\x86_policy.8.0.microsoft.vc80 & vc90 entries.

Note: On my 2008 R2 Server the third set of keys was not present

Then run services.msc and set the "Windows Module Installer" to automatic and Reboot.

The installation will now complete successfully.

Cannot resolve the collation conflict between “SQL_Latin1_General_CP1_CI_AS” and “Latin1_General_100_CI_AS” in the equal to operation

2012-06-18T10:22:00.002-06:00

Working in a Microsoft System Center Service Manager 2010 database I had added a couple of new tables for doing Business Hour Calculations ( see SQL Calculate Business Hours post). I added the tables calendar and holiday for the business hour calculations and when I attempted to execute my SQL function for doing the business hour calculation between date ranges I received the error.

After searching and searching I found a simple solution. First a useful query to determine what the collation is for a columns in a table. In my case I performed the query on the calendar table and day_name and day_number were both set incorrectly.

SELECT
col.name, col.collation_name
FROM
sys.columns col
WHERE
object_id = OBJECT_ID('YourTableName')

This query will return the collation for each column specified, for me it instantly helped my identify the collation conflict and I was able to execute the following query to correct the issue.

ALTER TABLE YourTableName
ALTER COLUMN OffendingColumn
VARCHAR(100) COLLATE Latin1_General_CI_AS NOT NULL

After I ran the alter statement, I tried the business hour function again and sure enough it worked perfectly.

SQL Server 2008 - No Administrator Access

2012-05-31T06:48:00.001-06:00

In the past I've experienced issues with SQL Server where the domain account or group that I designated for administrator access loses the ability to perform any administrative actions. Strange behavior because it will let the accounts log in to the server but anytime a domain user attempts an action that requires elevated permissions an error is thrown.

One quick solution is to logon to the machine as the local administrator rather than any domain account and use this account to re-add any domain user or group permissions. By default this account is given administrative access on the SQL server.

SQL - Calculate Business Hours Minus Holidays

2012-05-23T08:02:00.000-06:00

Calculating Business Hours

I was recently tasked with generating SSRS reports against a Microsoft System Center Service Manager data warehouse. The reports require that only business hours be used to extract things like how long a service management ticket was worked etc. In my case the service desk is open M-F from 7:30 to 4:30 and no weekends or Federal Holidays. I expected to find a number of good examples with a few searches but nothing came up that fit my needs exactly.

Here's a quick rundown of how I was able to satisfy the reporting requirements.

First - create a new table to store the work week hours including Saturday and Sunday, this table will be used whenever a query is generated to determine how many hours fall within the "open" hours of the service desk.

I started the process with some examples I gathered here - http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=74645 I then extended the examples to include Holidays and fix the queries when the start date and end date were on the same day.

Open SQL Management Studio and attach to the database you wish to add this new table to, paste the following SQL code into the query and execute.

CREATE TABLE [dbo].[ttr_calendar] (

[day_number] [varchar] (50) NOT NULL ,

[day_name] [varchar] (50) NULL ,

[begin_time] [datetime] NULL ,

[end_time] [datetime] NULL ,

[duration] [real] NULL

) ON [PRIMARY]

Next I'll populate the table with the hours of the service desk. Execute the following statement

insert into ttr_calendar

select 1, 'Monday', '7:30:00 AM', '4:30:00 PM', 32400 union all

select 2, 'Tuesday', '7:30:00 AM', '4:30:00 PM', 32400 union all

select 3, 'Wednesday', '7:30:00 AM', '4:30:00 PM', 32400 union all

select 4, 'Thursday', '7:30:00 AM', '4:30:00 PM', 32400 union all

select 5, 'Friday', '7:30:00 AM', '4:30:00 PM', 32400 union all

select 6, 'Saturday', '7:30:00 AM', '4:30:00 PM', 0 union all

select 7, 'Sunday', '7:30:00 AM', '4:30:00 PM', 0

For brevity I'll just link the F_Table_Date function that I used in conjunction with the other tables, this code will need to be copied and executed on our SQL instance, this will generate a function that is used in the query.

Using F_Table_Date - http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61519&SearchTerms=F_TABLE_DATE

Function F_TABLE_DATE is a multistatement table-valued function that returns a table containing a variety of attributes of all dates from @FIRST_DATE through @LAST_DATE. In short, it’s a calendar table function.

Next I need to create a table to store the Holiday information - Note: This table will have to be manually populated with your holiday information, simply add a title i.e. Christmas, New Years, etc. and the date in the following format 12/25/2012.

USE [DWDataMart] /* <--Your Database Name */

/****** Object: Table [dbo].[ttr_Holiday] Script Date: 05/22/2012 14:37:53 ******/

SET ANSI_NULLS ON

SET QUOTED_IDENTIFIER ON

SET ANSI_PADDING ON

CREATE TABLE [dbo].[ttr_Holiday](

[ID] [int] IDENTITY(1,1) NOT NULL,

[Name] [varchar](50) NOT NULL,

[Date] [date] NOT NULL,

CONSTRAINT [PK_ttr_Holiday] PRIMARY KEY CLUSTERED

(

[ID] ASC

)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

) ON [PRIMARY]

SET ANSI_PADDING OFF

Now that all the pieces are in place I can generate the actual query that will return my business hours minus Holidays.

declare @start_date datetime,

@end_date datetime,

@temp int

select @start_date = '24 May 2012 07:30:00 AM',

@end_date = '29 May 2012 04:30:00 PM'

Select @temp = COUNT(ttr_holiday.date)*9 from ttr_holiday where ttr_holiday.date Between @start_date and @end_date

select @temp, total_hours = sum(case

when dateadd(day, datediff(day, 0, @start_date), 0) = dateadd(day, datediff(day, 0, @end_date), 0) then

CASE

WHEN CONVERT(VARCHAR(8),@start_date,108) < '07:30:00 AM' and CONVERT(VARCHAR(8),@end_date,108) > '16:30:00'

THEN

datediff(second, [DATE] + begin_time, [DATE] + end_time)

WHEN CONVERT(VARCHAR(8),@start_date,108) < '07:30:00 AM' and CONVERT(VARCHAR(8),@end_date,108) < '16:30:00'

THEN

datediff(second, [DATE] + begin_time, @end_date)

WHEN CONVERT(VARCHAR(8),@start_date,108) > '07:30:00 AM' and CONVERT(VARCHAR(8),@end_date,108) < '16:30:00'

THEN

datediff(second, @start_date, @end_date)

WHEN CONVERT(VARCHAR(8),@start_date,108) > '07:30:00 AM' and CONVERT(VARCHAR(8),@end_date,108) > '16:30:00'

THEN

datediff(second, @start_date, [DATE] + end_time)

END

when [DATE] = dateadd(day, datediff(day, 0, @start_date), 0) then

case

when @start_date > [DATE] + begin_time then datediff(second, @start_date, [DATE] + end_time)

else duration

end

when [DATE] = dateadd(day, datediff(day, 0, @end_date), 0) then

case

when @end_date < [DATE] + end_time then datediff(second, [DATE] + begin_time, @end_date)

else duration

end

else duration

end

)

/ 60.0 / 60.0 - @temp

from F_TABLE_DATE(@start_date, @end_date) d inner join ttr_calendar c

on d.WEEKDAY_NAME_LONG = c.day_name

This query will also take into account the start date and end date being on the same day, in several examples that I looked at this part would not return the correct results.

I hope this post helps with calculating business hours.

Programmatically Change Sharepoint Web Application IP Address

2012-05-17T11:19:00.000-06:00

Recently I was asked about changing a Sharepoint Web Application IP Addresses programatically, is this possible and how will it affect the Sharepoint sites?

I did some testing and it turns out that it is indeed possible to change the IIS Website IP Address without impacting the Sharepoint Web Application(s). For the most part Sharepoint does not care about the IP Address that are assigned to it's Web Application(s), what it cares about is how the IIS sites are mapped to it's Site Collections. The mapping is done via host header in IIS and Alternate Access Mappings in Sharepoint.

Hopefully there are no Sharepoint sites that are accessed using IP Addresses, if so when the IP Address changes, things will break.

Using Host Headers and Alternate Access Mappings allow access via friendly names, these names are only bound by DNS so as

To create a friendly name like 'Portal' first I'll create a host header in IIS to my Sharepoint site, host headers allow me to have several IIS sites and only require one IP address.

In IIS select the Sharepoint site and click Bindings from the Actions menu, enter a friendly name, in my case 'Portal'

Next Ill create a new A record on my DNS server so that the name Portal resolves to my Sharepoint Web Applications IP Address.

Next I'll create a Sharepoint Alternate Access Mapping so that Sharepoint knows what to do when it receives a request for this friendly name 'Portal'

Open Sharepoint Central Administration, select Application Management and under Web Applications select configure alternate access mappings.

Select the alternate access mapping collection for your site and select edit public URLs

Next add the url for your friendly name in one of the zone text boxes

After this configuration is complete Sharepoint can be accessed by typing http://portal. Next I want to programmatically change the IP address of my Sharepoint Web Application.

I found a Powershell script to perform this exact task.

$oldIp = "172.16.3.214"
$newIp = "172.16.3.215"

# Get all objects at IIS://Localhost/W3SVC
$iisObjects = new-object `
System.DirectoryServices.DirectoryEntry("IIS://Localhost/W3SVC")

foreach($site in $iisObjects.psbase.Children)
{
# Is object a website?
if($site.psbase.SchemaClassName -eq "IIsWebServer")
{
$siteID = $site.psbase.Name

# Grab bindings and cast to array
$bindings = [array]$site.psbase.Properties["ServerBindings"].Value

$hasChanged = $false
$c = 0

foreach($binding in $bindings)
{
# Only change if IP address is one we're interested in
if($binding.IndexOf($oldIp) -gt -1)
{
$newBinding = $binding.Replace($oldIp, $newIp)
Write-Output "$siteID: $binding -> $newBinding"

$bindings[$c] = $newBinding
$hasChanged = $true
}
$c++
}

if($hasChanged)
{
# Only update if something changed
$site.psbase.Properties["ServerBindings"].Value = $bindings

# Comment out this line to simulate updates.
$site.psbase.CommitChanges()

Write-Output "Committed change for $siteID"
Write-Output "========================="
}
}
}

Note: Remember DNS will have to be changed first to accommodate the IP Address change.

Provided there are multiple IP Addresses available on the Sharepoint server, this script will look for an old IP Address and update the IIS website to the new IP Address. Again Sharepoint does not care about the IP Address but it only cares about the request coming to it via IIS and matching the name with a Site Collection.

Hopefully this is helpful, it can be useful in fail over scenarios where re-iping at the fail over site is required.

Passed VCP 510 (VMWare Certified Professional)

2012-02-24T13:27:00.000-07:00

I recently passed the VCP 510 exam renewing my VCP again before the deadline of February 28th 2012. If I wouldnt have taken the exam before this date I would have had to enroll in the week long training class prior to taking the exam.

The exam was very much like what I have been used to as far as the previous VMWare VCP exams have been, it did seem like there were more select multiple answer type questions than usual.

Here is a great study site that currently has 927 test questions posted, I can say that these questions are right inline with what you can expect to see on the test. If you can get comfortable with these test questions you will surely pass the test with no issues.

Check out the test questions here

SharePoint 2010 101 Code Samples

2012-02-23T17:14:00.000-07:00

Microsoft has released 101 code samples for Sharepoint 2010. The samples include HTML 5, AJAX, JQuery, WCF, REST and a lot more.

Check them out Here

Some of the projects include...

Each code sample is part of the SharePoint 2010 101 code samples project. These samples are provided so that you can incorporate them directly in your code. Each code sample consists of a standalone project created in Microsoft Visual Studio 2010

SoftArtisans OfficeWriter - Sharepoint 2010 - Word 2010

2012-02-10T12:57:00.000-07:00

I recently had the opportunity to check out SoftArtisans OfficeWriter product. The OfficeWriter product exposes an API that allows information from custom ASP.NET applications to be consumed and used to dynamically and programmatically build Microsoft Word documents and Microsoft Excel spreadsheets.

The OfficeWriter API is a .NET library that allows you to read, manipulate and generate Microsoft Word and Microsoft Excel documents from your own applications. The OfficeWriter product can integrate with Sharepoint 2010 allowing you to export Sharepoint list data into Microsoft Word and Excel documents.

SoftArtisans provides easy to understand sample code, videos and pre-built Sharepoint solutions that make getting started with the product very trivial.

For this tutorial I'll demonstrate deploying, configuring and testing Word Export Plus in a Sharepoint 2010 environment. Word Export Plus is a SharePoint solution that demonstrates the usage of the OfficeWriter API in SharePoint 2010. This solution adds a new context menu (custom action) button to list items, allowing you to export the list data to a pre-formatted Word template that can be designed yourself in Word, or automatically generated by Word Export Plus.

Requirements for this tutorial

SoftArtisans OfficeWriter - Installed and properly licensed, download the trial from Here
SoftArtisans Word Export Plus - Download the Sharepoint solution installer from Here
Sharepoint 2010 - A site in place that will be used to test the Sharepoint integration features
Microsoft Word 2010 - Installed on the Sharepoint 2010 server

Installation

Launch the WordExportPlus.msi executable, this will install the Sharepoint solution into the Sharepoint Farm.

After the Sharepoint solution has been installed it can be deployed

Open Sharepoint Central Administration
Navigate to System Settings | Farm Management | Manage Farm Solutions
Select Word Export Plus.wsp
Select Deploy Solution
Specify a deployment time
Select OK

After the solution has been deployed it can be enabled through the site features on the site where the tool is going to be used.

After Word Export Plus has been activated I'll configure it for use.

First I'll create a contacts list that will be the data source for my exports, select Site Actions | View All Site Content | Create and select Contacts

I'll name the list People and select OK.

After the list is created I'll create a couple of test contacts in the list.

Next I'll configure Word Export Plus by selecting Site Actions | Site Settings | OfficeWriter Solution: Word Export Plus

First I'll choose the list that I just created (People) in the Sharepoint List dialog, in the Word Template dialog select Create a new template file. In the Template File Location select the Shared Documents library of the current site. Enter a name for the Template File (Word Template). Enter a name for the Action (Word)

This completes the configuration,

select Create New Action

To test the new custom action browse to the People list created previously, from one of the contacts select the dropdown next to the last name column and select the action name created previously (Word)

A dialog will open asking if I would like to open or save the WordWriter.Doc file, select Save and after the file is downloaded select Open

This is how the auto-generated template will render the Sharepoint list data, I could have created my own Word template and selected that during the configuration steps. This provides a flexible solution to allow users to get the list data out quickly and formatted nicely into Microsoft Word.

Everything Sharepoint

Passed the Security+ SY0-501 Exam

SharePoint 2019 Public Preview

Links

Download

SPFX Host a SharePoint solution's files in a SharePoint Online Document Library CDN

Introduction

'SPFX SharePoint Online Responsive Web Part using the SharePoint Framework, Bootstrap, JQuery, JQuery Datatables and Toastr'

Prerequisites

Create a CDN hosted on your SharePoint Online Tenant

Configure SharePoint Solution for CDN

Create files for deployment

Copy Files to SharePoint Online

SPFX SharePoint Online Responsive Web Part using the SharePoint Framework, Bootstrap, JQuery, JQuery Datatables and Toastr

Introduction

Prerequisites

Steps

Node Packages/Types (Install these individually)

Include Node Packages in solution

Modify config.json

Adding the SharePoint List

Package the solution

Deploy Web Part to SharePoint Online

Test the Web Part

Responsive SharePoint Online Hosted Add-In using Bootstrap, Bootstrap Dialog, JQuery Datatables and Toastr

Prerequisites

Javascript Libraries

Terminology

Instructions

Installing NuGet packages

Create the SharePoint Files List to host the data for the datatables grid

Populate Sample Data into Files List

Add Javascript to App.js file

Modify the Default.aspx page with the following code

Deploy SharePoint Add-In to SharePoint Online

Testing SharePoint Add-In Functionality

Microsoft SQL Server 2016 Installation

Prerequisites

SharePoint SPFastDeploy

ASPNET Core MVC display database connection string to page

ASPNET Core MVC display database connection string on page

What SQL Server is my SharePoint machine pointed to?

Connect SQL Server 2014 Management Studio to Azure SQL Database

To connect SQL Server Management Studio (SSMS) to an Azure SQL database log in to the Azure Management Portal

Create a new database or connect to an existing database

Select the database

Add a firewall rule

Copy the server name

Determine Server Admin username for the Azure SQL Server

Launch the SSMS Application

OneDrive for Business

What is OneDrive for Business?

Microsoft OneDrive for Business variations

On Premises SharePoint – OneDrive for Business on premises

Prerequisites - To support OneDrive for Business document libraries in SharePoint Server 2013, you must have:

Library quotas

Library customization

Office 365 – SharePoint and OneDrive for Business in the Cloud

Stand alone OneDrive – give users the My Site, the My Site My Documents and the ability to sync

Limitations

Features

Hybrid OneDrive for Business - Starting with SharePoint 2013 SP1 you can connect on-premises SharePoint 2013 servers to the cloud and turn on OneDrive for Business

Windows Explorer view on client desktop

Coming Soon

New sync capabilities include:

New browser capabilities include:

New mobile capabilities include:

New IT capabilities include:

Entity Framework - Introduction (Part 2 of 3)

Entity Framework - Introduction (Part 2 of 3)

Microsoft Entity Framework Intro (Part 1 of 3)

Entity Framework - Introduction (Part 1 of 3)

SharePoint, Office 2013 RTM - MSDN

Microsoft MSDN .img file

Sharepoint 2013 Preview

Microsoft System Center Service Manager 2012 Gotchas

SQL 2008 Native Client Installation Error

Cannot resolve the collation conflict between “SQL_Latin1_General_CP1_CI_AS” and “Latin1_General_100_CI_AS” in the equal to operation

SQL Server 2008 - No Administrator Access

SQL - Calculate Business Hours Minus Holidays