*.config and *.csproj files format after using nuget manager


Is there a way to control how *.config and *.csproj are formatted after updating nuget packages?
Settings from the "Editor>Code Style>XML" seem not to affect format of the updated config and *.csproj files.
Any chances to get it under control to minimize unnecessary changes?

Thank you!


Comment actions Permalink


Could you please clarify what Rider version are you using and what is the exact concern about formatting in *.config and *.csproj files after updating NuGet packages? Screenshots or the files themselves before and after would be much appreciated. You can upload them here or with a new issue on our bug tracker. Thank you in advance!

Comment actions Permalink


Also annoyed by the issue described by KNTC. Every time after upgrading references in Nuget manager need to open *.csproj file and auto-format it to remove extra spaces added before />.

My current version:

JetBrains Rider 2020.2.4
Build #RD-202.7660.16, built on September 30, 2020

Steps to reproduce:

1. Initially .csproj file does not contain spaces before /> and this aligns with my "Editor->Code Style->XML" settings.

2. Upgrade Autofac.Extras.Moq to 6.0.0 in Nuget window.

3. Now .csproj contains spaces before />.


Thank you!

Comment actions Permalink

Hello Dima, thank you for giving an example, unfortunately you have faced a known issue: RIDER-40468. We would appreciate it if you would upvote it in order to bring increased awareness to the issue. Please also make sure to Watch for monitoring the progress.


Please sign in to leave a comment.