- #HOW DO YOU REPORT A PROBLEM TO MICROSOFT OFFICE UPDATES HOW TO#
- #HOW DO YOU REPORT A PROBLEM TO MICROSOFT OFFICE UPDATES FULL VERSION#
- #HOW DO YOU REPORT A PROBLEM TO MICROSOFT OFFICE UPDATES CODE#
In the developer command prompt console window, enter the command cl /Bv. For more information, see Developer command prompt shortcuts. For example, if you build by using Visual Studio 2017 on 圆4 for 圆4 targets, choose 圆4 Native Tools Command Prompt for VS 2017.
Open the Developer Command Prompt that matches the Visual Studio version and configuration architecture used to build your project.
#HOW DO YOU REPORT A PROBLEM TO MICROSOFT OFFICE UPDATES FULL VERSION#
To report the full version of your compiler If we can reproduce the problem, this information also gives us a starting point to investigate which other versions of the toolset have the same problem. That's so we can test your repro against the same toolset on our machines. We need the full version information and the target architecture of the toolset that causes the problem.
#HOW DO YOU REPORT A PROBLEM TO MICROSOFT OFFICE UPDATES HOW TO#
Read on to learn more about the specific information we need and where you can find it, and how to create a good repro.
#HOW DO YOU REPORT A PROBLEM TO MICROSOFT OFFICE UPDATES CODE#
The full cl.exe command line used to build your code.Ī detailed description of the problem you found.Ī repro: a complete, simplified, self-contained source code example that demonstrates the problem. The full version information of the toolset you're using. The better your report is, the more effectively we can recreate and diagnose the problem.Īt a minimum, your report should contain: It's important to create a high-quality report, because it's difficult for us to reproduce the problem you found without complete information. Thank you for helping us improve Microsoft C++! How to prepare your report Your reports are important to us and to other developers like you. We describe how to generate a repro for the kind of issue you've found, and how to send your report to the product team. In the sections below, you'll read about what makes a good report. It helps us determine whether it affects other versions of the compiler, and to diagnose its cause. This information lets us quickly verify that the problem exists in our code and isn't local to your environment. And it should include a repro, a complete test case we can use to reproduce the problem on our own machines. It should have all the details about how you build your program. The best way to let us know about a problem is to send us a report that includes a description of the problem you've discovered. When the issue is in our documentation, we want to know about that, too. If you find problems in the Microsoft C++ compiler (MSVC), the linker, or other tools and libraries, we want to know about them.
0 kommentar(er)
