Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "geertveenstra"

Hi, nothing was changed inside the FindUsers().

Your code is also giving the same Exception.

var query = UserManager.Users.Where(u => !userIdsInOrganizationUnit.Contains(u.Id));
var userCount = await query.CountAsync();

If I change the code to

var query = UserManager.Users.Where(u => !userIdsInOrganizationUnit.Contains(Convert.ToInt64(u.Id)));
var userCount = await query.CountAsync();

it is working fine and the non-assigned users show up in the modal

If I convert it explicitly to Int64 the exception is also not happening.

.Where(u => !userIdsInOrganizationUnit.Contains(Convert.ToInt64(u.Id)))

instead of

.Where(u => !userIdsInOrganizationUnit.Contains(u.Id))

I always thought there was no difference between using long or Int64 types ?

Should this setting not also be added to the MVC project then ? Since in that project it is also configured in startup.cs as

// Enable middleware to serve generated Swagger as a JSON endpoint
app.UseSwagger();
 // Enable middleware to serve swagger-ui assets (HTML, JS, CSS etc.)
app.UseSwaggerUI(options =>
{
     options.SwaggerEndpoint(_appConfiguration["App:SwaggerEndPoint"], "Portal API V1");
     options.InjectBaseUrl(_appConfiguration["App:WebSiteRootAddress"]);
 }); //URL: /swagger

I use this method since the beginning

[https://github.com/aspnetzero/aspnet-zero/issues/96#issuecomment-268093697]

I try to change as little as possible in the original files and if really necessary add as many comments as I can so I can recognize it when merging

For now, I added this to bundleconfig.json which fixed it for me.

{ "outputFileName": "wwwroot/metronic/src/js/demo/default/base/layout.min.js", "inputFiles": [ "wwwroot/metronic/src/js/demo/default/base/layout.js" ] }, { "outputFileName": "wwwroot/metronic/src/js/demo/demo8/base/layout.min.js", "inputFiles": [ "wwwroot/metronic/src/js/demo/demo8/base/layout.js" ] }

Not sure if it is the final solution, leave that up to you :-)

Probably same as already reported by me for Core & jQuery :

[#5867]

Thanks,

i am having the issue with the CORE & jQuery download, tried several times.

The abp.tenant cookie is not deleted on returning to the host.

Hi,

I am testing on the latest zero version (5.1)

Thanx, but what would I check exactly ?

I already mentioned I get an exception page on returning to the host. In the logfile I see the following error :

Mvc.ExceptionHandling.AbpExceptionFilter - Current tenant is different than given tenant. AbpSession.TenantId: 2, given tenantId:

Is the problem to be searched for in the aspnetzero code or in the boilerplate code ? I also wonder why the cookie is needed since it seems to be working also without it ?

Showing 11 to 20 of 22 entries