repro steps:
1. install a package that has the same file name with what's included in project
2. when asked for file conflict, select no
3. start PMC, uninstall the package, got the following warning message:
PM> uninstall-package Overwritetest
Removing 'OverwriteTest 1.0.0' from ClassLibrary7-VB.
__Skipping 'Class1.vb' because it was modified.__
Successfully removed 'OverwriteTest 1.0.0' from ClassLibrary7-VB.
Uninstalling 'OverwriteTest 1.0.0'.
Successfully uninstalled 'OverwriteTest 1.0.0'.
The fact is, Class1.vb was NOT modified, since users picked No during installation. Should reword the sentence to something like:
Skipping 'Class1.vb' because it was not overwritten.
Comments: I agree it's confusing, but we can't detect if it was modified or it wasn't overwritten. We just simply compare the contents of the file in package versus the file in project.
1. install a package that has the same file name with what's included in project
2. when asked for file conflict, select no
3. start PMC, uninstall the package, got the following warning message:
PM> uninstall-package Overwritetest
Removing 'OverwriteTest 1.0.0' from ClassLibrary7-VB.
__Skipping 'Class1.vb' because it was modified.__
Successfully removed 'OverwriteTest 1.0.0' from ClassLibrary7-VB.
Uninstalling 'OverwriteTest 1.0.0'.
Successfully uninstalled 'OverwriteTest 1.0.0'.
The fact is, Class1.vb was NOT modified, since users picked No during installation. Should reword the sentence to something like:
Skipping 'Class1.vb' because it was not overwritten.
Comments: I agree it's confusing, but we can't detect if it was modified or it wasn't overwritten. We just simply compare the contents of the file in package versus the file in project.