Skip to content

Latest commit

 

History

History
113 lines (91 loc) · 5.49 KB

README.md

File metadata and controls

113 lines (91 loc) · 5.49 KB

ms_dotnet Cookbook

Cookbook Version Build Status

Install the Microsoft .NET Framework.

Requirements

This cookbook supports Chef 11.10.0+

Platforms

  • Windows XP
  • Windows Vista
  • Windows Server 2003 R2
  • Windows 7
  • Windows Server 2008 (R1, R2)
  • Windows 8 and 8.1
  • Windows Server 2012 (R1, R2)

Cookbooks

The following cookbook is required as noted:

  • windows (> 1.36.1)

    ms_dotnet::default include the recipe 'windows::default' ms_dotnet::ms_dotnet2 and ms_dotnet::ms_dotnet4 leverage the windows_package LWRP ms_dotnet::ms_dotnet2, ms_dotnet::ms_dotnet3 and ms_dotnet::ms_dotnet4 leverage the windows_feature LWRP

Known Issues

Here are the known issues you can encounter with ms_dotnet recipes:

  • "Access denied" error on windows_package when running chef via WinRM
    • Cause: winrm limitation
    • Common environment: knife windows bootstrap, chef-provisioning, test-kitchen
    • Best solution: your remoting system should try to simulate a local session (psexec or schedule task)
    • Other solution: create your custom wrapper to simulate a local session

Attributes

ms_dotnet::ms_dotnet2

  • node['ms_dotnet']['v2']['name'] - used to configure the Windows Package name
  • node['ms_dotnet']['v2']['url'] - used to configure the source of the Windows Package
  • node['ms_dotnet']['v2']['checksum'] - used to configure the checksum of the Windows Package

ms_dotnet::ms_dotnet3

  • node['ms_dotnet']['v3']['enable_all_features'] - enable all parent features when installing NetFx3 (only supported on NT Version 6.2 or newer, default to true)
  • node['ms_dotnet']['v3']['source'] - used to configure the source of the Windows Package (only supported on NT Version 6.2 or newer)

ms_dotnet::ms_dotnet4

  • node['ms_dotnet']['v4']['version'] - used to configure the desired version of .NET4 ('4.0', '4.5', '4.5.1', '4.5.2')
  • node['ms_dotnet']['versions'][desired_version][feature]['name'] - used to configure the Feature name to use instead of a Windows Package for the specified desired_version
  • node['ms_dotnet']['versions'][desired_version][package]['name'] - used to configure the Windows Package name for the specified desired_version
  • node['ms_dotnet']['versions'][desired_version][package]['url'] - used to configure the source of the Windows Package for the specified desired_version
  • node['ms_dotnet']['versions'][desired_version][package]['checksum'] - used to configure the checksum of the Windows Package for the specified desired_version
  • node['ms_dotnet']['versions'][desired_version][patch]['name'] - used to configure the Windows Package name of the patch to apply for the specified desired_version
  • node['ms_dotnet']['versions'][desired_version][patch]['url'] - used to configure the source of the Windows Package of the patch to apply for the specified desired_version
  • node['ms_dotnet']['versions'][desired_version][patch]['checksum'] - used to configure the checksum of the Windows Package of the patch to apply for the specified desired_version

Usage

ms_dotnet::ms_dotnet2

To install Microsoft .NET Framework 2.0 on your node, just include the recipe ms_dotnet::ms_dotnet2 in its run_list. You can use a custom windows package by specifing the 3 attributes specified in the above section.

ms_dotnet::ms_dotnet3

To install Microsoft .NET Framework 3.0 on your node, just include the recipe ms_dotnet::ms_dotnet3 in its run_list.

NB: Starting with NT Version 6.2 (Windows 8/2012) .NET 3 is an on demand feature. Meaning that you need either to use the installing media or a custom windows image to enable the feature. See: http://msdn.microsoft.com/library/hh506443

ms_dotnet::ms_dotnet4

To install Microsoft .NET Framework 4 on your node, just include the recipe ms_dotnet::ms_dotnet4 in its run_list. Modify the version to install by changing the attribute node['ms_dotnet']['v4']['version'].

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

License and Authors

Authors: Baptiste Courtois ([email protected]), Jeremy Mauro ([email protected])

Copyright 2014-2015, Criteo.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.