You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
about: Report an issue about something that is not working in the new Razor tooling
4
+
labels: area-razor.tooling, feature-razor.vs
5
+
---
6
+
7
+
<!--
8
+
9
+
More information on our issue management policies can be found here: https://aka.ms/aspnet/issue-policies
10
+
11
+
Please keep in mind that the GitHub issue tracker is not intended as a general support forum, but for reporting **non-security** bugs and feature requests.
12
+
13
+
If you believe you have an issue that affects the SECURITY of the platform, please do NOT create an issue and instead email your issue details to [email protected]. Your report may be eligible for our [bug bounty](https://www.microsoft.com/en-us/msrc/bounty-dot-net-core) but ONLY if it is reported through email.
14
+
For other types of questions, consider using [StackOverflow](https://stackoverflow.com).
15
+
16
+
-->
17
+
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 -->
19
+
20
+
### Describe the bug
21
+
A clear and concise description of what the bug is.
22
+
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
34
+
35
+
Please collect the data below before reporting your issue to aid us in diagnosing the root cause.
36
+
37
+
#### Activity log
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.
39
+
40
+
#### Razor Language Server Client log
41
+
<!-- In Visual Studio's `Output` window, the drop-down contains a `Razor Language Server Client` item. Include that below. -->
42
+
<details>
43
+
<summary>Razor Language Server Client Log Output</summary>
44
+
45
+
Paste log output here
46
+
47
+
</details>
48
+
49
+
#### HTML Language Server Client log
50
+
<!-- In Visual Studio's `Output` window, the drop-down contains a `HtmlyLanguageClient` item. Include that below. -->
51
+
<details>
52
+
<summary>HTML Language Server Client Log Output</summary>
53
+
54
+
Paste log output here
55
+
56
+
</details>
57
+
58
+
### Further technical details
59
+
- 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.
@@ -22,7 +38,8 @@ Building ASP.NET Core on Windows requires:
22
38
However, any Visual Studio 2019 instance that meets the requirements should be fine. See [global.json](/global.json)
23
39
and [eng/scripts/vs.json](/eng/scripts/vs.json) for those requirements. By default, the script will install Visual Studio Enterprise Edition, however you can use a different edition by passing the `-Edition` flag.
24
40
* Git. <https://git-scm.org>
25
-
* NodeJS. LTS version of 10.14.2 or newer <https://nodejs.org>
41
+
* NodeJS. LTS version of 10.14.2 or newer <https://nodejs.org>.
**NOTE** some ISPs have been know to use web filtering software that has caused issues with git repository cloning, if you experience issues cloning this repo please review <https://help.github.com/en/github/authenticating-to-github/using-ssh-over-the-https-port>
72
73
73
74
## Building in Visual Studio
@@ -86,6 +87,9 @@ Before opening our .sln/.slnf files in Visual Studio or VS Code, you need to per
86
87
> :bulb: Pro tip: you will also want to run this command after pulling large sets of changes. On the master
87
88
> branch, we regularly update the versions of .NET Core SDK required to build the repo.
88
89
> You will need to restart Visual Studio every time we update the .NET Core SDK.
90
+
> To allow executing the setup script, you may need to update the execution policy on your machine.
91
+
You can do so by running the `Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser` command
92
+
in PowerShell. For more information on execution policies, you can read the [execution policy docs](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy).
89
93
90
94
2. Use the `startvs.cmd` script to open Visual Studio .sln/.slnf files. This script first sets the required
0 commit comments