If a file from a previous version of a NuGet package has been modified, NuGet ignores that file completely when updating the package version. Instead of ignoring the file and not picking up the latest updates, can't NuGet just pop up the VS merge UI and give the developer the chance to keep his changes, overwrite with the new version of the file, or to merge the two together?
This is causing a lot of headaches on our team as files we expect to be updated with the new version silently do not update because the customer had tweaked the original. Please allow for merges.
Comments: This is a dupe of #278
This is causing a lot of headaches on our team as files we expect to be updated with the new version silently do not update because the customer had tweaked the original. Please allow for merges.
Comments: This is a dupe of #278