- ABP Framework version: v5.1.3
- UI type: MVC
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): Yes
I was having calling any methods for the Setting, Permission and Feature App service *.HttpApi.Client in a tiered solution because the individual *generate-proxy.json files were not marked as an 'embedded resource' and/or the following lines were not included in the *.HttpApi.Client project file.
<ItemGroup>
<EmbeddedResource Include="**\*generate-proxy.json" />
<Content Remove="**\*generate-proxy.json" />
</ItemGroup>
Looking at the various pro and non pro ABP modules I don't see any consistency as to how these generated proxy files are marked as embedded. Would it be possible to for this aspect of the framework to be corrected so it's consistent for when a new version of ABP is released so manual fixes are not necessary.
Thank you.
3 Answer(s)
-
0
Hi,
Configuring embedded resources is necessary for static proxies.
For the ABP modules, we configure here: https://github.com/abpframework/abp/blob/dev/common.props#L27-L29
May I ask what error do you get?
-
0
When you download the module source code, the CLI will automatically configures embedded resources: https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/ProjectBuilding/Building/Steps/MakeProxyJsonFileEmbeddedStep.cs#L7
-
0
Ok, thank you. We manually build the common.props file and did not have these includes in our powershell script.