Downloads:
6,570
Downloads of v 1.2.2:
1,359
Last Update:
31 Mar 2019
Package Maintainer(s):
Software Author(s):
- Microsoft
Tags:
microsoft visual studio visualstudio vs 2017 ide workload office sharepoint vsto admin- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Office/SharePoint development workload for Visual Studio 2017
This is not the latest version of Office/SharePoint development workload for Visual Studio 2017 available.
- 1
- 2
- 3
1.2.2 | Updated: 31 Mar 2019
- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
6,570
Downloads of v 1.2.2:
1,359
Maintainer(s):
Software Author(s):
- Microsoft
Office/SharePoint development workload for Visual Studio 2017 1.2.2
This is not the latest version of Office/SharePoint development workload for Visual Studio 2017 available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Microsoft. The inclusion of Microsoft trademark(s), if any, upon this webpage is solely to identify Microsoft goods or services and not for commercial purposes.
- 1
- 2
- 3
This Package Contains an Exempted Check
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Office/SharePoint development workload for Visual Studio 2017, run the following command from the command line or from PowerShell:
To upgrade Office/SharePoint development workload for Visual Studio 2017, run the following command from the command line or from PowerShell:
To uninstall Office/SharePoint development workload for Visual Studio 2017, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download visualstudio2017-workload-office --internalize --version=1.2.2 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade visualstudio2017-workload-office -y --source="'INTERNAL REPO URL'" --version="'1.2.2'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade visualstudio2017-workload-office -y --source="'INTERNAL REPO URL'" --version="'1.2.2'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install visualstudio2017-workload-office
win_chocolatey:
name: visualstudio2017-workload-office
version: '1.2.2'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'visualstudio2017-workload-office' do
action :install
source 'INTERNAL REPO URL'
version '1.2.2'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller visualstudio2017-workload-office
{
Name = "visualstudio2017-workload-office"
Version = "1.2.2"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'visualstudio2017-workload-office':
ensure => '1.2.2',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved as a trusted package on 31 Mar 2019.
Overview
This package adds the Office/SharePoint development workload to an existing installation of Visual Studio 2017 (Enterprise, Professional or Community).
The lists of components included in this workload in respective Visual Studio 2017 products are shown here:
Visual Studio 2017 must be installed first, for example using Chocolatey packages: visualstudio2017enterprise, visualstudio2017professional, visualstudio2017community.
Customizations
The package passes all package parameters to the Visual Studio installer, enabling full customization of the installation. The possible parameters are described here. The package passes --norestart --includeRecommended
by default, and --quiet
, unless --passive
is specified in the package parameters.
By default, the package installs components required by and recommended for the workload. Package parameters can be used to adjust this behavior:
--no-includeRecommended
- Does not include the recommended components.--includeOptional
- Includes the optional components.
By default, the package will detect installed Visual Studio products and add the workload to all products that support it and do not have it installed already.
In order to act on one specific product when several are installed, the product needs to be indicated to the package via parameters, either:
--installPath
- the path where the product is installed, for example "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise"
or (both are needed):
--productId
- the identifier of the product, for example "Microsoft.VisualStudio.Product.Enterprise"--channelId
- the release channel, should be "VisualStudio.15.Release"
Example 1. Installing the workload on all products, including recommended, but not optional components:
choco install visualstudio2017-workload-office
Example 2. Installing the workload on one specific product, including all recommended and optional components:
choco install visualstudio2017-workload-office --package-parameters "--productId Microsoft.VisualStudio.Product.Enterprise --channelId VisualStudio.15.Release --includeOptional"
Example 3. Installing the workload on all products, including only required components:
choco install visualstudio2017-workload-office --package-parameters "--no-includeRecommended"
Remove-VisualStudioWorkload `
-PackageName 'visualstudio2017-workload-office' `
-Workload 'Office' `
-VisualStudioYear '2017' `
-ApplicableProducts @('Community', 'Professional', 'Enterprise')
Log in or click on link to see number of positives.
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Office/SharePoint development workload for Visual Studio 2017 1.2.3 | 1673 | Thursday, March 11, 2021 | Approved | |
Office/SharePoint development workload for Visual Studio 2017 1.2.2 | 1359 | Sunday, March 31, 2019 | Approved | |
Office/SharePoint development workload for Visual Studio 2017 1.2.1 | 533 | Saturday, November 17, 2018 | Approved | |
Office/SharePoint development workload for Visual Studio 2017 1.2.0 | 778 | Wednesday, May 30, 2018 | Approved | |
Office/SharePoint development workload for Visual Studio 2017 1.2.0-rc2 | 320 | Thursday, May 17, 2018 | Approved | |
Office/SharePoint development workload for Visual Studio 2017 1.1.1 | 740 | Saturday, December 9, 2017 | Approved | |
Office/SharePoint development workload for Visual Studio 2017 1.1.0 | 770 | Thursday, March 9, 2017 | Approved | |
Office/SharePoint development workload for Visual Studio 2017 1.0.0-rc1 | 397 | Sunday, March 5, 2017 | Exempted |
https://www.microsoft.com/en-us/legal/intellectualproperty/permissions
-
- chocolatey-visualstudio.extension (≥ 1.8.0)
- vcredist2013 (≥ 12.0.30501.20150616)
- vcredist140 (≥ 14.16.27027.1)
- netfx-4.6.1-devpack (≥ 4.6.01055.00)
- netfx-4.5.2-devpack (≥ 4.5.5165101)
- KB2882822 (≥ 1.0.0)
- visualstudio-installer (≥ 2.0.0)
Ground Rules:
- This discussion is only about Office/SharePoint development workload for Visual Studio 2017 and the Office/SharePoint development workload for Visual Studio 2017 package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Office/SharePoint development workload for Visual Studio 2017, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.