I had an issue starting Wabbajack entirely, it was crashing with the following in event viewer:
Application: Wabbajack.exe
CoreCLR Version: 9.0.1125.51716
.NET Version: 9.0.11
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AggregateException: Some services are not able to be constructed (Error while validating the service descriptor 'ServiceType: Wabbajack.Networking.NexusApi.ProxiedNexusApi Lifetime: Singleton ImplementationType: Wabbajack.Networking.NexusApi.ProxiedNexusApi': Unable to resolve service for type 'Wabbajack.Networking.Http.Interfaces.ITokenProvider`1[Wabbajack.DTOs.Logins.WabbajackApiState]' while attempting to activate 'Wabbajack.Networking.NexusApi.ProxiedNexusApi'.)
I have dotnet9, C++, etc. all installed, I can provide more info on the setup if you need, but I'm also a dev and run dotnet10 generally, VS code, VS 2026.
When I downloaded the 4.0.5.1 full package, I was able to start it, but then received an error while beginning the modlist installation. It was throwing an error after initializing all of the downloaders, while instantiating the installer.
It was about missing injected dependency, related to VFS Context. I pulled the source and debugged. Exception was thrown at InstallationVM.cs (StandardInstaller creation at line 647)
Looked for startup, and it seems like VFS Context just isn't registered in the startup for Wabbajack.App.Wpf. I added registration for it at app.xaml.cs in UI layer and it resolves fine (services.AddTransient(); around line 306).
If you can't reproduce or if you think it's not an issue, that's fine - I just figured I'd plop this here to give some extra help in case anyone else had the same problem or if you can repro elsewhere. If I were less lazy I'd add safety code (since I don't know if this is where you'd actually want to inject it, or if it's the correct scope, though it seems to work fine), and fork, but... you know - it's very late on a Sunday. 😆
I had an issue starting Wabbajack entirely, it was crashing with the following in event viewer:
Application: Wabbajack.exe
CoreCLR Version: 9.0.1125.51716
.NET Version: 9.0.11
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AggregateException: Some services are not able to be constructed (Error while validating the service descriptor 'ServiceType: Wabbajack.Networking.NexusApi.ProxiedNexusApi Lifetime: Singleton ImplementationType: Wabbajack.Networking.NexusApi.ProxiedNexusApi': Unable to resolve service for type 'Wabbajack.Networking.Http.Interfaces.ITokenProvider`1[Wabbajack.DTOs.Logins.WabbajackApiState]' while attempting to activate 'Wabbajack.Networking.NexusApi.ProxiedNexusApi'.)
I have dotnet9, C++, etc. all installed, I can provide more info on the setup if you need, but I'm also a dev and run dotnet10 generally, VS code, VS 2026.
When I downloaded the 4.0.5.1 full package, I was able to start it, but then received an error while beginning the modlist installation. It was throwing an error after initializing all of the downloaders, while instantiating the installer.
It was about missing injected dependency, related to VFS Context. I pulled the source and debugged. Exception was thrown at InstallationVM.cs (StandardInstaller creation at line 647)
Looked for startup, and it seems like VFS Context just isn't registered in the startup for Wabbajack.App.Wpf. I added registration for it at app.xaml.cs in UI layer and it resolves fine (services.AddTransient(); around line 306).
If you can't reproduce or if you think it's not an issue, that's fine - I just figured I'd plop this here to give some extra help in case anyone else had the same problem or if you can repro elsewhere. If I were less lazy I'd add safety code (since I don't know if this is where you'd actually want to inject it, or if it's the correct scope, though it seems to work fine), and fork, but... you know - it's very late on a Sunday. 😆