Activities of "kateryna.zorina"

Hi! As it was suggested in one of previous comments, we compared our version with version from master branch. We will compare with develop and get back to you.

Hi,

We compared our current version with Startup.cs from master branch and see the same problem there. Please, double check that current configuration of Swagger in Startap.cs from master does generate models in the same way as in service-proxies.ts from angular master. Check PagedResultDtoOfNameValueDto, EntityDtoOfInt64, etc.

Hi! After some investigation, we confirm that there is inconsistency between frontend and backend in terms of swagger and service-proxies in the 9.00v of the framework. Backend must use NSwag, because it generates generic types e.g.: EntityDtoOfGuid, PagedResultDtoOfNameValueDto, which are referenced in frontend. This means that in Web.Host Startup.cs, in ConfigureServices, should be a call to services.AddSwaggerDocument, and in Configure calls to app.UseOpenApi(); and app.UseSwaggerUi3. Also, corresponding nuget packages must be installed.

Hi! When updaing service proxies "generic" types like EntityDtoOfGuid, PagedResultDtoOfNameValueDto are not generated at all, and we get angular build errors, because these types are referenced in many places, e.g. common-lookup-modal.component.ts

Hi! Thanks for explanation.

Hi, in the 9th version, which we downloaded recently, there seems to be an inconsistency between angular and aspnetcore projects in terms of Swagger. In angular project there are many "generic" types like EntityDtoOfGuid, PagedResultDtoOfNameValueDto etc. which correspond to EntityDto<Guid> and PagedResultDto<NameValueDto> in c#. However, Swashbuckle implementation of swagger, which is used in Startup.cs, does not support generics, and these types are not generated when updating service-proxies.ts. After some investigation, we found out that Nswag does this, and we assume that Startup.cs in Web.Host, and Swagger*Filters in Web.Core are wrong. Could you check this?

hi guys!

We use AspNet Zero framework and currently working on integration with Identity Server. We found the following module https://docs.abp.io/en/commercial/latest/modules/identity-server and now have a questions:

1. Does our AspNet Zero license allows us to use this module?
2. Will it be correct to use this module in our app?
3. Won’t it have further implementation conflicts, since AspNet Zero also has Identity Server support?

Thanks

Hi, guys! I have a simple question. We're developing a web app, which can be iframed. Also we use token authentication and store auth token in cookies, which are stored using abp.utils.setCookieValue function. When app is iframed and we try to access/store cookies - the following warning appears - A cookie associated with a cross-site resource at was set without the 'SameSite' .... We've managed to get rid of this warning slightly modifying a function, that stores a cookie (adding cookieValue += "; SameSite=None; Secure" to the end of the function). We need to have ability to set these values out of the box, so are you planning to update this function in the nearest future?