voxpupuli / puppet-visualstudio

puppet module for managing Microsoft Visual Studio

Visual Studio module for Puppet

Table of Contents

1. Overview
2. Module Description - What is the visualstudio module?
3. Setup - The basics of getting started with visualstudio
   • What visualstudio affects
   • Beginning with visualstudio
4. Usage - Configuration options and additional functionality
5. Reference - An under-the-hood peek at what the module is doing and how
6. Limitations - OS compatibility, etc.
7. Development - Guide for contributing to the module

Overview

Puppet module for managing Microsoft Visual Studio

Module Description

The purpose of this module is to install the Microsoft Visual Studio suite and configure it's many service packs, tools, utilities and registry options.

Setup

What autoupdates affects

• Installs packages
• Alters registry keys

Beginning with autoupdate

Installing Visual Studio 2012:

    visualstudio { "visual studio":
      ensure      => present,
      version     => '2012',
      edition     => 'Professional',
      license_key => 'XXX-XXX-XXX-XXX-XXX',
    }

Usage

Classes and Defined Types

Defined Type: visualstudio

The primary definition of this module, it installs and configures the visual studio application on the system

Parameters within visualstudio:

ensure

Ensure that the application is installed or not.

version

The version of visual studio that should be installed

edition

The edition of visual studio that should be installed

license_key

The license key that corresponds to the version and edition that you have specified. This is required for installation to be successful.

components

The list components, tools and utilities that can be installed as part of the visual studio installation.

deployment_root

Network location where the visual studio packages are located

Reference

Defined Types

Public Defined Types

• visualstudio: Guides the basic installation and configuration of visual studio

Limitations

This module is tested on the following platforms:

• Windows 2008 R2

It is tested with the OSS version of Puppet only.

It support the following Visual Studio versions:

• 2012

Development

Contributing

Please read CONTRIBUTING.md for full details on contributing to this project.

puppet-visualstudio's Issues

VS2010 Support

I'm working on VS2010 support. I think adding it to your existing work makes sense. The unattended installation method is almost completely different from 2012 though so there is a lot of non-reuse.

One of my current design decisions is to separate the installation of VS2010 and SP1. There are a few installation instances where something else needs to be installed between the two. So I've effectively added a 2010 and a 2010SP1 version to the module.

I'm looking at some refactoring of how parameters etc get looked up and what parameters are available to users of the module, ie I'm exposing the deployment root as an option rather than having to modify the module.

I was wondering if there is a reason for the double verification of parameters in both the package and the init?

Let me know if you have any input. I've been reading up on module best practices and trying to keep mostly in line with what you've done

Archiving this module

The discussion came up of this module should get archived. Should someone want to keep this module around, just comment here.
If no comments to keep this around arise in the new weeks, we will move forward with archiving.

Add support for puppetlabs/powershell >= 2.0.0.

Currently puppet-visualstudio requires puppetlabs/powershell < 2.0.0, please support 2.x versions as well.