Activities of "viswajwalith"

abp generate-proxy -t js -m userTaskService -url HttpApi.Host'URL

Finally we are able to see some progress (not 100%) able to run the generate proxy

but still not able to see the the new service related proxies in the main solution(base problem)

still missing in definitions as well

Hi,

I think it should work if you use it to generate client proxy files.

I am also not sure tried many ways, what do u suggest now?

/api/abp/api-definitionapi-definition

If I get the definition for individual micro service the Module is showing up

Hi,

Module name: app is invalid

You need to specify the service(module) name. you can find it in the /api/abp/api-definitionapi-definition endpoint.

No project file found in the directory. The working directory must have a Web project file

You need to run the command in the web project directory of the service

Hi It Seems some issue with main definition itself, not able to see newly added micro service under modules

Hi,

You need to manually generate the proxy using ClI: https://docs.abp.io/en/abp/latest/CLI#generate-proxy

Hi, We already tried this but getting the below errors

Also the suprise is without doing anything the Proxies got generated for some other services, means Proxies generated for XYZ service but same is not getting generated for PQR service.

Hi,

Yes, If there is a project dependency, then it is required

Hummm, ok. let me try that and update you accordingly.

do u think just sharing the web (UI) project works for you to replicate the issue?

No, it's not enough.

It has couple of dependent projects

Did you also upgrade the dependent projects?

do you think it is necessary to update all other services as we are following micro service based architecture, those are just Rest full services and the UI layer has nothing to do with that technology stack/version right?

But I have a question on one of the Project reference

	        <ProjectReference Include="..\..\..\..\services\volo.filemanagement\src\Volo.FileManagement.HttpApi.Client\Volo.FileManagement.HttpApi.Client.csproj" />

do you think all kind of services also need to be upgraded?

Hi,

Could you share a project that can reproduce the problem? shiwei.liang@volosoft.com I will check it.

It has couple of dependent projects, do u think just sharing the web (UI) project works for you to replicate the issue?

Hi,

You should make sure all abp packages upgrade to 7.1.1

BTW, ABP 7.1.1 is based on NET 7.0, you need to also upgrade all Microsoft's packages.

You can check the migration guide: https://docs.abp.io/en/commercial/latest/migration-guides/index

When you done, please run dotnet clean & dotnet build command.

Hi As I mentioned earlier I already tried with all packages with 7.1.1 anyhow I did tried again and obviously .net version is 7

still getting the below error

2023-04-11 13:13:57.474 +05:30 [FTL] Exceego.EHSWatch.AppV3.Web terminated unexpectedly! Volo.Abp.AbpInitializationException: An error occurred during ConfigureServicesAsync phase of the module Volo.Abp.AspNetCore.Mvc.AbpAspNetCoreMvcModule, Volo.Abp.AspNetCore.Mvc, Version=7.1.1.0, Culture=neutral, PublicKeyToken=null. See the inner exception for details. ---> System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Could not load type 'Volo.Abp.EventBus.ILocalEventHandler1' from assembly 'Volo.Abp.EventBus, Version=7.1.1.0, Culture=neutral, PublicKeyToken=null'. at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module) at Microsoft.AspNetCore.Mvc.Controllers.ControllerFeatureProvider.PopulateFeature(IEnumerable1 parts, ControllerFeature feature) at Microsoft.AspNetCore.Mvc.ApplicationParts.ApplicationPartManager.PopulateFeature[TFeature](TFeature feature) at Microsoft.Extensions.DependencyInjection.MvcCoreMvcBuilderExtensions.AddControllersAsServices(IMvcBuilder builder) at Volo.Abp.AspNetCore.Mvc.AbpAspNetCoreMvcModule.ConfigureServices(ServiceConfigurationContext context) at Volo.Abp.Modularity.AbpModule.ConfigureServicesAsync(ServiceConfigurationContext context) at Volo.Abp.AbpApplicationBase.ConfigureServicesAsync() System.TypeLoadException: Could not load type 'Volo.Abp.EventBus.ILocalEventHandler1' from assembly 'Volo.Abp.EventBus, Version=7.1.1.0, Culture=neutral, PublicKeyToken=null'. --- End of inner exception stack trace --- at Volo.Abp.AbpApplicationBase.ConfigureServicesAsync() at Volo.Abp.AbpApplicationFactory.CreateAsync[TStartupModule](IServiceCollection services, Action1 optionsAction) at Microsoft.Extensions.DependencyInjection.ServiceCollectionApplicationExtensions.AddApplicationAsync[TStartupModule](IServiceCollection services, Action1 optionsAction) at Microsoft.Extensions.DependencyInjection.WebApplicationBuilderExtensions.AddApplicationAsync[TStartupModule](WebApplicationBuilder builder, Action1 optionsAction) at Exceego.EHSWatch.AppV3.Web.Program.Main(String[] args) in C:\Official\EHSWatchV3\repo\EHSWatch_AppV3\apps\web\src\Exceego.EHSWatch.AppV3.Web\Program.cs:line 29

Let me know if anything is missing

If I create the Micro Service solution once again and then add the service, it worked. but if this is the case we may the issue if we plan to add the micro service after some releases right