Starts in:
1 DAY
1 HR
1 MIN
32 SEC
Starts in:
1 D
1 H
1 M
32 S

Activities of "jim"

I did tried to rename to AllotShareAsync and now works fine. So the Async Keyword plays an important role here.

Many Thanks. Jimwell

Hello, I have an issue with generating a client proxy. Every time I need to regenerate a static client proxy using the command: abp generate-proxy -t csharp -m myService -u https://localhost:44769 --without-contracts an issue occurs. I don't understand why it happens, and I don't have any idea how to resolve it.

  • ABP Framework version: v7.2.2
  • UI type: Blazor
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes
  • Exception message and stack trace: Method 'AllotShare' cannot implement method from interface 'CmvPoint.ShareholderService.ShareTransactions.IShareTransactionAppService'. Return type should be 'System.Threading.Tasks.Task<CmvPoint.ShareholderService.ShareTransactions.ShareTransactionDto>'.

Inner Exception

Don't have any inner exception.

  • Steps to reproduce the issue:"

The steps I've taken:

  1. Create the IShareTransactionAppService
  2. Added Task<ShareTransactionDto> AllotShare(AllotShareInputDto input); on my IShareTransactionAppService
  3. Generate Client proxy using command mentioned above

For the reference: I've attached the image which is the IShareTransactionAppService

IShareTransactionAppService

ShareTransactionCliehntProxy.Generated.cs

Highlighted Issue

Hi

Thank you for your prompt response to my previous inquiry regarding the issue I encountered with Localization. I appreciate your willingness to assist.

Despite the fact that I recognize how crucial it is to make the source code available for debugging, I want to inform you that my project's source code is restricted.

If so, Are you able to have a short time meeting for remote session instead? or can you provide an example implementation on it with WPF, and send me through jimwellbuot@gmail.com email? Thank you!

Have a great day!

Hello maliming, Can we have a remote instead?

Hello everyone, I have question regarding on application of Localization on my Wpf client. I have microservices, which my wpf client connected through client proxy. I wanted to reuse my localization on my shared domain on one of my service to put it out on my wpf application. Do you have any article explaining oh how can we utilized it? Thanks in advance.

  • ABP Framework version: v7.0.2
  • UI type: WPF
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes
  • Exception message and stack trace: An exception was thrown while activating Microsoft.Extensions.Localization.StringLocalizer1 [[CmvPoint.ContactService.Localization.ContactServiceResource, CmvPoint.ContactService.Domain.Shared, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]] -> Volo.Abp.Localization.AbpStringLocalizerFactory -> Volo.Abp.AspNetCore.Mvc.Client.RemoteExternalLocalizationStore.

Inner Exception

Autofac.Core.DependencyResolutionException: None of the constructors found with 'Autofac.Core.Activators.Reflection.DefaultConstructorFinder' on type 'Volo.Abp.AspNetCore.Mvc.Client.RemoteExternalLocalizationStore' can be invoked with the available services and parameters: Cannot resolve parameter 'Volo.Abp.AspNetCore.Mvc.Client.ICachedApplicationConfigurationClient configurationClient' of constructor 'Void .ctor(Volo.Abp.AspNetCore.Mvc.Client.ICachedApplicationConfigurationClient, Microsoft.Extensions.Options.IOptions1[Volo.Abp.Localization.AbpLocalizationOptions])'. at Autofac.Core.Activators.Reflection.ReflectionActivator.<>c__DisplayClass12_0.<UseSingleConstructorActivation>b__0(ResolveRequestContext ctxt, Action1 next) at Autofac.Core.Resolving.Middleware.DelegateMiddleware.Execute(ResolveRequestContext context, Action1 next) at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt) at Autofac.Core.Resolving.Middleware.DisposalTrackingMiddleware.Execute(ResolveRequestContext context, Action1 next) at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt) at Autofac.Builder.RegistrationBuilder3.<>c__DisplayClass41_0.<PropertiesAutowired>b__0(ResolveRequestContext ctxt, Action1 next) at Autofac.Core.Resolving.Middleware.DelegateMiddleware.Execute(ResolveRequestContext context, Action1 next) at Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt) at Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action1 next)

  • Steps to reproduce the issue:"

The steps I've taken:

  1. Referenced my Service Domain Shared to my WPF Application
  2. Added typeof(AbpLocalizationModule) on my WPF Module
  3. Configure AbpLocalization Option on my ConfigureServices function: Configure<AbpLocalizationOptions>(options => { options.Resources .Add<ContactServiceResource>("en"); });

*** Note that the ContactServiceResource Referenced to my Contact Service on my Abp.

  1. Then initialized a IStringLocalizer on my view Model

private IStringLocalizer<ContactServiceResource> _localizer => GetService<IStringLocalizer<ContactServiceResource>>();

  1. Then use like var test = _localizer["HelloWorld"];

Hello, Yes sure, I'll send you an invitation.

Hello,

We Already been configured the AddStaticHttpClientProxies and we also had the

In the meanwhile, here is globalServicegenerate-proxy.json. This is too long to put here, so I've uploaded it to Google Drive instead.

https://drive.google.com/file/d/1TQV3-oQe4Pry6DYTYFgqMsKAkPV4Fa3T/view?usp=sharing

Thank You!

Hello, Jeff and I are team members, however he is now unable to respond.

Here is the appsettings.json file

{
  "ConnectionStrings": {
    "ProductService": "mongodb://root:root123@localhost:27017/CMVPoint_ProductService?authSource=admin"
  },
  "RemoteServices": {
    "Default": {
      "BaseUrl": "https://localhost:44325/"
    }
  },
  "IdentityServer": {
    "AuthUri": "https://localhost:44322",
    "GatewayUri": "https://localhost:44325",
    "BrowserPort": 54955,
    "Oidc": {
      "RedirectUri": "http://127.0.0.1:54955/signin-oidc",
      "ClientId": "CmvPoint_WpfClient",
      "ClientSecret": "1q2w3e*",
      "Scope": "openid profile email ProductService AdministrationService IdentityService ShareholderService GlobalService"
    }
  }
}

Hi gterdem,

I've submitted a community-article-requiest on Github, but I think it takes time to be noticed by the team? because until now there is no reply on this. But anyway, Is there any possible to add another Data Access for Abp? I want to utilized the Xpo from DevExpress which is required by my client. My problem here is that I'm having a hard times of manually configure and build a context of it. Is there any possible for this? can you please give me some insight on this. Thank you.

I tried to copy the implementation of MongoDb Integration, but everything seems to fail. I plan to just add another Data Access layer and use DevExpress's Xpo ORM.

Showing 1 to 10 of 11 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06