Well if its copying to output directory it doesn't really make sense to have it embedded, but I tried it anyway and published, this did copy the files to Templates, but still I deployed this and still the same issue
I can confirm that the files ended up on the file system of the docker container
The issue is that this is missing in the file ProjectBlazorHostModule on the blazor.server.host project...
Configure<AbpMultiTenancyOptions>(options =>
{
options.IsEnabled = MultiTenancyConsts.IsEnabled;
});
Using "brave" and "edge" in incognito, same problem.
Blazor.Server.Host is the startup project
I have manually changed everything to leptonx in the module successfully, but the tenant missing issue is happening straight from module creation.
Generated by ABP suite with new module solution wizard
Same error. I've uploaded a fresh project for you, just created now with abp new abpupdate -v 7.2.2 please unzip and run abp update -v 7.2.3 on this project.
Does this mean my abp login or a login for a specific project?
I replicated this on another machine by
I already explained that I did this, I'm not sure what is unclear on my side... but thanks.
Anjali,
I tried that, but it just causes more inconsistencies, rabbit hole of dependency problem. All abp packages should be on same version to avoid this, thats what im trying to do but it doesnt work either.
I create a brand new project at v 7.2.2 then i tried to update the project to 7.2.3 and i got the same update errors so it doesn't seem project specific. Can we have a screenshare?
I did perform the steps above.
I'm reporting that I have a solution that i need to update, it is currently on 7.2.2. Part of the update is to run abp update on this solution which will update the abp components from 7.2.2 to 7.2.3. So I run abp update, and you can see the failures above. I **cannot **simply start a brand new project on a newer version and copy all my code.
I have a bugfix I must deliver to a client, but I cannot build the solution because i receive this error in authserver.
Even though I have checked and auth server explicitly has this reference, i still get the error and cannot build.
so then i went to update my solution to 7.2.3 via abp update -v 7.2.3 and it fails. I need to resolve this asap.
