The issue is back. Please refer the issue and you will understand what I am asking.
This probably happened with the latest update of Abp Studio.
In Brief I have 2 mciroservice and when i try to generate proxy for one microservice it errors out stating the other microservice
angular>abp generate-proxy -t ng -url http://localhost:44319 -m artificialintelligence
[19:50:38 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli
[19:50:39 WRN] "@abp/ng.schematics" version is lower than ABP Cli version.
[Invalid Module] Backend module "document" does not exist in API definition.
I am using the Microservice Template to build. And I am using the latest version.
Issue #1 : When I try to publish a a Distributed Event from a Domain Sevice
public class DocumentEventPublisher : DomainService
private readonly IDistributedEventBus _eventBus;
public DocumentEventPublisher(IDistributedEventBus eventBus)
{
_eventBus = eventBus;
}
public async Task PublishSucceededAsync(AnalyzeOperationSucceededEventEto input)
{
await _eventBus.PublishAsync(input);
}
The event doesn't publish meaning I try to log using DistributedEventSentHandler and I don't get a hit. However I could see an entry in Outbox table
But if I use a background job and try to publish it works fine.
What are the things I should look for to be able to publish without the need of a background job.
Issue #2 : I am unable to listen to the even from a different microservice. I did everything that was required , e.g. I create a similar Eto in the mciroservice and made sure the event name is correc. Something like the below :
public class DocumentAnalyzedEventHandler : IDistributedEventHandler<AnalyzeOperationSucceededEventEto>,ITransientDependency
I didn't want to write the whole code but i hope this should be enough to help you understand my issue
Why are you guys locking out the post so early. You should keep it at aleast 2 weeks. I was out fo station so couldn't find a chance to look at it. Your response :
We’re currently working on a fix, which will be included in the upcoming release. In the meantime, I can share the updated file that resolves the issue directly with you via drive. https://drive.google.com/drive/folders/1MHQSeIa6rOw4rAcXAnq11U2XLfFYjTc5?usp=drive_link. If you replace the .suite folder under your angular app directory, you will be able to work around the issue.
We appreciate your patience and cooperation as we work to improve the experience. Let us know if you have any further questions!
I want to understand where exactly i need to put this as I don't see any .suite folder in my angular app directory. Please provide clear screenshots and let me know
I am having the exact same issue as https://abp.io/support/questions/9043/Angular-proxy-generation-error
This is the first time I am using the command line to generate proxy and having the same issue as mentioned above.
I did see the proxy generation file has a different service name as that of RemoteServiceConsts .
e.g. in the Proxy Generated by Abp Suite have documentService as the module name where as in the RemoteServiceConsts file the service name is document.
I deleted the proxy generated json file and was able to create the proxies, but the problem is lot of files are getting created outside the controller folder which is causing major issues.
So the file generation through command line and AbpSuite are different which is causing the issue.
Please provide a solution.
I am trying to use the Pre Defined Events for Entity following this link : https://abp.io/docs/latest/framework/infrastructure/event-bus/distributed?_redirected=B8ABF606AA1BDF5C629883DF1061649A#pre-defined-events.
I tried this code in the file management module :
ConfigureDistributedEntityEvent();
private void ConfigureDistributedEntityEvent()
{
Configure<AbpDistributedEntityEventOptions>(options =>
{
options.AutoEventSelectors.AddAll();
});
}
My expectation was the message should start showing up in the Eventoutbox table whenevver I add a file or delete a file.
However I get some exception which doesn't appear either on Log file or Audit log or anywhere. But when I comment the code everything works fine.
Is there any other settings I have to make to see the messages in the eventbox.
Note : I am not asking about Synchronizing yet as the first step is to be able to see the meesges in the outbox.
I started a new micro service solution with a new installation of everything and using 9.1
I am encountering the below issue while generating the UI for angular using Abp Suite :
025-03-11 22:03:34.292 -07:00 [INF] Running the Angular Schematics command:
node run-schematics.mjs "C:/SourceCode/xxxServices/apps/angular/.suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" app-nolayers-pro xxxServices.AIService "C:/SourceCode/xxxServices/services/ai/.suite/entities/TestPage.json" "C:/SourceCode/xxxServices/apps/angular"
2025-03-11 22:03:36.033 -07:00 [INF] Angular Schematics command failed.
C:\SourceCode\xxxServices\apps\angular\.suite\schematics\node_modules\execa\lib\error.js:60
error = new Error(message);
^
Error: Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-nolayers-pro --target xxxServices.AIService --source C:/SourceCode/xxxServices/services/ai/.suite/entities/TestPage.json
[1m[31m[Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.[39m[22m
at makeError (C:\SourceCode\xxxServices\apps\angular\.suite\schematics\node_modules\execa\lib\error.js:60:11)
at handlePromise (C:\SourceCode\xxxServices\apps\angular\.suite\schematics\node_modules\execa\index.js:118:26)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async file:///C:/SourceCode/xxxServices/apps/angular/.suite/schematics/run-schematics.mjs:6:20 {
shortMessage: 'Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-nolayers-pro --target xxxServices.AIService --source C:/SourceCode/xxxServices/services/ai/.suite/entities/TestPage.json',
command: '.suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-nolayers-pro --target xxxServices.AIService --source C:/SourceCode/xxxServices/services/ai/.suite/entities/TestPage.json',
escapedCommand: '".suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" --template app-nolayers-pro --target xxxServices.AIService --source "C:/SourceCode/xxxServices/services/ai/.suite/entities/TestPage.json"',
exitCode: 1,
signal: undefined,
signalDescription: undefined,
stdout: '',
stderr: '\x1B[1m\x1B[31m[Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.\x1B[39m\x1B[22m',
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
Node.js v22.14.0
After I upgrade from 9.0 to 9.1 I get the following errors and its all over the place.
./node_modules/@volosoft/ngx-lepton-x/fesm2022/volosoft-ngx-lepton-x.mjs:1030:49-70 - Error: export 'provideAppInitializer' (imported as 'provideAppInitializer') was not found in '
I deleted node+modules folder and yarn.lock file but no luck.
What should i do ?
I am reopening this issue again via a different ticket as it was closed .
The example you provided I saaw is you tried with only 1 new micro service. If you read my issue carefully , the issue comes in when you go and generate the proxies for the second microservice.
So try to generate the proxies for the second microservice and check.
By the way , I tried your solution and the same issue exists.
ABP Framework version: v9.0.2
UI Type: Angular
Tiered (for MVC) or Auth Server Separated (for Angular): yes
I created 2 Microservice and using the AbpStudio I tried creating proxy for the first microservice and it ran perfectly fine. However when I tried to run the proxy for the second microservice it gives me the below error :;
[Invalid Module] Backend module "myfirstmodulename" does not exist in API definition.
The problem is why its referring to the previous microservice name when I am generating the proxy for the second microservice
