Activities of "liangshiwei"

Hi,

Yes,we will fix it: https://github.com/abpframework/abp/pull/16324

Hi,

I don't think this is related to package restoring. If there is no restore, you can't even build the project.

Hi,

I shared the project with you, please check it

Hi,

You can overwrite the code of the module by creating a JS file in the same path.

The path is Pages/Forms/Shared/Components/ViewForm/Default.js.

The redirect code is location.href = ${window.origin}/Forms/${result.id}/FormResponse;

Default.js

https://gist.github.com/realLiangshiwei/2cbe40167c85b22e13148b6558bea864

ok. What's your email?

Yes, since your web app project needs to remain independent, it should not depend on any service projects if you want to upgrade only the web app without upgrading other services

In this case, you need to generate client proxies in the web app project.

Static c# proxies currently depending on target service's application.contracts package, so they can reuse the DTOs and other related classes. However, that can be a problem when we want to create fully independently developed and deployed microservices. We want to use the static proxy generation even without depending target service's application.contracts package.

More explanation:https://github.com/abpframework/abp/issues/13613

Hi,

Thanks for the inputs, it got succussed partially when I executed Step 1: proxies got generated only for Sample Controller

There are two API definitions only uppercase and lowercase letters differ,

You can try -m UserTaskService

Also We would like to understand why dynamic proxies are not working

You have to reference the UserTaskService.HttpApi project and add module dependency to AppV3WebModule if you want to use dynamic proxies.

Using dynamic proxies will make things easier, you don't have to generate static proxy files and can remove those files.

Hi,

I can't reproduce the problem

.AddOpenIdConnect("AzureOpenId", "Azure AD OpenId", options =>
{
    options.Authority = "https://login.microsoftonline.com/" + configuration["AzureAd:TenantId"] + "/v2.0/";
    options.ClientId = configuration["AzureAd:ClientId"];
    options.ResponseType = OpenIdConnectResponseType.CodeIdToken;
    options.CallbackPath = configuration["AzureAd:CallbackPath"];
    options.ClientSecret = configuration["AzureAd:ClientSecret"];
    options.RequireHttpsMetadata = false;
    options.SaveTokens = true;
    options.GetClaimsFromUserInfoEndpoint = true;
    options.Scope.Add("email");
    options.ClaimActions.MapJsonKey(ClaimTypes.NameIdentifier, "sub");
    
    var onTokenValidated = options.Events.OnTokenValidated;
    options.Events.OnTokenValidated = validatedContext =>
    {
        validatedContext.Principal.AddClaim(AbpClaimTypes.Email, 
            validatedContext.Principal.FindFirstValue(ClaimTypes.Email));
        return onTokenValidated.Invoke(validatedContext);
    };
})

Thanks for the inputs, If we understand correctly we can have different versions of solutions if we move all web pages into web and remove all depended projects (web) from main UI layer. in this case we need to remove reference to contract layer as well? You mention We support this feature after 7.0.0, (It also requires that the service version is 7.0.0.) means this kind of approach will work only after having our entire project running on 7.0 and for future upgraded we can follow this way? please elaborate

• You need to upgrade your project to at least 7.0.0.
• Then delete all references to the services in the web app
• Generate static proxy for web app, it will generate all required files, interfaces, DTO, etc.

Can you please shed some light on what changed with the version 7.1 that might be causing this issue. Elsa is also using .net 7 and automapper version 12.0.0.

There is no breaking changes from 7.0 to 7.1, can you reproduce this issue with a new project and share it with me? shiwei.liang@volosoft.com I will check it.