I don't know whether this solve it for mdframe but I changed the options.CustomSchemaIds(x => x. FullName) which resolved the issue with not being able to run the server code but, after doing an nswag refresh I am getting dozens of compilation errors when doing an npm start.
This fix allowed me to start the server app but after doing a nswag refresh, I am now getting dozens of errors when I do an npm start.
I posted a little too quickly as I found the solution at https://stackoverflow.com/questions/46071513/swagger-error-conflicting-schemaids-duplicate-schemaids-detected-for-types-a-a
I changed
options.CustomSchemaIds(SchemaIdSelector);
to
options.CustomSchemaIds(x => x.FullName);
in the SwaggerExtension CustomDefaultSchemaIdSelector
and I no longer get the error
I am just selecting the US flag and allowing the defaults. I changed the language to the English flag and got the same thing. The Dto that I pass to the "ExportToFile" has all the numberic fields defined as decimal or decimal?
Thanks. I was finally able to see the subscription using the UI and get the webhook to publish the data to a remote site. I used https://webhook.site which is a great site for testing webhooks. I am actually not sure what it was that finally caused the data to publish. It may have been the adding of the publish within a unit of work using clause -- _unitOfWorkManager.Current.SetTenantId
No the webhook would be received by a third party application. I think I have figured out the calling of the Publish to initiate the webhook but the webhook is not being received at the destination uri of the subscriber. I have also not been able to see any of my webhooks on the client angular side; I created the subscription by adding a record to the database.
