Climax

Act 1

1. Install the latest version of Node.JS.
2. In a PowerShell window install the Yeoman Generator.
   • npm install -g yo
3. Still in a PowerShell window install Gulp (for example) for previewing and testing your solution.
   • npm install -g gulp
4. Still in the PowerShell install the Microsoft SharePoint Framework toolkit
   • npm install -g @microsoft/generator-sharepoint
5. Finally install the Visual Studio Code (or whatever dev environment you want to use).

Act 2

Act 3

npm config set strict-ssl false
npm config set registry "http://registry.npmjs.org/"
npm --proxy http://username:password@cacheaddress.com.br:80 install packagename

Act 4

1. The system environment variables, where you specify it like this:
   • HTTP_PROXY    http://10.2.0.8:8888
   • HTTPS_PROXY  http://10.2.0.9:8888
   • 
2. The WinHTTP configuration
   • NETSH WINHTTP SET PROXY 'http://10.2.0.8:8888'

1. One that was acting as a proxy.
   • This has Fiddler installed, and
   • Configured to "Allow remote computers to connect"
2. Another one that was creating the package.
   • This one is using the above mentioned proxy configurations (both the system variable and the WinHTTP), and
   • is creating the new SPFx package with the good old yo @microsoft/sharepoint command.

Falling Action

Method 1: Capture the whole installation network traffic and play it back with Fiddler.

• This is probably the easier way to do it, although it does not make it possible to automate the installation, should you need to create installation packages.
  1. Configure NPM to use HTTP traffic.

npm config set strict-ssl false
npm config set registry "http://registry.npmjs.org/"

1. 2. Start Fiddler and start capturing.
   3. Install your package using Fiddler as a proxy.

npm --proxy http://username:password@cacheaddress.com.br:80 install packagename

1. 4. Save all packets from Fiddler.
   5. Transfer the .SAZ file to your locked down box.
   6. Start Fiddler on the locked down box.
   7. Import the .SAZ file into the Autoresponse rules.
   8. Configure the locked down box as you did with the previous one (step 1 in this section).
   9. Run the installation using Fiddler as a proxy, just as you did with the previous one (step 3 in this section.)

Method 2: Use NPMBox to package most of the stuff and use Fiddler to replay only the single file that is missing from the package.

• Personally, I favor this option as this is cleaner and could be packaged in the future, when the guys fix that tiny little problem of the missing file.
  1. Install NPMBox.

npm install -g npmbox

1. 2. Create an npmbox packate for Yeoman, Gulp and the SharePoint Framework Toolkit.

npmbox --proxy='http://127.0.0.1:8888' -t c:\Temp\NPMBox NPMBox
npmbox --proxy='http://127.0.0.1:8888' -t c:\Temp\Yo yo
npmbox --proxy='http://127.0.0.1:8888' -t c:\Temp\Gulp gulp
npmbox --proxy='http://127.0.0.1:8888' -t c:\Temp\SPFx @microsoft/generator-sharepoint

1. 3. Configure NPM to use HTTP traffic.

npm config set strict-ssl false
npm config set registry "http://registry.npmjs.org/"

1. 4. Re-install the SharePoint Framework toolkit using the NPMBox package.

npmunbox --proxy='http://127.0.0.1:8888' -g SPFx

1. 5. Take note of the URL of the extra package that is loaded by the installer. It's going to be a version of the postcss-modules-extract-imports-1.1.0.tgz module. (Note: this step is required only until the NPMBox guys fix the issue with the missing packet.)
   6. Save the module as a file.
   7. Copy the NPMBox packages and the extra file to the locked down box.
   8. Unpack the NPMBox file. For this you will need to rename the NPMBox.npmbox file to NPMBox.tar. On Windows machines, you'll need to use something like 7ZIP.
   9. Change to the folder where you unpacked the NPMBox package, then install the NPMBox offline on the locked down box

npm install --global --cache .\.npmbox.cache --optional --cache-min 99999999999 --shrinkwrap false npmbox

1. 10. Install Fiddler and configure an AutoResponder rule for the missing packet with the URL in step 5. (Note: this step is required only until the NPMBox guys fix the issue with the missing packet.)
   11. Use NPMUnbox to install the offline packages.

npmunbox --proxy='http://127.0.0.1:8888' -g Yo
npmunbox --proxy='http://127.0.0.1:8888' -g Gulp
npmunbox --proxy='http://127.0.0.1:8888' -g SPFx

Dénouement

Rising Action

Act 1

• removes the SP2010 Workflow History link from the list item
• removes the Workflow Instance reference from the workflow service's register.

