any reason not to ship packages.config after 9.12.* ?
we are facing some issues when we configure VS with 9.12.* because of this
any reason not to ship packages.config after 9.12.* ?
we are facing some issues when we configure VS with 9.12.* because of this
Hi Shiwanka,
We don't use packages.config anymore. We use PackageReference instead.
What do you need it for? You can install the Dynamicweb.Admin package from nuget.org and then your web application project will have all required dependencies added to either packages.config or as PackageReference entries in the project file (depending on your project configuration).
ok, understood
can you help to resolve this query based on this scenario?
We have a project that is configured full-on VS and running with 9.10.* and We need to upgrade to 9.12.*, what would be the ideal steps to follow? (we don't want to lose svn history and this should do within max 2hrs time frame).
what we did before is replace Admin folder and package.config and restore nuget, then we will get latest version with in few minutes time
Can you try to follow these steps?
https://docs.microsoft.com/en-us/nuget/consume-packages/migrate-packages-config-to-package-reference
HI Nicolai
If i convert to package Reference can I update the version only updating NuGet package of the Dynamicweb.Admin ? meant to say Admin folder also getting update?
You must be logged in to post in the forum