Create unhandled exception message (#7392)

Create unhandled exception message

.github/ISSUE_TEMPLATE/01_bugreport.md

@@ -20,6 +20,12 @@ labels: bug, needs-triage
 * Your zipped project.
 * IDE / CLI steps to create the project and reproduce the behaviour.
 * Your command line invocation
+
+If providing steps to reproduce the issue proves difficult, consider attaching a binlog:
+[Details on sharing binary logs](https://aka.ms/msbuild/binlog)
+[More information on binary logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Binary-Log.md)
+NOTE: Binary logs capture environment information. Ensure it does not include any information you don't want to be public before you attach one.
+If you want to share one just with Microsoft, you can [report a problem through Visual Studio](https://developercommunity.visualstudio.com/report) and share it privately with Microsoft.
 -->
 
 ### Expected Behavior
@@ -46,13 +52,3 @@ labels: bug, needs-triage
 * Post any other relevant configuration settings here.
 *   OS, architecture, etc.
 -->
-
-### Attach a binlog
-<!--
-* If providing us a project that reproduces the issue proves difficult, consider including a binlog.
-* Click [here](https://aka.ms/msbuild/binlog) for details on sharing binary logs.
-* Click [here](https://github.com/microsoft/msbuild/blob/master/documentation/wiki/Binary-Log.md) for more information on binary logs.
-    NOTE: Binlogs can contain sensitive information. Don't attach anything you don't want to be public.
-
-*   To view the contents of the binlogs yourself, you may wish to use a tool like https://msbuildlog.com/.
--->

.github/ISSUE_TEMPLATE/02_performanceissue.md

@@ -20,6 +20,12 @@ Include as much of the following if possible:
 * Your zipped project.
 * IDE / CLI steps to create the project and reproduce the behaviour.
 * Your command line invocation
+
+If providing steps to reproduce the issue proves difficult, consider attaching a binlog:
+[Details on sharing binary logs](https://aka.ms/msbuild/binlog)
+[More information on binary logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Binary-Log.md)
+NOTE: Binary logs capture environment information. Ensure it does not include any information you don't want to be public before you attach one.
+If you want to share one just with Microsoft, you can [report a problem through Visual Studio](https://developercommunity.visualstudio.com/report) and share it privately with Microsoft.
 -->
 
 ### Data
@@ -57,13 +63,3 @@ Post any other relevant configuration settings here.
 *   What version of MSBuild or VS were you using before the regression?
 *   What version of MSBuild or VS are you on now that you discovered the regression?
 -->
-
-### Attach a binlog
-<!--
-* If providing us a project that reproduces the issue proves difficult, consider including a binlog.
-* Click [here](https://aka.ms/msbuild/binlog) for details on sharing binary logs.
-* Click [here](https://github.com/microsoft/msbuild/blob/master/documentation/wiki/Binary-Log.md) for more information on binary logs.
-    NOTE: Binlogs can contain sensitive information. Don't attach anything you don't want to be public.
-
-*   To view the contents of the binlogs yourself, you may wish to use a tool like https://msbuildlog.com/.
--->

.github/ISSUE_TEMPLATE/03_mybuildisbroken.md

@@ -28,6 +28,12 @@ labels: needs-triage
 * Your zipped project.
 * IDE / CLI steps to create the project and reproduce the behaviour.
 * Your command line invocation
+
+If providing steps to reproduce the issue proves difficult, consider attaching a binlog:
+[Details on sharing binary logs](https://aka.ms/msbuild/binlog)
+[More information on binary logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Binary-Log.md)
+NOTE: Binary logs capture environment information. Ensure it does not include any information you don't want to be public before you attach one.
+If you want to share one just with Microsoft, you can [report a problem through Visual Studio](https://developercommunity.visualstudio.com/report) and share it privately with Microsoft.
 -->
 
 ### Expected Behavior

.github/ISSUE_TEMPLATE/05_unhandledexception.md

@@ -0,0 +1,34 @@
+---
+name: 😱 Unhandled Exception
+about: Reporting holes in our bug reporting system
+title: ''
+labels: bug
+---
+
+<!-- This is a template that helps us provide quicker feedback.
+Use any relevant sections and delete what you don't need. -->
+
+### Issue Description
+<!--
+Include a stack trace if possible.
+If you do not see one, try looking in your temp folder for the most recently created file named
+MSBuild_pid-{pid}_{guid}.failure.txt
+-->
+
+### Steps to Reproduce
+<!--
+* Include as many of these as possible:
+* A minimal sample project that reproduces the issue
+* IDE or CLI steps that create the project and reproduce the issue
+* Your command line invocation
+-->
+
+### Analysis
+<!-- If you think you know what the problem is, please include that here. -->
+
+### System Configuration
+<!--
+What version of MSBuild are you using? (`msbuild --version` from a developer command prompt)
+What version of the tool invoking MSBuild are you using? (`dotnet --version`, accessing it from the Visual Studio Installer, etc.)
+OS version (or at least Windows/Mac/Linux), architecture, etc.
+-->