<ItemGroup> <None Remove="Images\**\*" /> <EmbeddedResource Include="Images\**\*" /> </ItemGroup>
Anyone know where to find 16.3 community? 16.4 is completely broken, and we need to roll back.
@ThadHouse - what's the problem with 16.4? Have you reported the issue on Developer Community? If something is completely blocking or broken, we try to address it pretty immediately... Also, per our Support Policy (https://docs.microsoft.com/en-us/visualstudio/releases/2019/servicing) we only provide links to prior versions of Enterprise, Professional and Build Tools.
If/when you do report it on Dev Community, reply back here with a link and I'll make sure it gets attention.
It's reported, but apparently a code gen bug causing runtime crashes isn't important.
Hi! I'm having trouble installing VS 16 into a Docker container and I'm trying to figure out how to report the problem. The directions on developercommunity.visualstudio.com to "use the in-IDE Report a Problem tool" are inapplicable because I'm working inside a Docker container -- there is no IDE.
It's quite possible that in my general frustration and stomping around I've missed something obvious. I would be grateful for a pointer to the right way to report this.
To be more specific: I am following the instructions on https://docs.microsoft.com/en-us/visualstudio/install/advanced-build-tools-container?view=vs-2019, slightly modified, in an attempt to install just the Visual C++ build tools. I can do this (mostly) if I go for an offline install created with 'vs_buildtools.exe --layout', but I run into problems trying to download on demand because I don't know how to communicate proxy settings to the installer inside a container. Ordinarily it would pull the proxy settings from Internet Explorer, but there is no IE installed inside the container. There is no documentation telling me how else to communicate these settings to vs_buildtools.exe.
I have a bundle of logs generated by vscollect.exe. I have the Dockerfile in question. I have other evidence supporting the idea that it's a proxy problem. What I need to know is where to create a problem report. The options presented on the "report a problem" page on https://developercommunity.visualstudio.com/content/problem/post.html?space=8 are not usable here: both of them rely on reporting problems from within a GUI (the installer or the IDE), neither of which are available inside a container.