![visual studio 2019 release note visual studio 2019 release note](https://docs.microsoft.com/en-us/visualstudio/releases/2019/media/16.10/16.10_p2_rebase_conflicts.png)
You can locate the RELEASE-NOTES.txt file anywhere, in this case, I located the RELEASE-NOTES.txt file at the solution folder of the my NuGet package library project. Write the release notes in outside of the project file.Īt first, create a text file named RELEASE-NOTES.txt, and write the package release notes in this file, like this. csproj file, and import it from inside of. The method is, writing the package release notes in a text file which is outside of. One day, I found the method to solve this my problem finally! writing custom build tasks) without auto-formatting is also strongly painful. Yes, I can avoid this trouble by disabling auto-format feature, but editing. You can see many undesired spaces and line breaks in the package release notes after auto-formatting. This auto-formatting feature breaks all of the layout of the package release notes! However, if you write the package release notes by Visual Studio's text editor directly, is become a nightmare.īecause the Visual Studio's text editor format the XML contents of. While you are writing the package release notes in Visual Studio's project property GUI, there is no problem. However, editing release notes is a nightmare.īy the way, if you are developing a library to be a NuGet package, you would like to write the package release notes. csproj file in that's text editor when the project node in solution explorer is double-clicked, instead of showing project property GUI, if the. csproj file.Īdditionally, by default, Visual Studio 2019 opens a. csproj file (a.k.a "SDK style project") is very simpler rather than old style. csproj XML file, instead of via Visual Studio's project property GUI.īecause, the contents of modern. In a C# programming these days, it is becoming increasingly the case that direct editing a.