Office UI Fabric for VSTS Extensions – Extension Time

We continue from Office UI Fabric for VSTS Extensions – a few moving bits. Now that we have some code to compile, we need to package it so that we can upload an extension to VSTS. Upload First we need to make sure that the tfx-cli is installed globally: npm install tfx-cli -g. This is…

0

Office UI Fabric for VSTS Extensions – a few moving bits

Moving on from Office UI Fabric for VSTS Extensions – Typescript tools, we can start adding a few “moving bits” and tasks to perform and automate various tasks. I’m going to use npm tasks, because it is just simpler that way. You could use something like gulp tasks etc. if you prefer. First things first,…

0

Office UI Fabric for VSTS Extensions – Typescript tools

In the series of blog on how to leverage Office UI Fabric in VSTS Extensions , we continue on from Office UI Fabric for VSTS Extensions – Getting Started and start to delve into how to setup our development environment. TSLInt To start off with, Lint is a set of tools to provide static code…

0

Office UI Fabric for VSTS Extensions – Getting Started

Continuing from Office UI Fabric for VSTS Extensions. I have spent way too much time trying to get things running the way that I want them to, based on concepts, intentions, and bootstrapping found on blogs and technical websites. To simplify, I’ve created this series of posts the highlights a “from scratch” way to setup…

0

Office UI Fabric for VSTS Extensions

Office UI Fabric is the “official front-end framework for building experiences that fit seamlessly into Office and Office 365”. It is a set of UI styles and JavaScript based controls that are geared towards providing seamless visual and component level integration with modern Office applications. It consists of several “simple” components such as buttons, labels…

0

Empowering the community with our OSS projects

If you’re following our continuous transformation to Agile practices and DevOps, you’ll realize that we have come a long way with self-organizing and self-managing teams. See our stories for details. We’re ready to take the next step! We’re handing over our github.com/ALM-Rangers organisation and repositories to our community of ALM | DevOps Ranger contributors. What…

0

Why we’re using AWS, not Azure, to store our OSS releases

We’ve received the question “why are you storing your releases on AWS and not on Azure” for projects, such as the vsts-agent and ALM-Rangers/Migrate-assets-from-RM-server-to-VSTS. For example, when you’re downloading a release from either of these projects you’ll notice amazonaws in the download URLs, as highlighted below: Both projects, and others, are open source solutions (OSS)…

0

Manage your open source usage and security in your pipeline

The open source approach has a tremendous value for us as a technological community. The collaborative development model helps the industry evolve rapidly, increase innovation and save time and money. We all use open source components in our applications, front or back end, JavaScript, .NET or Python, whether it is a JSON serialization library or…

4

Why are we open sourcing our extensions?

We plan to open source many of our solutions, listed on library of tooling and guidance solutions, to share them as sample code, foster community collaboration and innovation. Our mission is to “provide professional guidance, practical experience and gap-filling solutions”. When we ship a solution, we need to switch context to other gaps, limiting our…

5

Library of tooling and guidance solutions (aka.ms/vsarsolutions)

A library of out-of-band tooling and practical guidance, extensions,  and community solutions, complementing our publications (aka.ms/vsarpublications). You can get information about new features and bug fixes included in the releases here. Extensions | Guidance and Tooling | Community Solutions | Retiring Guidance and Tooling | Deprecated Solutions Extensions Library of Visual Studio and Visual Studio…

4