Activities of "Spospisil"

Thank you. That was the issue.

Let me see if I can't figure out why it still does not work. Can you update the repo with your changes applied please?

Still does not resolve the issue. Did you try it after to changed the things you recommended?

Any update on this?

Thanks

I've added you to it.

Run the dbmigrator to create and seed the DB then run the tiered layers

What is you email address and I'll share a repo with you

Ok, thank you. We manually build the common.props file and did not have these includes in our powershell script.

The solution was to add the following lines to the project file(s) for SettingManagementHttpApiClient, FeatureManagementHttpApiClient and PermissionManagementHttpApiClient

<ItemGroup>
	<EmbeddedResource Include="**\*generate-proxy.json" />
	<Content Remove="**\*generate-proxy.json" />
</ItemGroup>

We run our solutions with full source code. If I step through the code the issue is happening on the highlighted (red box) line in the ClientProxyBase.cs class as shown in the below screenshot. The value of 'methodUniqueName' is:

Volo.Abp.FeatureManagement.IFeatureAppService.GetAsync.System.String-System.String

How do these values get loaded into the ClientProxyApiDescriptionFinder collection as this value is not being loaded into it?

Hi,

As highlighted below, the ABP Framework documentation does not not exclude a tiered solution from this framework feature. Could you please updated your documentation accordingly so that other customers do not waste their time exploring how to do this as the documentation does not indicate that this only works for a non tiered solution?

Thanks.