Guys, is it possible to provide some kind of documentation on what changes C# compiler applies to expression tree when it generates Expression object from C# code in IQueryable context?

As ORM developers, who need to work with expressions, from time to time we hit issues, because we receive unexpected values from expressions. Like char or enum values is source code being replaced with integer c

Just followed the instructions as per docs sample:

1. Install scriptcs via Chocolatey
2. Copy-Paste code snippet
3. Install RavenDB.Embedded in a workdir
4. Launch app.csx

Log:

$ scriptcs -install RavenDB.Embedded
Installed: RavenDB.Embedded
Package installation succeeded.
Saving packages in scriptcs_packages.config...
Creating scriptcs_packages.config...
Added RavenDB.Embedded (

What would you like to be added:

Implement the TextBlock.MaxLines. It's not implemented yet:
https://github.com/unoplatform/uno/blob/4bd015b98029ae8c121a5ad9d36268742fb76b8e/src/Uno.UI/UI/Xaml/Documents/UIElementTextHelper.wasm.cs#L107_L110

Documentation:
https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.controls.textblock.maxlines

Solution:
https://twitter.com/addyosmani/st

Whenever you create a variable named document, you can't use the class Document anymore.
As work-around you can rename the variable (to e.g. doc).

Steps To Reproduce

https://deck.net/3707a48b6ab5672937f9c3b1a8207979

public class Program
{
    public static void Main()
    {
        var document = new HTMLDivElement {
            TextContent = "Hello world!"   
  

The analyzer docs contain the same info you can find inside of visual studio, so clicking to see more details of any RCS number serves no practical purposes at the moment.

This is a really neat project! New users may find it useful to see a list REPL commands when the REPL is launched:

PS C:\Code> dotnet script
Commands:
  #help                     Show help information
  #load                     Load a script into the REPL (same as #load usage in CSX)
  #r                        ...
  ...
>

Invoking #help would show the list of REPL comm

When you comment out some code, the code comments as you would expect. However, when you uncomment that code again, RoslynPad decides it needs to re-format your entire document. This is unexpected, and unwanted behavior. It requires you to take the additional step of undoing the last command (the formatting) any time you uncomment code.

Formatting should not ever be an automatically-applied

I love that these features are available, but am left very confused. I am coming straight to C# using VS Code on Linux, never used Visual Studio.

Searching the web I can only find blog articles mentioning these features at /www.strathweb.com and a pull request.

How do I know what rules I can use in my editorconfig file using this extension? The best reference I can find seems to be https:/

The analyzer warns correctly, but the documentation for SCS0007 only has guidance for XmlReader and XmlDocument. The warning also appears for XmlPathDocument/XPathNavigator, which is also insecure by default on .NET version prior to 4.5.2. https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.md#xpathnavigator has guidance on an example fix

I've been playing around with this package, and while I think it has some merit and potential, it feels woefully under-documented, and its advice is confusing.

For example, I ran across an interpolated string in my code where the analyzer raised HAA0601. The help link does nothing, nor is there any code fix available, so I really don't know how to fix this. I'm guessing it's because the value t

.aspx files should change CodeBehind tag vale from ".vb" -> "*.cs"

There are categories of API advice for which deprecation seems like too strong a word.

It seems like this is also an ideal place to notify of less severe issues (guidance).

I am thinking about this for the issues surrounding APIs which are inferring their Assembly load context from their caller and sometimes get this wrong.
See https://github.com/dotnet/coreclr/blob/master/Documentation/d

https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/fabric

The testing SDK provides EmptyDiagnosticAnalyzer for this case (and EmptyCodeFixProvider for cases where there is an analyzer but no fix).

Originally posted by @sharwell in dotnet/roslyn-analyzers#3143 (comment)

this should be in the docs once the new testing sdk is released

The new Roslyn API context.Options.AnalyzerConfigOptionsProvider.GetOptions allows to get the configuration from the editorconfig file.

• Remove the custom editorconfig parser
• Replace all usage by context.Options.AnalyzerConfigOptionsProvider.GetOptions
• Update tests
• Update documentation to use the new names
• Update <https://github.com/meziantou/editorconfig/bl