-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
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
Can't upgrade packages.config file in VB.Net projects #9
Comments
I get the same error. @robertmclaws could this please be fixed as this could be such a useful tool?
|
Same. Visual Studio 2017 Enterprise v15.7.4. @robertmclaws Would be estatic to beta test.
|
Did they ever get around to fixing this? |
Visual Studio 2017 has a conversion feature, so I doubt this will ever be
fixed.
Right click a project with packages.config and the option will appear.
…On Tue, Mar 12, 2019 at 5:36 AM Abrahamlet ***@***.***> wrote:
Did they ever get around to fixing this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA-wyHrwcvC2qzcY9So8pVe7e7P3poFZks5vV4M3gaJpZM4Rjvvs>
.
|
Submitted a fix. #11 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Installed product versions
Description
In a .sln file, I have a couple VB.Net projects (of type Class Library). Each references one or more NuGet packages, and under each project root is the packages.config file. The tool fails to upgrade any of the packages.config files. I've
attachedpasted the contents of one of the packages.config that the tool was failing on.Steps to recreate
Current behavior
In the output pane, the tool logs that the current packages.config was backed up then, on the very next step, it outputs that a null reference exception occurred. Pasted below is the full output.
Output
packages.config
Expected behavior
Convert the items within the packages.config file to PackageReferences within the .vbproj file.
The text was updated successfully, but these errors were encountered: