Chris Kent very quickly discovered an issue with the default schema the new SharePoint Framework Extensions Developer preview includes, and noted that bug here (thanks, Chris). The summary of the issue is that f you’re working with the new developer preview, you’ll currently get a schema error on the {AppName}ApplicationCustomizer.manifest.json file located within your {AppDirectory}/src/extension
Picture this: You’ve just created your first SharePoint Framework webpart, and you’re ready to slap your company logo on it, and send it out the door. It’s easy – you just reference your image in relation to your webpart file, via a require statement (which will push it into your ‘dist’ folder of assets), and
I enjoyed having the opportunity to head to Chicago over the weekend for #SPSChiBurbs, and give a session on getting started with the SharePoint Framework.
Having trouble with some of your pages in SharePoint 2013 rendering incorrectly at times, for no apparent reason? If so, you’ve come to the right place, provided that what I’m about to describe is actually your issue, and it’s not related to your html or css. Seems harmless right? It’s a content query webpart in
With the recent Thanksgiving Holiday, I thought it would be a good time to share a trick that will provide a feast of GUIDS. I like to use this method while doing SharePoint development, but it can really be useful anytime you have a need to create several GUIDs. While it is easy to create
When creating a new web application in SharePoint, you choose the physical location of where the IIS website will be created. Once the application is born, however, there is no longer an option to change this path in Central Administration. You can very easily change it in IIS (by going to your websites Properties ->
