roslyn

It seems to have partially inherited fonts and colors from my current settings, which has made it pretty ugly right now. I looked in fonts and colors but there is no settings for C# Interactive. Disclaimer : I work for Microsoft on the Roslyn team. We have not done the polish work to create the logical and correct fonts and colors for the C# Interactive Window yet. In this case, the black text in your screenshot should using Text Editor->Plain Text, but it's not. Instead, it's using "Text Editor->Interactive Console - Black". If you change "Text Editor->Interactive Console - Black" to match

I have two identical ASP.Net 4.6 MVC project, project 1 is using roslyn complier within the site which is working fine. c:\windows\system32\inetsrv>C:\Websites1\bin\roslyn\csc.exe Microsoft (R) Visual C# Compiler version 1.2.0.60325 With the second project I'm getting the error below, it's using the complier from .Net framework. c:\windows\system32\inetsrv> "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe" Microsoft (R) Visual C# Compiler version 4.6.1590.0 Line 6: @if (!Model?.Item?.IsDerived(Templates.PageMetadata.ID) ?? true) Line 7: { Line 8: return; c:\Website2\Views\metadata

Following on from this tutorial from MS, I have created an analyzer for Roslyn. According to the page, you can mark the rule as DiagnosticSeverity.Error , and this will cause the build to break: In the line declaring the Rule field, you can also update the severity of the diagnostics you’ll be producing to be errors rather than warnings. If the regex string doesn’t parse, the Match method will definitely throw an exception at run time, and you should block the build as you would for a C# compiler error. Change the rule’s severity to DiagnosticSeverity.Error: internal static

To generate open cover report I have to make debugType as Full. I generate report on build server as I have to fail the build if the coverage doesn't reach a certain threshold. The build is generated in Release mode. What consequence does keeping debugType Full in my csproj file have? Will it degrade the performance in production? The difference is that the "full" type emits a classic windows PDB symbol file which is complex and poorly documented. The "portable" PDB format is a new open-source format that can be created and used on all platforms. You can read more information on this format at

Using expression-bodied members allows you to define the body of a method or property as a single expression without a return keyword (should it return something). For example it turns these int Method1() { return 5; } void Method2() { Console.WriteLine(); } into these int Method1() => 5; void Method2() => Console.WriteLine(); A difference comes into play when you throw an exception from the body: void Method3() { throw new Exception(); } However, the following will not compile: void Method3() => throw new Exception(); with the following messages: Warning The member 'Program.Exception()' does