We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After converting project, packages.config still remains even though those references are now migrated to <PackageReference> elements.
packages.config
<PackageReference>
The file is also specifically mentioned in the generated csproj:
csproj
<None Include="packages.config" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" />
Which it should not.
I recommend this file is deleted. Or at least renamed to .old.
.old
The text was updated successfully, but these errors were encountered:
The same probably applies for any nuspec file being converted to be inside csproj
Sorry, something went wrong.
Agreed, but we still need to figure out if we have parity for both files in the new system.
At first I didn't want to touch any of these files but it is weird to keep them included. I think renaming them too is worthwhile and safe.
This is now renamed by merging #26 the packages config is now renamed. I won't delete any file as I cannot assume version control being present.
No branches or pull requests
After converting project,
packages.config
still remains even though those references are now migrated to<PackageReference>
elements.The file is also specifically mentioned in the generated
csproj
:Which it should not.
I recommend this file is deleted. Or at least renamed to
.old
.The text was updated successfully, but these errors were encountered: