Profile Picture

VS2015

Posted By Roman Sallin 5 Years Ago
Author
Message
Roman Sallin
Problem Posted 5 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: Forum Members
Last Active: 5 Years Ago
Posts: 3, Visits: 19
Hi
In VS2015 (with Update 1): as soon as I drag and drop the NRichTextViewWithRibbon on a form (in a WinForms project, .NET 4.5), the compiler gives the following warning:
Severity    Code    Description    Project    File    Line    Suppression State
Warning    AD0001    Analyzer 'Microsoft.CodeAnalysis.VisualBasic.CodeFixes.SimplifyTypeNames.VisualBasicSimplifyTypeNamesDiagnosticAnalyzer' threw an exception of type 'System.ArgumentNullException' with message 'Value cannot be null.
Parameter name: source'.    NOVText        1    Active


Is OpenVision fully compatible to VS2015?
Best regards
Roman




Nevron Support
Posted 5 Years Ago
View Quick Profile
Supreme Being

Supreme Being (4,093 reputation)Supreme Being (4,093 reputation)Supreme Being (4,093 reputation)Supreme Being (4,093 reputation)Supreme Being (4,093 reputation)Supreme Being (4,093 reputation)Supreme Being (4,093 reputation)Supreme Being (4,093 reputation)Supreme Being (4,093 reputation)

Group: Forum Members
Last Active: 6 hours ago
Posts: 2,965, Visits: 3,372
Hello Roman,
Nevron Open Vision provides support for Visual Studio 2015.

We were able to reproduce the warning message in a VB.NET project – it appears when you run the Code Analysis. However, your project (and the NOV Example Solution) should be compiling without problems. The Code Analysis may be configured to run by default within your VS. You can check the configuration for the VS Code Analysis.

We got a suggestion from the built-in code analyzer to simplify the type name. Since the class name from the second message is VisualBasicSimplifyTypeNamesDiagnosticAnalyzer, we suppose that it occurs because the code analyzer does not work properly when attempting to analyze the type name or suggest an alternative name. We suggest that you contact the Roslyn community regarding this issue.

See also:
VisualBasicSimplifyTypeNamesDiagnosticAnalyzer threw exception 'source cannot be null'

Best Regards,
Nevron Support Team





Similar Topics


Reading This Topic