When I created my first teamsite in SharePoint 2019 on-prem, I was impressed with the new elegant design. However as soon as I opened the Document Library - I feel that something was amiss.
Following screenshot is the Document library in SharePoint 2019 on-prem:
I can no longer find “Document” template when I click on “New". In SharePoint 2019 on-prem its only showing “Folder” and “Link” under “New” button while in SharePoint online I can see Document templates and ‘+ Add template’ menu.
Last month I bought new external SSD drive of 512 GB. I plan to use it as a file history backup of my Windows 10. Initially, I have no idea why I left with only 25 GB free space after I activate the file history. Until this morning when I really need more space, I started to find out more what is actually happening.
I right click a folder in C:\ and the compare it with the external SSD, and found out that the ratio between Size and Size on disk are different between both.
After spending some times drawing on the board and planning, finally I have time to start realizing the idea. You can read in other post why I am starting Generator-Office-X. I spend 2 weekends to read blogs, open source and finally come up with the first release of Generator-Office-X in npm library.
Releasing Generator-Office-X Generator-Office-X is now available in NPM official repository (https://www.npmjs.com/package/generator-office-x). You will need Yeoman before you can use generator-office-x.
The installation experience of SharePoint 2019 to Windows Server 2019 was brisk except that I have issue during pre-requisites installation. It takes me sometimes before I realize that SharePoint 2019 still require Windows features that depends on .NET Framework 3.5.
I launched prerequisites installer, and it stops quickly with error.
I click “Review the log file” in the error window, then it opens the log file in Notepad.
As you can see, that prerequisites installer executes Install-WindowsFeature.
December and January was a busy month for me, I have been reading lot about Yeoman generator. There is not much documentation about Yeoman generator, and even if there is some documentation I feel it is far from clarity. I don't want to offence the Yeoman folks, in fact they have done very great job. I read their source code in Yeoman GitHub repository here to understand how does it work, and to get some ideas directly from the source code.
What do you need? Azure Devops account (signup here : https://aka.ms/SignupAzureDevOps ) GitHub account (signup here: https://github.com/join ) I will not elaborate how to create project in Azure Devops or GitHub. In this example, I created generator-office-x repository in both GitHub and Azure Devops account. The GitHub will be used to store the source code and Azure Devops will be used to run the build pipeline.
Add “Azure pipeline” GitHub App to the Repository 1 - Open Github marketplace and search for “azure pipeline”
When you read this post, I assume that you have already known that I started to create open source project Generator-Office-X. If you want to know why, just visit the previous post.
I have been using Travis CI for most of my GitHub repo, so far I have found no problem using free CI/CD service from Travis CI. I also been using freemium build from Azure Devops (previously known as Visual Studio Team Services) for my private repo.
Howto configure Azure Pipelines for Github – Ideas For Free - Feb 2, 2019[…] you read this post, I assume that you have already known that I started to create open source project Generator-Office-X. If you want to know why, just visit the previous […]
[…] finally I have time to start realizing the idea. You can read in other post why I am starting Generator-Office-X. I spend 2 weekends to read blogs, open source and finally come up with the first release of […]
It's been a while since my pull request to Generator-Office for Vue template has been made. I can see that my pull request now has some conflict, after the master branch received new merge from others.
Conflict due other higher priority changes
While working on Office Add-ins generator using Vue, I made some modification in index.ts between line 294-295. I added action to copy 3 dot files: .eslintignore, .eslintrc.js and .
In part-2, I have described how start to create a new Office add-in Vue template generator. As new template author, I relies on Yeoman documentation, original generator-office source code and rounds of rounds of testing to ensure that the new template will work.
Fortunately the generator-office source code has been developed with easy to follow structure. The source code is available openly, so that I can read and follow the framework - even with minimum documentation.