Skip to content

Commit 491ad53

Browse files
author
N. Taylor Mullen
authored
Simplify Razor bug reports. (#31033)
* Simplify Razor bug reports. - We now have better mechanisms for capturing information so no need to scare users off. * Address code review feedback
1 parent 14af9d9 commit 491ad53

File tree

1 file changed

+10
-28
lines changed

1 file changed

+10
-28
lines changed

.github/ISSUE_TEMPLATE/30_razor_tooling.md

Lines changed: 10 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -15,38 +15,20 @@ For other types of questions, consider using [StackOverflow](https://stackoverfl
1515
1616
-->
1717

18-
<!-- NOTE: This issue template is meant specifically to be used for issues with the new experimental Razor tooling experience provided in Visual Studio's Preview Feature pane -->
18+
### Visual Studio Code
1919

20-
### Describe the bug
21-
A clear and concise description of what the bug is.
20+
Select the `Razor: Report a Razor Issue` command in [VSCode Command Palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette) and follow the instructions to gather information necessary for us to investigate. Paste below:
2221

23-
### To Reproduce
24-
<!--
25-
We ❤ code! Point us to a minimalistic repro project hosted in a GitHub repo.
26-
For a repro project, create a new ASP.NET Core project using the template of your your choice, apply the minimum required code to result in the issue you're observing.
27-
28-
We will close this issue if:
29-
- the repro project you share with us is complex. We can't investigate custom projects, so don't point us to such, please.
30-
- if we will not be able to repro the behavior you're reporting
31-
-->
32-
33-
### Logs & Exceptions
22+
---
23+
Paste Content Here
24+
---
3425

35-
Please collect the data below before reporting your issue to aid us in diagnosing the root cause.
26+
### Visual Studio Windows
3627

37-
#### Activity log (only needed if VS crashes)
38-
[Here](https://docs.microsoft.com/en-us/visualstudio/extensibility/how-to-use-the-activity-log?view=vs-2019#to-examine-the-activity-log) are the instructions on how to generate/acquire one. Note that GitHub does not generally allow .xml files to be uploaded with issues.
28+
You may file an issue here but please create a Visual Studio bug first and link here as it will capture all necessary logs for us to investigate further.
3929

40-
#### Language Server logs
41-
1. Run Visual Studio with the [/Log](https://docs.microsoft.com/en-us/visualstudio/ide/reference/log-devenv-exe?view=vs-2019) command line switch
42-
2. Reproduce the issue
43-
3. Provide the logs located at `%Temp%\VisualStudio\LSP`
30+
How to report a problem in Visual Studio: https://docs.microsoft.com/en-us/visualstudio/ide/how-to-report-a-problem-with-visual-studio
4431

45-
### Further technical details
46-
- VS version (Help => About Microsoft Visual Studio, i.e. 16.8.0 Preview 1 30313.27...). If in Codespaces there will be two versions (server and client), please provide both.
47-
- Scenario (Local, LiveShare, Codespaces)
32+
### Visual Studio Mac
4833

49-
### Pre-requisite checklist
50-
- [ ] Steps to reproduce the issue
51-
- [ ] Razor Language Server client logs included.
52-
- [ ] HTML Language Server client logs included
34+
Please try and provide as much information as possible so we can try and resolve the issue.

0 commit comments

Comments
 (0)