Provide informational messaging when a package used content files or install.ps1

[KSchlobohm]

When try-convert migrates from packages.config to PackageReference it should provide informational links/messaging that explain that some features may have changed by moving to PackageReference.

Packages such as NLog.Config do not function the same when referenced via PackageReference as they can no longer provide a "default" nlog.config file that can be edited. Content files can only be linked to and are not editable.

If a project previously referenced bootstrap, and had made changes to the bootstrap.css file then try-convert should explain how to think about upgrading this scenario. A prompt asking the user how to proceed might be helpful.

There are at least two choices that could happen

• Option1 - keep the modified file as a Content reference (what should happen to the file added by the package? can it be overriden/hidden)
• Option2 - delete the modified file use the file from the NuGet package

If the package previously used the Install.ps1 to modify the web.config or make some other change then this feature will not be supported post PackageReference conversion and that information should be made more visible.

Package compatibility issues