Month: January 2019

Feb 21 NorthWest Chicago JavaScript Meetup – Fixing Memory Problems in Single Page Apps 

Marky Roden Just Marky

As always the NWCJS meetups will be held in the PSC Office in Schaumburg – everyone is welcome 🙂

 

Fixing Memory Problems in Single Page Apps
by Mike Labriola

Single Page Apps may run for hours or days without the user closing or refreshing their browser. This poses a huge problem for JavaScript developers that may not be aware of how much memory their app is using, reusing or squirreling away without need. The problem gets bigger as the device gets smaller, with the biggest pain felt by users of progressive web apps on mobile devices. Come and learn how memory management works in the browser and how you can use the tools that ship with Google Chrome to observe, and debug, your memory management woes.

https://www.meetup.com/Northwest-Chicago-JavaScript/events/257291661/ #nwcjs

Office Add-in Community call 9 Jan 2019

Marky Roden Office Add-In ,

This months meeting is Wednesday Jan 9th – 8am PST

You can sign up for the Office DEveloper community calls here – https://aka.ms/OfficeDevCalls

The Office Add-ins community call is our quarterly event for developers to connect in real-time with the folks who are building the Office JavaScript APIs. During this call, we’ll share updates about new Office JavaScript APIs and provide tips about useful tools, samples, and resources for developing Office Add-ins. Additionally, each call will feature a technical deep dive on a specific topic and will conclude with an opportunity for attendees to ask questions and share feedback.

If you’d like to submit questions before the call, please use this form – https://aka.ms/officeaddinsform

Join the call here – https://aka.ms/officeaddinscall

 

PSC Tech Talk: Using AzureDevOps to Automate the Build and Deployment of SharePoint Framework widgets

Marky Roden Tech Talks , , ,

During this PSC Tech Talk, Mark Roden gave a precursory run-through presentation for his SharePointFest Chicago 2018 presentation on the automation of build and deployment for SharePoint Framework widgets.

What is AzureDevops

Mark briefly walked through why AzureDevOps is PSC’s tool of choice for managing Agile projects. During an Agile project we build and deploy projects every two weeks so that progress can be demonstrated to clients and to ensure that the process is tested and working. Azure DevOps allows us to manage the whole process from:

  • Requirements Management (Backlog)
  • Project Management (Sprint Boards)
  • Code Source Control (git)
  • Automated Build and Deploy pipelines
  • Automated Testing

Quality

Having a transparent, visible to a client, Quality control process generates trust. Not only in the development process but also in the process for deployment. PSC uses AzureDevOps capabilities to run unit tests and where appropriate load testing of projects in development. SharePoint Framework is no exception. We want to make sure that anything being developed does not break existing code or the user interface. Traditionally testing would be done at the end of the project. In an Agile project it is done every two weeks.

What is SharePoint Framework?

Traditionally SharePoint on premises allowed an organization to customize the functionality using a “trusted-code” model whereby they were in complete control of the code going into their environment. When SharePoint online came out though this model was not available. Because of the shared-tenant model and because of a lack of access to modify SharePoint in a similar manner than on prem, Microsoft create the front-end-based SharePoint Framework model.

SharePoint online and therefore the SharePoint Framework (SPFx) are based on the React JavaScript framework. Developers create components which are directly integrated into the SharePoint online experience as if they were a first class member of the site.

Hello world 

Mark’s presentation used the Hello World example provided by Microsoft as a simple demonstration of how to build and deploy an SPFx widget locally. Mark then walked through the process of adding the widget manually to his SharePoint on line development tenant. Manually this process takes a couple of hours to set up and then about 10-15 minutes for every successful deployment.

Using AzureDevOps

Mark walked through the “build” and “deployment” processes provided by Microsoft in the AzureDevOps tool. The Build process manager has the ability to create separate tasks which simulate the manual process of creating the deployable code as explained in the Hello World example. The build process is triggered by checking the code into the Master branch.

The deployment process is similar and automates the process of taking the code and moving it out to the SharePoint tenant. The deployment is triggered on the completion of a successful “build”.

The Build and deployment process takes approximately 5 minutes and Mark showed the ability to track progress and see the console logging provided. Mark’s example also provided code coverage reports and testing dashboards.

Summary

When working on agile projects PSC recommends using AzureDevOps as the management tool of choice and as Mark demonstrated in this Tech Talk, building, testing and deploying SharePoint Framework widgets can automated.