roslyn-code-analysis

问题 I'm evaluating an script using the CSharpScript.EvaluatyAsync<T> method and passing some C# code. I can easily see the line number of errors when there is a parsing issue, e.g. a syntax error, but when there is a runtime exception all I get is an AggregateException wrapping my exception ( NullReferenceException ) in this case, but there is no clue of how to get the line number for me (3 in this example below). Console.WriteLine(CSharpScript.EvaluateAsync<int>( @"string s = null; // some

问题 I'm trying to invent good way to pack my Roslyn analyzer projects into NuGet. It requires specific NuGet package structure with .dll put into \analyzer\ , not \lib\ . For this to work, I have to call nuget pack <name>.nuspec , not nuget pack <name>.csproj . But if I use nuspec , than $version$ tag gets ignored. Seems that my only option is to manually update version in .nuspec on every rebuild. What is correct and right way to accomplish this? 回答1: I just had the same problem. I don't like

问题 I have a Visual Studio 2015 professional (in Windows 7) and Visual Studio 2015 community (in Windows 10), both of have latest update 1 installed. And I have both of them opened the exactly same solution. Both tools also have Refactoring Essentials for Visual Studio plug-in installed. In professional edition I can clearly see live code analyzer actually works: You can see the wave lines under files, folders, projects and solution. When I hover mouse over then I can preview the issue before I

问题 I am trying to analyse a solution with Roslyn, with MSBuildWorkspace. The solution is a new solution, with 2 class library projects in them, one referencing the other. They are created in Visual Studio 2017, .Net 4.6.2. When I open the solution, I receive two generic errors in workspace.Diagnostics, both are : Msbuild failed when processing the file ' PathToProject ' There is nothing more in the diagnostics or output window, to indicate WHY it failed to process the project file. The code for

问题 I'm trying to determine if there's a programmatic way to check for possible DivideByZeroException in my codebase. My codebase includes a series of relatively simple to relatively complex formulas, approximately 1500 of them (and growing). When new formulas are written, care must be taken to ensure that division is done safely to avoid exceptions during processing of these formulas. E.g. decimal val1 = 1.1m; decimal val2 = 0m; var res = val1/val2; //bad var res = val2 == 0 ? 0 : val1/val2; /

问题 In the implementation of my analyzer I am in the AnalyzeSymbol method: public override void Initialize(AnalysisContext context) { context.RegisterSymbolAction(AnalyzeSymbol, SymbolKind.Method); } private static void AnalyzeSymbol(SymbolAnalysisContext context) { // here I look through the syntax of the method body in order to find invocations. var methodSymbol = context.Symbol as IMethodSymbol; var location = methodSymbol.Locations.FirstOrDefault(); var methodNode = location.SourceTree

问题 I'm investigating the use of the Roslyn compiler within a Visual Studio Extension (VSIX) that uses the VisualStudioWorkspace to update existing code. Having spent the last few days reading up on this, there seem to be several ways to achieve this....I'm just not sure which is the best approach for me. Okay, so let's assume that the User has their solution open in Visual Studio 2015. They click on my Extension and (via a form) they tell me that they want to add the following method definition

问题 Our team uses the Code Analysis feature with a custom ruleset to cause our build to fail if we forget to do things like null checks on method arguments. However, now as we create a new .NET Core project, it doesn't look like Code Analysis is a feature of these new projects. There is no UI for it in the Project Properties area, and adding a custom ruleset to the project as recommended here only appears to affect StyleCop Analyzers (the SAxxxx rules). Is there any way to enable Code Analysis (

问题 I have 2 test projects in solution. First project ("VDoc") declare VDocQuery type. Second project ("VDocQueryTest" ) calls VDocQuery constructor. I get 2 VDocQuery's ITypeSymbol's (one from each project), compare it, but get false result. Steps: 1. Get first ITypeSymbol (from VDoc project with SemanticModel.LookupNamespacesAndTypes() method). 2. Get second ITypeSymbol from VDocQueryTest project (from ObjectCreationExpressionSyntax.GetTypeInfo().Type) 3. Compare it with ITypeSymbol.Equals

问题 I intend to use the new Roslyn Code Analysis API with an MVC 6 project. However, when I run this code: string pathToSolution = @"..\..\..\WebApplicationComplex.sln"; const string projectName = "RoslynWebAPIProject"; MSBuildWorkspace workspace = MSBuildWorkspace.Create(); Solution solutionToAnalyze = workspace.OpenSolutionAsync(pathToSolution).Result; Project sampleProjectToAnalyze = solutionToAnalyze.Projects.Where((proj) => proj.Name == projectName).FirstOrDefault(); Compilation