Act 2

Climax

Act 3

Act 4

https://www.contoso.com/sites/testsite/_api/Web/Lists/GetByTitle('MyList')/WorkflowAssociations?$filter=Name eq 'My2010WFName'&$Select=BaseID,ListID

• The BaseID will be equal to the WorkflowTemplateID.
• While the ListID is the GUID of the original list where the item is.

https://www.contoso.com/sites/testsite/_api/Web/Lists/GetByTitle('Workflow%20History')/Items?$filter=((substringof('<ListGUID>',List)) and (substringof('<BaseID>',WorkflowTemplate)) and (Item eq <ItemID>))&$orderby=ID desc

• Filter for the WorkflowTemplateID, where it equals the BaseID,
• Order the results by Modified descending.
• Should you have run the workflow more than once, it will give you all the entries for that Workflow definition.
• (Note that the { and } characters are forbidden in the Workflow definition, so we have to use the SubstringOf method to filter for the List and WorkflowTemplate columns.)

Act 5

https://www.contoso.com/sites/testsite/_api/web/lists/GetByTitle('Workflow%20History')/Items?$filter=WorkflowInstance eq '<WFInstanceGUIDFromURL>'$orderby=ID desc

Falling Action

Dénouement

1. You get the number of items you want to iterate through.
2. Set a pointer.
3. Do your magic.
4. Increment the pointer.

Act 1

1. Fiddler cannot authenticate against POST, so you should have a cookie available.
2. You need to post an X-RequestDigest header.
3. You might need to have a payload in the Message Body.

• Generate random content for SharePoint – About how to create big files for upload testing.
• Generate random content for SharePoint 2 – About how to generate Word files for Search and integration testing.
• Generate random content for SharePoint 3 – About how to generate Excel files for Search and integration testing.
• Generate random content for SharePoint 4 – About how to generate PowerPoint files for Search and integration testing. (This article.)

Exposition

Rising Action

Act 1

$msoTrue = [Microsoft.Office.Core.MsoTriState]::msoTrue
$msoFalse = [Microsoft.Office.Core.MsoTriState]::msoFalse

$PPTDocument = $PPTApplication.Presentations.Add($msoFalse)

Act 2

Climax

Act 3

$PPTSlideLayout = [microsoft.office.interop.powerpoint.ppSlideLayout]::ppLayoutText
$Slide = $PPTDocumet.Slides.Add($SlideCounter,$PPTSlideLayout)

$Slide.Shapes.Title.TextFrame.TextRange.Text = $TitleText
$Slide.Shapes.Item(2).TextFrame.TextRange.Text = $SlideText

Act 4

$PictureWidth = [math]::Round(($Picture.Width / $Picture.HorizontalResolution * 72),4)
$PictureHeight = [math]::Round(($Picture.Height / $Picture.VerticalResolution * 72),4)

If ($PictureWidth -gt $PicturesMaxWidth)
{
    $Multiplier = $PicturesMaxWidth / $PictureWidth
    $PictureHeight = $PictureHeight * $Multiplier
}
If ($PictureHeight -gt $PicturesmaxHeight)
{
    $Multiplier = $PicturesmaxHeight = $PictureHeight
    $PictureWidth = $PictureWidth * $Multiplier
}

$pic = $Slide.Shapes.AddPicture(($RandomPicture.FilePath),$msoFalse, $msoTrue,$PicturesLeft,$PicturesTop, $RandomPicture.Width, $RandomPicture.Height)

$Imgage.RawFormat.Equals([System.Drawing.Imaging.ImageFormat]::Png)

Act 5

$Slide.SlideShowTransition.EntryEffect = 769


$Slide.Shapes.Title.AnimationSettings.TextLevelEffect = 1
$Slide.Shapes.Title.AnimationSettings.EntryEffect = 769
$Slide.Shapes.Title.AnimationSettings.Animate = $msoTrue

$Animations = 3844, 769, 770, 3074, 3073, 1025, 1026, 3845, ... ... , 3347, 3348

$RandomAnimation = ($TextAnimationEffects | Get-Random)
$Slide.Shapes.Title.AnimationSettings.EntryEffect = $RandomAnimation

Falling Action

Act 6

[gc]::collect()
[gc]::WaitForPendingFinalizers()
[gc]::collect()
[gc]::WaitForPendingFinalizers()
$PPTDocument.Saved = $msoTrue
$PPTDocument.Close()
$null = [System.Runtime.InteropServices.Marshal]::FinalReleaseComObject($PPTDocument)
$PPTDocument = $null
[gc]::collect()
[gc]::WaitForPendingFinalizers()
[gc]::collect()
[gc]::WaitForPendingFinalizers()
$PPTApplication.quit()
$null = [System.Runtime.InteropServices.Marshal]::FinalReleaseComObject($PPTApplication)
$PPTApplication = $null
[gc]::collect()
[gc]::WaitForPendingFinalizers()
[gc]::collect()
[gc]::WaitForPendingFinalizers()

Dénouement

• Generate random content for SharePoint – About how to create big files for upload testing.
• Generate random content for SharePoint 2 – About how to generate Word files for Search and integration testing.
• Generate random content for SharePoint 3 – About how to generate Excel files for Search and integration testing. (This article.)
• Generate random content for SharePoint 4 – About how to generate PowerPoint files for Search and integration testing.

Exposition

Rising Action

Act 1

# Generate the first line with the headers
For ($Column = 1; $Column -le $Columns; $Column++)
{
    $RandomWordLine = Get-Random -Minimum 1 -Maximum $DictionaryFileRows
    $RandomWord = $DictionaryFileContent[$RandomWordLine]
    $FileStream.Write("`t$RandomWord")
}
# And the rows with the content
For ($Row = 1; $Row -le $Rows; $Row++)
{
    $FileStream.Write("`r`n") # New line
    $RandomWordLine = Get-Random -Minimum 1 -Maximum $DictionaryFileRows
    $RandomWord = $DictionaryFileContent[$RandomWordLine]
    $fileStream.Write("$RandomWord`t") # Row first column
    For ($Column = 1; $Column -le $Columns; $Column++)
    {
        $NumberTXT = [string](Get-Random -Minimum 1 -Maximum 10000) + "`t"
        $FileStream.Write($NumberTXT) # The actual numbers in the table
    }
}

Act 2

Climax

Act 3

• If we do not have a template Excel file, then we have to create TXT files, then convert them into XLSX. Not a big burden, but it has a little performance impact.

$ExcelWorkBook = $ExcelApplication.Workbooks.Open($TempTXT)
$ExcelWorkBook.SaveAs($ExcelFile, [Microsoft.Office.Interop.Excel.XlFileFormat]::xlWorkbookDefault)
$ExcelWorkBook.Saved = $true
$ExcelWorkBook.Close()

• If we do have a template file, then we have to copy-paste the content into the file. Yes, copy-paste. It is working, but if you want to use the machine while the files are being generated, then it might cause some problems.

$TempDocument = $ExcelApplication.Workbooks.Open($TempTXT,$null,$true)
$TempSheet = ($TempDocument.Sheets)[1]
$CopiedContent = $TempSheet.UsedRange.Copy()
$Pasted = $ExcelSheet.Range("A1").PasteSpecial()

• The [Microsoft.Office.Interop.Excel.XlFileFormat]::xlWorkbookDefault directive is defining the output file format, so if you want to generate different files, you could change it to fit your needs. The full list of possible output formats in the XlFileFormat enumeration article.
• The ($TempDocument.Sheets)[1] definition is not as any other array references as we do not start from zero, but from one.
• Last, but not least the $TempSheet.UsedRange.Copy() call is the one that copies the content to the clipboard, and this is where you might wish to not use your computer, because you might end-up losing some information.

Act 4

<?xml version="1.0" encoding="UTF-8" standalone="true"?>
<cp:coreProperties xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dcmitype="http://purl.org/dc/dcmitype/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cp="http://schemas.openxmlformats.org/package/2006/metadata/core-properties">
<cp:lastModifiedBy>Zsolt Illes</cp:lastModifiedBy>
<dcterms:created xsi:type="dcterms:W3CDTF">2017-03-02T07:17:00Z</dcterms:created>
<dcterms:modified xsi:type="dcterms:W3CDTF">2017-03-02T07:17:00Z</dcterms:modified>
</cp:coreProperties>

$CreatorNameSpace = 'http://purl.org/dc/elements/1.1'
$CreatorElement = $CoreXML.CreateElement('dc','creator',$CreatorNameSpace)
$null = $CoreXML.DocumentElement.AppendChild($CreatorElement)

<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/" />

<dc:creator />

$CreatorNameSpaceToNull = ' xmlns:dc="' + $CreatorNameSpace + '"'
$CoreXML = $CoreXML.OuterXml.Replace($CreatorNameSpaceToNull,'')

[System.Xml.XmlNamespaceManager]$NameSpaceManager = New-Object System.Xml.XmlNamespaceManager $CoreXML.NameTable
$NameSpaceManager.AddNamespace('dc', 'http://purl.org/dc/elements/1.1/')
$DCNameSpace = $NameSpaceManager.LookupNamespace('dc')
$NewElement = $CoreXML.CreateElement('dc', 'creator', $DCNameSpace)

Falling Action

Act 5

• Dictionary for the Row- and Column headers,
• Random generator for the numbers,
• A list for users and dates to update the document properties,
• Way to push all this information into an Excel file,
• I’ve not detailed it in this article, but my solution also contains a routine to use a pre-defined Excel file template. This might come handy if you want to fine tune your search experience even more. (Just think about search driven solutions for example.)

Dénouement

• Generate random content for SharePoint - About how to create big files for upload testing.
• Generate random content for SharePoint 2 - About how to generate Word files for Search and integration testing. (This article.)
• Generate random content for SharePoint 3 - About how to generate Excel files for Search and integration testing.
• Generate random content for SharePoint 4 - About how to generate PowerPoint files for Search and integration testing.

Exposition

Rising Action

Act 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Video provides a powerful way to help you prove your point.

Act 2

Climax

Act 3

$DictionaryFile = Get-Content '.\words_en.txt'
$DictionaryFile | Get-Random

$DictionaryFileRows = $DictionaryFile.Count
$RandomWordLine = Get-Random -ProviderName 1 -Maximum $DictionaryFileRows
$RandomWord = $DictionaryFileContent[$RandomWordLine]

Act 4

$WordApplication = New-Object -ComObject "Word.Application"
$WordDocument = $WordApplication.Documents.Add()
$WordSelection = $WordApplication.Selection
$WordSelection.InsertAfter($RandomWord)
$WordSelection.InsertAfter($RandomSeparator)

[string]$LongString = ''
For($i=1; $i -le $WordCount; $i++)
{
    $RandomWordLine = Get-Random -Minimum 1 -Maximum $DictionaryFileRows
    $RandomWord = $DictionaryFileContent[$RandomWordLine]
    $RandomSeparator = $Separators[(Get-Random -Minimum 0 -Maximum $($Separators.Count))]
    $RandomWord = $RandomWord + $RandomSeparator
    $LongString = $LongString + $RandomWord
}
$WordSelection.Select()
$WordSelection.Delete()
$WordSelection.InsertAfter($LongString) 

Act 5

<?xml version="1.0" encoding="UTF-8" standalone="true"?>
<cp:coreProperties xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dcmitype="http://purl.org/dc/dcmitype/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cp="http://schemas.openxmlformats.org/package/2006/metadata/core-properties">
<dc:title/>
<dc:subject/>
<dc:creator>Zsolt Illes</dc:creator>
<cp:keywords/>
<dc:description/>
<cp:lastModifiedBy>Zsolt Illes</cp:lastModifiedBy>
<cp:revision>3</cp:revision>
<dcterms:created xsi:type="dcterms:W3CDTF">2017-03-02T07:17:00Z</dcterms:created>
<dcterms:modified xsi:type="dcterms:W3CDTF">2017-03-02T07:17:00Z</dcterms:modified>
</cp:coreProperties>

• The creator and lastModifiedBy fields should be presented in SIP format, so that the presence information
• The created and modified fields are in Sortable Time Format.

$RandomDateNr = Get-Random -Minimum 0 -Maximum $DatesCount
$RandomDate = $DatesList[$RandomDateNr]
$CoreXML.coreProperties.created.'#text' = $RandomDate.ToString()
# Here we need a trick, as we have to make sure the last modifed
# date is not earlier than the date creation. (This is why we ordered the list.)
$RandomDateNr = Get-Random -Minimum $RandomDateNr -Maximum $DatesCount
$RandomDate = $DatesList[$RandomDateNr]
$CoreXML.coreProperties.modified.'#text' = $RandomDate.ToString()

$WordFile = [System.IO.Compression.ZipFile]::Open( $WordFilePath, 'Update' )
$ZippedCoreXMLFile = [System.IO.StreamWriter]($WordFile.Entries | Where-Object { $_.FullName -match 'docProps/core.xml' }).Open()
$ZippedCoreXMLFile.BaseStream.SetLength(0)
$ZippedCoreXMLFile.Write($Script:CoreXML.OuterXml)
$ZippedCoreXMLFile.Flush()
$ZippedCoreXMLFile.Close()
$WordFile.Dispose()

Falling Action

Act 6

• Dictionary for words,
• Separator list,
• A list for users and dates to update the document properties,
• and  a nice way to push all this information into a Word document directly.
• I've not detailed it in this article, but my solution also contains a routine to use a pre-defined Word file template. This might come handy if you want to fine tune your search experience even more. (Just think about search driven solutions for example.)

Dénouement

• Generate random content for SharePoint - About how to create big files for upload testing.(This article.)
• Generate random content for SharePoint 2 - About how to generate Word files for Search and integration testing.
• Generate random content for SharePoint 3 - About how to generate Excel files for Search and integration testing.
• Generate random content for SharePoint 4 - About how to generate PowerPoint files for Search and integration testing.

Exposition

Rising Action

Act 1

1. Remember that you need unique content. While this function is useful to generate excessive number of paragraphs, the content in them will be repeating, and we already know, this is not useful for us because of the Shredded Storage.
2. Since Microsoft introduced the Office Open XML file format, the actual text is being compressed into a simple ZIP file, so generating big files (above a few 100KBs) will be quite hard. Yes, we could fill the content with picture, but this would be once again not be the brightest idea if we want to process the file content with the Search.

• Have unique content.
• Have sensible content that we can search for.
• Vary by size.

Act 2

a3284fbb-6fd6-49bc-a0de-f12886a3e648

$GUID = ([guid]::NewGuid()).ToString()
$StringToDump = $GUID.Replace('-','_')

$FileStream = New-Object System.IO.FileStream($FullFilePath,[System.IO.FileMode]::CreateNew)
$StreamWriter = New-Object System.IO.StreamWriter($FileStream,[System.Text.Encoding]::ASCII,128)

# Logic to generate n number of GUIDs.
...
$StreamWriter.Write($StringToDump)
...
# End of logic to generate n number of GUIDs.

$StreamWriter.Close()
$FileStream.Close()

• A target folder where we're going to save the files.
• Maybe a file prefix parameter.
• A set of parameters for different pre-defined size of files.
  • Some pre-defined sizes:  5KB, 10KB, 20KB, 50KB, 100KB, 200KB, 500KB, 1MB, 2MB, 5MB, 10MB, 20MB, 50MB, 100MB, 200MB, 500MB, 1GB.
• A parameter for custom sizes.
• And maybe a switch parameter to create a folder for each file size.

Climax

Act 3

# For network drives:
$Disk = Get-WmiObject Win32_LogicalDisk | ?{($_.ProviderName) -and ($DestinationFolder -like "*$($_.ProviderName)*")}
# For local drives:
$Disk = Get-WmiObject Win32_LogicalDisk -Filter $("DeviceID='" + $DestinationDrive + "'")

$PhysicalMemory = (((Get-CimInstance -ClassName "cim_physicalmemory").Capacity) | Measure-Object -Sum).Sum

Falling Action

Act 4

Dénouement

function MyFunction
{
    param
    (
        [int]$5turns
    )
    Write-Host $5turns
} 

MyFunction: Cannot process argument transformation on parameter '5turns'. Cannot convert value "-5turns" to type "System.Int32". Error: "Input string was not in a correct format."

Act 1

int a = 1
int 2a = 3
int b = 2a

Dénouement

Rising action

Climax

1. One does not need to be a SharePoint superuser to be able to create a business logic that is to be implemented in SharePoint.
2. One can port their precious Workflows between environments with ease.

Act 1

• the actual list where you deploy your workflow to,
• the Workflow History List,
• the Workflow Task List.

• the association scope between the SharePoint site and the Workflow Manager farm is different, because that's another GUID.

Act 2

1. Create the basic structure of your solution in your DEV environment, including the
   • List(s) that you will use to store your data
   • Workflow History List
   • Workflow Task List
2. Port your list to the other environments (TEST, UAT and PROD). For this you can use
   • Content Database transfer
   • SharePoint solution that deploys the above lists with the same GUID throughout the environments. (This is the option you have to choose when you are in a Hybrid scenario, as you cannot just port the ContentDB to SharePoint Online.)  (Seems this is not an option unfortunately. Thanks to my colleagues Westin Kirebel who highlighted this, and Istvan Fabian, who helped with the clarification. Sorry.)
3. Have your Business Champ create the Workflow in Visio 2013. (This is an optional step, if you are the Site Administrator and you know what you want to achieve.)
4. Import the saved Workflow into SharePoint Designer - or create your own if you skipped Step 3 - and bound it to the List. Map the fields and do whatever other modifications are needed to make the Workflow working in SharePoint.
5. Export the Workflow from SPD.
6. Copy the VSDX file to your other environments.
7. Import the VSDX file in your other environments and bound them to the same lists.
8. Enjoy your solution.

Act 3

Falling Action

Dénouement