Feature category

• Check(Type 'x') any that Applicable item:
  • Vim
  • Vim plugin

Currently it seems that VsVim (and Vim for that matter) do not support interpolated strings of C#. It would be really neat if in a string like the following:

logger.Info($"Starting to move tokens {(string.Join(", ", tokens))} from card with code: {oldCard.Code} to replacement card with

Use this query to search for the most popular feature requests.

Is your feature request related to a problem? Please describe.
I'm always frustrated when I read the document, I don't know whether + - is supported in string/list, whether [] is case sensitive or not in htt

Environment

• Visual Studio version: [2019 Community]
• CodeMaid version: [11.1]

Description

Installation breaks all custom entries in the context menu "Other Context Menus | Easy MDI Document Window"

Steps to recreate

1. Call Customize... (from the menu or toolbar)
2. Add a custom item into "Other Context Menus | Easy MDI Document Window"
3. Install CodeMaid
4. Open a fil

This suggestion is based on real experience helping an internal customer identify missing API's in the WCF client implementation. We have some properties on our classes which are either server only api's or aren't currently supported. An example of this is NetTcpBinding.TransactionFlow. On .NET Framework, this property is [defined like](https://referencesource.microsoft.com/#System.ServiceModel/Sy

Add examples of how to do different things with XAML generation.
This could be in profiles.md or in a separate (linked) document.

Examples such as

• how to exclude a common base type property
• how to create a DataGrid from a collection
• more...?

X-ref: discussion in #259

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

--source should be the source of the root, not of the package. Otherwise how can we use it when packages are inside nested directories?

In other words, how would one use it with --recursive and with --latest-only ?

It would be nice if the ID of a specific analyzer would be shown in Super Quick Info (probably at the end of the its message). Ideally that ID would be clickable as it is in the "Lightbulb" menu:

![2019-02-05 09_36_20-](https://user-images.

Write a "How to open *.nswag files with NSwagStudio from Solution Explorer"

If the model has no tables, DAX Editor shouldn't create a new DAX file. Now it opens an empty file in compatibility level 1200 and generates an exception in compatibility level 1103.

If any custom local images are referenced in the given overview.md they should be included in the publishManifest.json and copied to the VSIX project directory.

See https://docs.microsoft.com/en-us/visualstudio/extensibility/walkthrough-publishing-a-visual-studio-extension-via-command-line?view=vs-2019#asset-files