- ABP Framework version: v7.3.0
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Auth Server Separated (Angular): no
- Exception message and stack trace:
- Steps to reproduce the issue:"
Attempting to update my project from 7.2.3 to 7.3.0 using the ABP CLI update command gives an error.
$ abp update ABP CLI 7.3.0 Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at Volo.Abp.Cli.ProjectModification.VoloNugetPackagesVersionUpdater.GetLatestVersionFromMyGet(String packageId) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo. Abp.Cli.Core\Volo\Abp\Cli\ProjectModification\VoloNugetPackagesVersionUpdater.cs:line 281 at Volo.Abp.Cli.ProjectModification.VoloNugetPackagesVersionUpdater.UpdateSolutionAsync(String solutionPath, Boolean includePreviews, Boolean includeReleaseCandidates, Boolean swi tchToStable, Boolean checkAll, String version) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectModification\VoloNugetPackagesVersi onUpdater.cs:line 42 at Volo.Abp.Cli.Commands.UpdateCommand.UpdateNugetPackages(CommandLineArgs commandLineArgs, String directory, String version) in D:\ci\Jenkins\workspace\abp-volo-release\abp\frame work\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\UpdateCommand.cs:line 80 at Volo.Abp.Cli.Commands.UpdateCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\C ommands\UpdateCommand.cs:line 44 at Volo.Abp.Cli.CliService.RunInternalAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliServic e.cs:line 169 at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 77
11 Answer(s)
-
0
hi
MyGet is down now. You can try again after it is back. You can also upgrade packages to the latest manually.
https://myget.org/
-
0
MyGet is still down, I decided to take your suggestion and go manual
Manually upgraded packages from 7.2.3 => 7.3.0. Then abp install-libs. Also needed to add Hangfire.Core. When trying to run the backend the restores take about 10 minutes (usually ~1 minute) and then we get this error (i clipped it as it is very long). I got to this point yesterday before the issues w/ myget.
previous restores are all succesful and then this:
c:\appdev\otised\OtisEd.Synergyz\aspnet-core\src\OtisEd.Synergyz.HttpApi.Host\OtisEd.Synergyz.HttpApi.Host.csproj : error NU1106: Unable to satisfy conflicting requests for 'Volo.Abp.MultiTenancy': Volo.Abp.MultiTenancy (>= 7.3.0)
.....
package/Volo.Abp.MultiTenancy.Abstractions 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.MultiTenancy.Abstractions 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.Localization 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.MultiTenancy.Abstractions 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.MultiTenancy.Abstractions 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.Localization 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.Localization 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.Localization 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3 Failed at 'command: "dotnet.exe" restore c:\appdev\otised\OtisEd.Synergyz\aspnet-core\OtisEd.Synergyz.sln --interactive' (994572ms) with error: ERROR ExitCode(null)
-
0
@maliming Do you guys have a contingency plan in case myget does not return?
- status.myget.org reports all services down (for over 24 hours now)
- docs.myget.org reports that the Azure App service is not running
- Their twitter account (@mygetteam) has not posted in nearly 3 years
From my perspective, this is looking very much like a dead project at this point.
-
0
hi paul.harriman
Did you upgrade the leptonX packages?
@scott7106 We have removed the myget source. Only night build uses it. we'll continue to see what happens with it
-
0
@maliming I see there is a new version of ABP (7.3.1). When I update CLI to 7.3.1 and then run the abp update command, the NPM packages are updated to 7.3.1 however, the nuget packages are still 7.3.0. Is this the expected behavior of this release?
-
0
so this morning abp update runs normally. the ~10 minute restore is back to normal. the long error still exists when i try and run the backend. Scott and I are looking at it now
c:\appdev\otised\OtisEd.Synergyz\aspnet-core\src\OtisEd.Synergyz.HttpApi.Host\OtisEd.Synergyz.HttpApi.Host.csproj : error NU1106: Unable to satisfy conflicting requests for 'Volo.Abp.MultiTenancy': Volo.Abp.MultiTenancy (>= 7.3.0) (via package/Volo.Abp.
lepton-x is at 2.3.0
host/package.json "@volo/abp.aspnetcore.mvc.ui.theme.leptonx": "~2.3.0",
angular/package.json "@volosoft/abp.ng.theme.lepton-x": "^2.3.0",
upgraded to 7.3.1, then i get
-
0
Any update on the last 2 questions in this thread? It has been a week now with no response.
-
0
hi
the NPM packages are updated to 7.3.1 however, the nuget packages are still 7.3.0. Is this the expected behavior of this release?
You can run the command again.
error NU1106: Unable to satisfy conflicting requests for 'Volo.Abp.MultiTenancy': Volo.Abp.MultiTenancy (>= 7.3.0) (via package/Volo.Abp.
You can create a new template project and copy the lepton package version to your project.
-
0
Hi,
Thank you for the fast response yesterday. Running the update command again did update all the relevant references to 7.3.1 as expected. As a side note, I create a new project as you suggested and it is using 2.3.*-* for the LeptonX package. I changed this and backed up to the last release build since I do not want preview packages.
Even with all of this, the dotnet restore command still errors out after 10+ minutes. We are continuing to investigate the issue, I will report back when we have more information.
-
0
hi
Even with all of this, the dotnet restore command still errors out after 10+ minutes.
What's the error?
-
0
The error is "Unable to satisfy conflicting requests for 'Volo.Abp.MultiTenancy'". We have isolated the issue to a dependent module which did not get updated. I believe we can close this ticket now.
