NOTE – PDF format updated to include both SharePoint 2013, 2016, and 2019 notes.
Ever wondered what fixes are inside of a given CU? Please see attached PDF with full detail. I wanted a new format for easy reading. Show management and make the business case for why downtime should be taken to apply CUs. Also posted at http://sharepointupdates.com/
If you found this helpful, please leave a comment.
![shades_smile_thumb_thumb_thumb_thumb[2]](https://www.spjeff.com/wp-content/ftp_uploads/Whats-in-that-patch-SharePoint-2013--Oct_A762/shades_smile_thumb_thumb_thumb_thumb2.gif "shades_smile_thumb_thumb_thumb_thumb[2]")
| What’s in that patch – Oct 2019.PDF |
Demo for how to configure SnagIt Preset with Image only to avoid extra dialog prompting for Image or Video. Few people use SnagIt video, so skip the prompt.
Saves time with every screen capture you make. Cheers.
Recently I had F12 network trace open and launch OneDrive “Sync” button from SharePoint Modern pages toolbar. A strange protocol showed on the network activity. Not HTTP or HTTPS, but “ODOPEN://”
Application launcher custom URL prefixes enable web browsers to handoff to local desktop applications. Here, ODOPEN is One Drive Open and activates the OneDrive client by passing parameters for the scope destination document library to sync.
Parameters are enumerated below in the Code section. GUID for the scope (Site / Web / Library) identify the target data. Current user detail is passed with user GUID and user Email. Interesting to see how the “Sync” button works internally and wanted to share notes.
Cheers
odopen://sync?userId=45f4af2f-e9e9-48a9-93c5-00df32aa7488&
userEmail=spjeff@spjeff.com&
isSiteAdmin=1&
siteId={07a88858-981d-4465-b36b-52ae6065d6b0}&
webId={c1c208d9-5b06-4703-981c-f6240fb45c4d}&
webTitle=Jeff Jones&
webTemplate=21&
webLogoUrl=_layouts/15/images/siteicon.png&
webUrl=https://spjeff-my.sharepoint.com/personal/spjeff_spjeff_com&
onPrem=0&
libraryType=1&
listId={9CBDD007-6D00-4F69-8D2C-BDD10D95F518}&
listTitle=Documents&
scope=OPENLIST
Below end to end demonstration of creating SharePoint Framework (SPFX 1.9) with Azure Dev Ops (ADO) code repository to hold original source. ADO uses for source code repositry (repo) to hold the SPFX project code.
From there, ADO “Build” creates SPPKG dynamically with a Ubuntu container VM that employs NODE and NPM install to load all dependency. Centralized container build has the benefit of uniform consistency. No developer workstation configurations. No server setting inconsistency.
Finally ADO “Release” copies the SPPKG into SharePoint Online App Catalog with Office 365 Command Line Interface (CLI). From there, it can be added to page on sites across the O365 Tenant.
Cheers.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 |
pool: name: Azure Pipelines steps: - task: NodeTool@0 displayName: 'Use Node 10.x' inputs: versionSpec: 10.x checkLatest: true - task: Npm@1 displayName: 'npm install' inputs: verbose: false - task: Npm@1 displayName: 'npm test' inputs: command: custom verbose: false customCommand: test - task: PublishTestResults@2 displayName: 'Publish Test Results temp/test/junit/junit.xml' inputs: testResultsFiles: temp/test/junit/junit.xml searchFolder: '$(Build.SourcesDirectory)' - task: PublishCodeCoverageResults@1 displayName: 'Publish code coverage from $(Build.SourcesDirectory)/temp/test/cobertura-coverage.xml' inputs: codeCoverageTool: Cobertura summaryFileLocation: '$(Build.SourcesDirectory)/temp/test/cobertura-coverage.xml' reportDirectory: '$(Build.SourcesDirectory)/temp/test' - task: Gulp@0 displayName: 'gulp bundle' inputs: targets: bundle arguments: '--ship' publishJUnitResults: true - task: Gulp@0 displayName: 'gulp package-solution' inputs: targets: 'package-solution' arguments: '--ship' - script: 'dir sharepoint/solution/*.sppkg' displayName: DIR - task: CopyFiles@2 displayName: 'Copy Files to: $(build.artifactstagingdirectory)/drop' inputs: Contents: 'sharepoint/solution/*.sppkg' TargetFolder: '$(build.artifactstagingdirectory)/drop' - task: PublishBuildArtifacts@1 displayName: 'Publish artifacts: drop' inputs: PathtoPublish: '$(Build.ArtifactStagingDirectory)/drop' |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
steps: - task: NodeTool@0 displayName: 'Use Node 10.x' inputs: versionSpec: 10.x steps: - task: Npm@1 displayName: 'npm custom' inputs: command: custom verbose: false customCommand: 'install -g @pnp/office365-cli' #Your build pipeline references a secret variable named ‘password’. Create or edit the build pipeline for this YAML file, define the variable on the Variables tab, and then select the option to make it secret. See https://go.microsoft.com/fwlink/?linkid=865972 variables: tenant: 'spjeff' catalogsite: 'sites/catalog' username: 'spjeff@spjeff.com' steps: - script: 'o365 spo login https://$(tenant).sharepoint.com/$(catalogsite) --authType password --userName $(username) --password $(password)' displayName: 'Command Line Script' steps: - script: 'o365 spo app add -p $(System.DefaultWorkingDirectory)/SPFX-CICD/drop/sharepoint/solution/code.sppkg --overwrite' displayName: 'Command Line Script' variables: tenant: 'spjeff' catalogsite: 'sites/catalog' steps: - script: 'o365 spo app deploy --name code.sppkg --appCatalogUrl https://$(tenant).sharepoint.com/$(catalogsite)' displayName: 'Command Line Script' |
Fun software I work with every day.
Return to Top ▲