![]() ![]() Optionally, select Monitor warnings to add warnings to the analysis.Ĭlick Save in the Settings dialog to apply the modifications and let JetBrains Rider choose where to save them, or save the modifications to a specific settings layer using the Save To list. Optionally, select Enable computationally expensive inspections, which turns on the data-flow analysis and brings additional inspections, for example, to calculate nullability. Optionally, you can enable or disable warnings in solution-wide analysis. On the Editor | Inspection Settings page of JetBrains Rider settings Control+Alt+S, make sure that the Enable code analysis checkbox is selected, and click Enable solution-wide analysis. If you have a very large solution and experience performance problems, you may want to disable solution-wide analysis. Solution-wide analysis can take some time for the initial processing of the solution but once it is complete, it works in the background and does not consume much resources. Note that solution-wide analysis doesn't monitor errors in projects that are not built in the current solution configuration. When solution-wide analysis is enabled, issues detected by the solution-wide inspections are highlighted in the opened files in the same way as other issues, and they also appear in the Inspection Results window when you run code inspection in specific scope. Solution-wide code inspections, which help find issues that can only be detected by analysing the whole solution (unused public types and members, unassigned public fields, suspicious type conversions and so on). You can choose to monitor only errors or both errors and warnings in solution-wide analysis. You can jump to the next error in solution and find out that someone uses this member from another project in your solution. Then, you switch on solution-wide analysis, and actually there are errors. At this stage, JetBrains Rider finds no errors in the current file. ![]() ![]() If you delete a public member or change its visibility, the code in the current file can still be correct, but what if this member is used somewhere else in the solution? For example, suppose that you changed the visibility of a member from public to internal, assuming that it was only used inside the current project. You do not have to open every file to make sure that your solution does not contain errors/warnings. This feature works together with the design-time code inspection and brings two advantages: Solution-wide errors/warnings monitor, which lets you constantly keep track of all errors/warnings in your solution: both compiler errors/warnings and errors/warnings detected by JetBrains Rider’s own inspections. JetBrains Rider's solution-wide analysis enables two related but distinct features: Solution-wide analysis only works in C# and Visual Basic. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |