Outputs the modified report onto STDOUT in the format specified in the task's pattern.Reads and parses this temporary report in order to collate metadata about each issue into a more suitable format for output to VS Code.Runs InspectCode.exe for the solution you defined and outputs the report as a temporary XML file in the root of your workspace.This is not required if the PATH was set up as explained above. InspectCode.exe is an optional argument (default value is InspectCode.exe) that defines where the package can find ReSharper's executable.MySolution.sln is a required argument defining the path to the solution to inspect relative to the root of your workspace.Node node_modules\\resharper-vs-code-bridge MySolution.sln InspectCode.exe ![]() The package takes one required argument and another optional one. The task itself simply runs the resharper-vs-code-bridge NodeJS package, listens for output on STDOUT and then parses it with the provided regex pattern in order to extract code inspection issues and pass them to the IDE. Run the inspect task from the Tasks -> Run Task."node_modules\\resharper-vs-code-bridge", Note: This must be added to either the system's PATH or the PATH of the user that runs your VS Code tasks Extract the tools to a known location and add that directory to your system's PATH variable.Download the ReSharper Command Line Tools from.Install as a dev dependency: npm i -D resharper-vs-code-bridge. ![]() This is an extremely shabby attempt at getting ReSharper's inspections into Visual Studio Code now that JetBrains have expressed no interest in bringing ReSharper across officially.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |