Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Joseph Musser
    @jnm2
    The alternative would be to add <EnableDefaultNoneItems>false</EnableDefaultNoneItems> and add each None file that you actually want in the project using individual <None Include lines (can use globs)
    Or you could do
      <ItemGroup>
        <None Remove="Images\**\*" />
        <EmbeddedResource Include="Images\**\*" />
      </ItemGroup>
    Johan Larsson
    @JohanLarsson
    nice, thanks
    Hussam Al-Tayeb
    @hussamT
    hello. i am compiling llvm using cmake from command line. it correctly detected VS 2019 C++ compiler. the source code is on drive D:\, an hdd. but it is writing temporary object files to drive C:\, my ssd.
    Would anyone possibly know how to change this behavior?
    is this controlled by VS C++ compiler?
    As always, I'm online all the time. So if anyone sees my question tomorrow or any day, and you happen to know the answer, feel free to let me know. I'm in no rush at all.
    Diogo Martinho
    @DiogoMartinh0
    is it possible to still install the last preview for vs19, v16.4? the 16.5 preview breaks my xamarin debugger
    calbertrov
    @calbertrov
    How can someone open their.pbix file in VS to Power BI Desktop? When in VS, I chose my.pbix then "Open with" a window open up and ask to chose a program to open you file. I select Power BI Desktop and ok. Then I receive a message that says "The file cannot be open with the selected editor. Please chose another editor". Have anyone run into this issue?
    Hussam Al-Tayeb
    @hussamT
    16.4 will be supported after 16.5 is released?
    RaviU
    @Raviuppa
    @DiogoMartinh0 unfortunately, previous preview builds are not available for download and only the released builds. Can you submit your Xamarin Debugger issue with 16.5 preview through VS Feedback so that we can investigate and address it appropriately?
    RaviU
    @Raviuppa
    @hussamT , yes, 16.4 is supported after the release of 16.5. 16.4 is the Service baseline. For more information on VS 2019 Product Life Cycle and Servicing, please refer this doc https://docs.microsoft.com/en-us/visualstudio/releases/2019/servicing
    Hussam Al-Tayeb
    @hussamT
    @Raviuppa I am reading it. Thank you.
    Hussam Al-Tayeb
    @hussamT
    @Raviuppa Just so I understand correctly, once 16.5 is installed, the VS installer will give me the option to upgrade to 16.5 or install further 16.4 updates?
    err is released
    not is installed
    sorry.
    Hussam Al-Tayeb
    @hussamT
    I also noticed Python 3.7.6 was released. Will Visual Studio offer this at some point as an update?
    Hugh Gleaves
    @Korporal
    I have a question. Given a folder tree, containing numerous arbitrary folders and within them VS solutions/projects , then given any filename in the folder tree can we determine a list of all projects that depend on that file? for example some C# source file.
    RaviU
    @Raviuppa
    @hussamT No worries. VS 2019 is in place update of its release channel (Release/Preview/SKU such as Community, Pro and Enterprise). For eg, if you have just 16.4 Pro installed then this 16.4 Pro can be upgraded to 16.5 Pro. You can not have both 16.4 Pro and 16.5 Pro as sxs. However, you can have sxs if their release channels/SKus are different. Such if you have 16.4 Pro installed and wanted to install 16.5 Enterprise then both 16.4 Pro and 16.5 Enterprise can exist sxs. Let us know if any questions.
    Hussam Al-Tayeb
    @hussamT
    I have 16.4.2 community edition. So, it will continue to offer me 16.4.x updates after 16.5 is installed till I get a new installer and use that to install 16.5 community (replacing 16.4 community) or install Pro for example?
    err after 16.5 is released
    let me write that again:
    I have 16.4.2 community edition. So, it will continue to offer me 16.4.x updates after 16.5 is released till I get a new installer and use that to install 16.5 community (replacing 16.4 community) or install Pro for example?
    RaviU
    @Raviuppa
    @hussamT if you are on 16.4.2 Community and want to remain on 16.4.x release then yes you will continue to be offered 16.4 Servicing updates till we release next servicing Base line update (haven't finalized on which build it would be) or till you upgrade to 16.5 Community (16.4.x community can be upgraded to 16.5 Community).
    Hussam Al-Tayeb
    @hussamT
    @Raviuppa Sounds perfect. Thank you!
    I give up after 2 week searching for solutions, now I unintall any visual studio item, then install agan but hte problem come again
    Thad House
    @ThadHouse

    https://docs.microsoft.com/en-us/visualstudio/releases/2019/history#installing-an-earlier-release

    Anyone know where to find 16.3 community? 16.4 is completely broken, and we need to roll back.

    Veselin Ivanov
    @vvatkov
    Guys, is there a way to customize the names of the items in the XAML designer toolbox in Visual Studio 2019? It seems that when the NuGet package approach is used to register the controls in the toolbox, the names of the items contain the namespace of the control which is redundant in our case. For example MyCustomControl (MyNamespace). Is there a way to have just MyCustomControl as a toolbox item name?
    Christine Ruana
    @christineruana

    @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.

    RaviU
    @Raviuppa
    @ThadHouse Unfortunately, the previous versions of Community editions for VS 2019 are not available for download. Can you open a ticket for the issue you are facing with 16.4 via vs-feedback so that we can take a look at it? Also, were you able to replicate the 16.4 issue with 16.5 community Preview edition? You can download 16.5 Preview from https://visualstudio.microsoft.com/vs/preview/.
    RaviU
    @Raviuppa
    @nyongrand , sorry to hear that you are running into the solution load issue. As noted in the DevCom bug notes, can you upload your VS installation logs to the same bug. Reason for installation logs request is, we would like to investigate for any package/component installation related issue that may be the cause of solution load failure. Is it happening with any specific type of solution or happening with any type of solution?
    Thad House
    @ThadHouse

    @christineruana It's this issue
    https://developercommunity.visualstudio.com/content/problem/847490/msvc-codegen-error-vector-reverse-iterator-x64-c17.html?childToView=872391#comment-872391

    It's reported, but apparently a code gen bug causing runtime crashes isn't important.

    And its breaking Azure for us, so our CI has been dead for over a month. Making us seriously think about dropping Azure for CI. Its breaking a ton of C++ builds, even in popular libraries, and its just DOA with no workaround in some cases.
    RaviU
    @Raviuppa
    @ThadHouse , thank you for providing addition information. Apologies for the inconvenience the issue caused in your environment. It has been fixed in the upcoming VS 2019 Update 5. It is currently under preview mode. Did you test the scenario with the current VS 2019 U5 Preview? You can download it from https://visualstudio.microsoft.com/vs/preview/.
    Thad House
    @ThadHouse
    We can't install preview on Azure. So that doesn't help. They really should just do a patch release to 16.4, especially since 16.4 is a larger longer term release.
    If it was properly patched, azure could have it fixed in a day, rather then having CI broken for almost 3 months. It's a bit insane that they'll do nothing about the issue with their own service.
    RachelSchaw
    @RachelSchaw
    @ThadHouse Hi Thad, to best forum for reporting problems with Visual Studio is https://developercommunity.visualstudio.com/. While there are some folks from Microsoft part of this room, our engineering team actively monitors and responds to issues reported through the Visual Studio Developer Community. https://developercommunity.visualstudio.com/
    RaviU
    @Raviuppa
    @ThadHouse , Understood and we will be addressing this issue in 16.4 as well and the fix will be part of upcoming Servicing update for 16.4. We do not have exact release date but will be released soon.
    CJRyan
    @charlesryan1
    @RachelSchaw Responses telling us that without enough up votes or activity, by others with the same problem, the reported bugs will not be investigated/worked on is not even close to being useful. https://developercommunity.visualstudio.com/ is nothing but a containment site for customers with issues the VS team does not want to address.
    RachelSchaw
    @RachelSchaw
    @charlesryan1 Thank you for your feedback. I am on the Visual Studio team and can attest to the fact that as part of our release processes we do have metrics around meeting a specific SLA for responding to and resolving to customer feedback submitted through the Visual Studio Developer Community. If you find that Gitter is a more effective way to report issues, I would love to learn more. But, I did want to set expectations that we do not have any formal SLA around tracking and responding to issues in this feedback channel.
    CJRyan
    @charlesryan1
    @RachelSchaw I did not mean to suggest this channel was a preferred way to report issues, I simply meant to state that the VSDC site has proven pretty low value as well. Example: "Error: DataTip unavailable = error CS0726: ':' is not a valid format specifier" received this response "Visual Studio Feedback System on 12/5/2019
    I have detected that for the last 35 days, this issue didn't have much product team activity and a very small amount of new votes or comments. Based on this, its severity, and affected area, it’s my experience that this issue is very unlikely to be fixed."
    Andy Wilson
    @atwilso

    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.

    RaviU
    @Raviuppa
    @atwilso , Currently Windows Containers do not have the support of Interactive User Interface so no way of Installing Visual Studio and reporting a problem through VS IDE or through VS Setup UI Windows. You can install Build Tools and please refer this doc for additional details. https://docs.microsoft.com/en-us/visualstudio/install/build-tools-container?view=vs-2019.
    Andy Wilson
    @atwilso

    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.

    RaviU
    @Raviuppa
    @atwilso Thank you for the details. Yes, the installation logs would be able to identify the probable cause of the issue. Unfortunately due to lack of UI support on the Docker containers, there is no way of reporting the issue through Feedback channel from within the Docker container. Can you please submit a ticket from a regular machine through VS IDE and attach the logs to it along with the issue description?
    Andy Wilson
    @atwilso
    Done. Let me know if you need the issue number.
    RaviU
    @Raviuppa
    @RachelSchaw , today we have released the 3rd Servicing Update for Visual Studio 2019 Update 4 which has the fix for the MSVC toolset Codegen issue. You can download the update from this release notes page and as well VSCOM download page. https://docs.microsoft.com/en-us/visualstudio/releases/2019/release-notes#16.4.3. Please test it and provide us the feedback if any.
    trsh
    @trsh
    Hey visual studio Guru's. Help me with this issue https://stackoverflow.com/questions/59845196/cant-install-or-uninstall-visual-studio-2017 . Is urgent! :(