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
{{ message }}
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
Extra errors are shown when you enable produce outputs on build. Without this checkbox set, the design time host builds returns us the framework that the error belongs to and we format the error message to include this in the msbuild subtype field. This is later picked up by our project system and we push those errors into the corresponding language service which will unify it with existing errors. For produce outputs on build the framework information is not present so we don't know the language svc to pass them to. The fix is for the produce outputs on build to leverage the subtype field of an msbuild canonical error.
The highlighted is missing in the typical error message. If the command line builds wrote the friendly framework name here this would just work. C:\Users\billhie\documents\visual studio 14\Projects\ConsoleApp1\src\ConsoleApp1\Program.cs(12,25,12,34): DNX 4.5.1 error CS0246: The type or namespace name 'MailChimp' could not be found (are you missing a using directive or an assembly reference?)
The text was updated successfully, but these errors were encountered:
Adding additional category information representing the framework is deemed difficult. The conversion from roslyn Diagnostic to an error message is a black box implemented in CSharpDiagnosticFormatter.
I'm researching if I can replicate the Diagnostic and put additional information into it so that when it is converted to error message, framwork information is in it.
Another approach is to derive https://github.com/dotnet/roslyn/blob/master/src/Compilers/Core/Portable/Diagnostic/DiagnosticFormatter.cs
Extra errors are shown when you enable produce outputs on build. Without this checkbox set, the design time host builds returns us the framework that the error belongs to and we format the error message to include this in the msbuild subtype field. This is later picked up by our project system and we push those errors into the corresponding language service which will unify it with existing errors. For produce outputs on build the framework information is not present so we don't know the language svc to pass them to. The fix is for the produce outputs on build to leverage the subtype field of an msbuild canonical error.
The highlighted is missing in the typical error message. If the command line builds wrote the friendly framework name here this would just work. C:\Users\billhie\documents\visual studio 14\Projects\ConsoleApp1\src\ConsoleApp1\Program.cs(12,25,12,34): DNX 4.5.1 error CS0246: The type or namespace name 'MailChimp' could not be found (are you missing a using directive or an assembly reference?)
The text was updated successfully, but these errors were encountered: