-
Notifications
You must be signed in to change notification settings - Fork 52
Issues: jberezanski/ChocolateyPackages
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
The installation of visualstudio2022buildtools failed (installer exit code: 5003)
#154
opened Sep 2, 2024 by
Lyvin-zhang
.net framework 4.8.1 choco installer has a version conflict even though they match
#153
opened Jun 12, 2024 by
Pxtl
What is the visualstudio2022 workload name for Microsoft.NetCore.Component.SDK?
#150
opened May 30, 2024 by
TraGicCode
visualstudio2022buildtools Fails to Install - Version Mismatch?
#134
opened Aug 22, 2022 by
eXpl0it3r
Add/modify functions to use the --config paramter of vs_installer
#130
opened Jun 14, 2022 by
mkr-schleupen
Choco install
visualstudio2017-workload-vctools
no longer works on windows-2019
#97
opened Mar 11, 2021 by
collinpeters
chocolatey-dotnetfx.extension add support for file to allow internalization
#90
opened Jun 24, 2020 by
TheCakeIsNaOH
Create a package for installing VSSetup and make VS packages depend on it
#76
opened Oct 1, 2019 by
jberezanski
VS: harmless warning from VSSetup when VS is not installed yet
#75
opened Oct 1, 2019 by
jberezanski
VS: duplicate and misspelled messages after update with reboot required
#72
opened Sep 9, 2019 by
jberezanski
visualstudio2017: install the exact VS version as the package version
#11
opened Apr 19, 2017 by
jberezanski
visualstudio2017: if VS Installer needs upgrade, --passive does not work
#8
opened Apr 19, 2017 by
jberezanski
visualstudio2017: if VS Installer needs upgrade, --wait does not work
#7
opened Apr 19, 2017 by
jberezanski
ProTip!
no:milestone will show everything without a milestone.