Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
Downloads:
17,802
Downloads of v 0.2.180221-dev-20180516000001:
368
Last Update:
17 May 2018
Package Maintainer(s):
Software Author(s):
- Microsoft
Tags:
winobjc-tools;winobjc;vsimporter;winmd2objc;objc2winmd- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
winobjc-tools
This is a prerelease version of winobjc-tools.
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
17,802
Downloads of v 0.2.180221-dev-20180516000001:
368
Maintainer(s):
Software Author(s):
- Microsoft
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
Some Checks Are Exempted or Have Failed
1 Test Failing and 1 Exempted Test
Validation Testing Failed
Verification Testing Exempt:
This package requires VS 2017 to be installed.
To install winobjc-tools, run the following command from the command line or from PowerShell:
To upgrade winobjc-tools, run the following command from the command line or from PowerShell:
To uninstall winobjc-tools, run the following command from the command line or from PowerShell:
NOTE: This applies to both open source and commercial editions of Chocolatey.
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment-
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://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
choco download winobjc-tools --internalize --source=https://chocolatey.org/api/v2(additional options) - Run
choco push --source="'http://internal/odata/repo'"for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://chocolatey.org/api/v2)
4. Choose your deployment method:
choco upgrade winobjc-tools -y --source="'STEP 3 URL'" [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 winobjc-tools -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Ensure winobjc-tools installed
win_chocolatey:
name: winobjc-tools
state: present
version: 0.2.180221-dev-20180516000001
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
Coming early 2020! Central Managment Reporting available now! More information...
chocolatey_package 'winobjc-tools' do
action :install
version '0.2.180221-dev-20180516000001'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: winobjc-tools,
Version: 0.2.180221-dev-20180516000001,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller winobjc-tools
{
Name = 'winobjc-tools'
Ensure = 'Present'
Version = '0.2.180221-dev-20180516000001'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'winobjc-tools':
provider => 'chocolatey',
ensure => '0.2.180221-dev-20180516000001',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install winobjc-tools version="0.2.180221-dev-20180516000001" source="STEP 3 URL"
See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.
5. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
There are versions of this package awaiting moderation . See the Version History section below.
Command Line tools and Visual Studio Extensions for the WinObjC Project. This package includes vsimporter (the tool to convert an existing Xcode Cbjective-C project to a Visual Studio solution), winmd2objc (the tool to generate ObjC projections from Windows Metadata files (winmd)), objc2winmd (the tools to convert ObjC middleware to WinRT Component) as well as the Visual Studio Extensions (requires Visual Studio 2017 or later) for Objective C syntax highlighting and Nuget package creation. See https://github.com/Microsoft/WinObjC for more details.
# WinObjC.Frameworks
Accelerate.lib
Accounts.lib
AddressBook.lib
AddressBookUI.lib
AdSupport.lib
AssetsLibrary.lib
AudioToolbox.lib
AudioUnit.lib
AutoLayout.lib
AVFoundation.lib
AVKit.lib
CloudKit.lib
Contacts.lib
CoreAudio.lib
CoreAudioKit.lib
CoreBluetooth.lib
CoreData.lib
CoreGraphics.lib
CoreImage.lib
CoreLocation.lib
CoreMedia.lib
CoreMIDI.lib
CoreMotion.lib
CoreTelephony.lib
CoreText.lib
CoreVideo.lib
EventKit.lib
EventKitUI.lib
GameController.lib
GameKit.lib
GamePlayKit.lib
GLKit.lib
HealthKit.lib
HomeKit.lib
iAd.lib
ImageIO.lib
LocalAuthentication.lib
MapKit.lib
MediaAccessibility.lib
MediaPlayer.lib
MessageUI.lib
Metal.lib
OpenGLES.lib
QuartzCore.lib
QuickLook.lib
SafariServices.lib
Security.lib
Social.lib
StoreKit.lib
SystemConfiguration.lib
Twitter.lib
UIKit.lib
WebKit.lib
# WinObjC.Frameworks.Core
CFNetwork.lib
CoreFoundation.lib
Foundation.lib
MobileCoreServices.lib
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="NuGetizer CI Builds" value="https://ci.appveyor.com/nuget/nugetizer3000" />
</packageSources>
</configuration>
{
"dependencies": {
"WinObjC.Frameworks": "*",
"WinObjC.Language": "*",
"WinObjC.Packaging": "*"
},
"frameworks": {
"uap10.0": {
"imports": "native"
}
},
"runtimes": {
"win10-arm": {},
"win10-x86": {},
"win10-arm-aot": {},
"win10-x86-aot": {}
}
}
{
"dependencies": {
"WinObjC.Frameworks": "*",
"WinObjC.Language": "*"
},
"frameworks": {
"uap10.0": {
"imports": "native"
}
},
"runtimes": {
"win10-arm": {},
"win10-x86": {},
"win10-arm-aot": {},
"win10-x86-aot": {}
}
}
<?xml version="1.0"?>
<!-- This file contains Runtime Directives used by .NET Native. The defaults here are suitable for most developers. However, you can modify these parameters to modify the behavior of the .NET Native optimizer. Runtime Directives are documented at http://go.microsoft.com/fwlink/?LinkID=391919 To fully enable reflection for App1.MyClass and all of its public/private members <Type Name="App1.MyClass" Dynamic="Required All"/> To enable dynamic creation of the specific instantiation of AppClass<T> over System.Int32 <TypeInstantiation Name="App1.AppClass" Arguments="System.Int32" Activate="Required Public" /> Using the Namespace directive to apply reflection policy to all the types in a particular namespace <Namespace Name="DataClasses.ViewModels" Seralize="All" /> -->
<Directives xmlns="http://schemas.microsoft.com/netfx/2013/01/metadata"><Application>
<!-- An Assembly element with Name="*Application*" applies to all assemblies in the application package. The asterisks are not wildcards. -->
<Assembly Dynamic="Required All" Name="*Application*"/>
<!-- Add your application specific runtime directives here. -->
</Application>
</Directives>
{
"dependencies": {
"WinObjC.Packaging": "*"
},
"frameworks": {
"uap10.0": {
"imports": "native"
}
},
"runtimes": {
"win10-arm": {},
"win10-x86": {},
"win10-arm-aot": {},
"win10-x86-aot": {}
}
}
{
"dependencies": {
},
"frameworks": {
"uap10.0": {
"imports": "native"
}
},
"runtimes": {
"win10-arm": {},
"win10-x86": {},
"win10-arm-aot": {},
"win10-x86-aot": {}
}
}
{
"dependencies": {
"WinObjC.Packaging": "*"
},
"frameworks": {
"dotnet": {
"imports": [
"netstandard1.0",
"netstandard1.1",
"netstandard1.2",
"netstandard1.3",
"netstandard1.4",
"netstandard1.5",
"netstandard1.6",
"net20",
"net35",
"net40",
"net45",
"net452",
"net461",
"native",
"uap",
"monoandroid",
"xamarinios10"
]
}
},
"runtimes": {
"win10-arm": {},
"win10-x86": {},
"win10-arm-aot": {},
"win10-x86-aot": {}
}
}
# $projectname$ Readme
Update this readme with a description of your package.
This Readme will automatically be opened when your package is added to a project.
# WinObjC.Tools Readme
WinObjC.Tools package provides the commandline (via Chocolatey) entrypoint for the WinObjC project.
This includes the following:
- VSIX
- vsimporter
- winmd2objc
- objc2winmd
See https://github.com/Microsoft/WinObjC for more information
$ErrorActionPreference = 'Stop';
$packageName = 'WinObjC.tools'
$silentArgs = '' # "/s /S /q /Q /quiet /silent /SILENT /VERYSILENT" # try any of these to get the silent installer #msi is always /quiet
$validExitCodes = @(0) #please insert other valid exit codes here, exit codes for ms http://msdn.microsoft.com/en-us/library/aa368542(VS.85).aspx
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installPath = & vswhere -latest -property installationPath
if(!$installPath) {
throw "There was an error finding latest Visual Studio install location. Please make sure Visual Studio (2017 or later) is installed correctly."
}
$vsixInstaller = gci -File -Recurse -Filter vsixinstaller.exe -Path $installPath
Write-Host "Installing Objective-C Visual Studio 2017 Extension ... " -ForegroundColor Blue
$result = Install-Vsix -Installer $vsixInstaller.FullName -InstallFile "$toolsDir\objc-language-services-VS2017.vsix"
if($result -eq 2004) { #2004: Blocking Process (need to close VS)
throw "A process is blocking the installation of the Visual Studio Extension. Please close all Visual Studio instances and try again."
}
if($result -gt 0 -and $result -ne 1001) { #1001: Already installed
throw "There was an error installing the Objective-C Visual Studio 2017 Extension. The exit code returned was $result."
}
Write-Host "Downloading Nugetizer Visual Studio 2017 Extension ... " -ForegroundColor Blue
Get-ChocolateyWebFile -PackageName $packageName -FileFullPath "$toolsDir\nugetizer-2017.vsix" -Url 'http://bit.ly/nugetizer-2017'
Write-Host "Installing Nugetizer Visual Studio 2017 Extension ... " -ForegroundColor Blue
$result = Install-Vsix -Installer $vsixInstaller.FullName -InstallFile "$toolsDir\nugetizer-2017.vsix"
if($result -eq 2004) { #2004: Blocking Process (need to close VS)
throw "A process is blocking the installation of the Visual Studio Extension. Please close all Visual Studio instances and try again."
}
if($result -gt 0 -and $result -ne 1001) { #1001: Already installed
throw "There was an error installing the Objective-C Visual Studio 2017 Extension. The exit code returned was $result."
}
#NOTE: Ple$ErrorActionPreference = 'Stop';
$packageName = 'WinObjC.tools'
$silentArgs = '' # "/s /S /q /Q /quiet /silent /SILENT /VERYSILENT" # try any of these to get the silent installer #msi is always /quiet
$validExitCodes = @(0) #please insert other valid exit codes here, exit codes for ms http://msdn.microsoft.com/en-us/library/aa368542(VS.85).aspx
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installPath = & vswhere -latest -property installationPath
if($installPath) {
$vsixInstaller = gci -File -Recurse -Filter vsixinstaller.exe -Path $installPath
Write-Host "Uninstalling Objective-C Visual Studio 2017 Extension ... " -ForegroundColor Blue
$result = & $vsixInstaller.FullName /q /uninstall:VSIX..9c35fff1-f084-44c1-a38e-68c707163aa2
if($result -eq 2004) { #2004: Blocking Process (need to close VS)
throw "A process is blocking the uninstallation of the Visual Studio Extension. Please close all Visual Studio instances and try again."
}
if($result -gt 0 -and $result -ne 1002) { #1002: Not installed
throw "There was an error uninstalling the Objective-C Visual Studio 2017 Extension. The exit code returned was $result."
}
Write-Host "Uninstalling Nugetizer Visual Studio 2017 Extension ... " -ForegroundColor Blue
$result = & $vsixInstaller.FullName /q /uninstall:NuGet.Packaging
if($result -eq 2004) { #2004: Blocking Process (need to close VS)
throw "A process is blocking the uninstallation of the Visual Studio Extension. Please close all Visual Studio instances and try again."
}
if($result -gt 0 -and $result -ne 1002) { #1002: Not installed
throw "There was an error uninstalling the Objective-C Visual Studio 2017 Extension. The exit code returned was $result."
}
}
md5: 867488B794B5C054A014659B097EE721 | sha1: EF54A422A8A115CA5B9F04313D0CADE497B7A431 | sha256: EFC791367CEB922E153651DAEECA7BFB8E8D328202DC78393F9B15C92390FAEF | sha512: E964A09F974CDD3ACCF3C17F9E579ED69DE8FB849147177873104BD457EF4DDCA1CD739A13684396F579C4A96EC512BEF2510AC96D9E02E489DCCA7042A44CCE
md5: 641D9904E545F61E8908EE4FE34A5C2A | sha1: 1051417673D285FB7BD912716996C12EDDA71C20 | sha256: 147A4CF0D74903AD0C7392FF2B8E61ABF955C1BD641D8FB4ED37CE878A4E61B8 | sha512: 6D941FB78D1C8C43B634223984EF9BF39F1CFE32DB91D072A1F515EEFAC8262DD6EA7CCF41977F696B0BC8DC0DB5CFC3683AFCA1A1D0D7CBCC486C1B22AD0FD8
md5: 9663D1B597A44EB230D14E0FB56528F1 | sha1: 4194D288E8F11D84365561ABB1AD67EF8F64D71F | sha256: 35F55C88CC484F341E23C441C4FD11A7DE50A6158F64FE4C6FF7C90786E30A0F | sha512: C90EB560D898EF70806AFC726A31044FA3F21B747215D307C71F31DFE233313CF80C2A467FD60718D44CED6C6D1FE22B55186BEA060AEAD54952D7B0682D45F4
md5: 6626FD9189FF4C6C6B9B21658A553B21 | sha1: 5744E3AD4E00E672EABC651A9FA094326947EF4D | sha256: DF8A95DD131CBAD706B4DE7711DD6DBCAA4F16B41A10139D0C5CB32B16E0E0EF | sha512: 0976AFFC3FDC889DB14A63E5A8581A912AC74F5CA60EBCA51E2FB07257DF26438C23BE4F4FE5DF279AF35F6AA11771388F22EC0893CA66D4EEA7A40012C444E7
Log in or click on link to see number of positives.
- winobjc-tools.0.2.180221-dev-20180516000001.nupkg (41c47cf64555) - ## / 61
- libclang.dll (efc791367ceb) - ## / 65
- objc2winmd.exe (147a4cf0d749) - ## / 66
- vsimporter.exe (35f55c88cc48) - ## / 66
- winmd2objc.exe (df8a95dd131c) - ## / 66
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.
Copyright © Microsoft
-
- vswhere (≥ 1.0.50)
Ground Rules:
- This discussion is only about winobjc-tools and the winobjc-tools 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 winobjc-tools, 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.

