Mapperly - must have an implementation part because it has accessibility modifiers. #1431
Replies: 5 comments 7 replies
|
It might be these two lines. How can Mapperly differ these methods. The have the same signature. So there is no way for Mapperly to know whom to choose. public partial List MapBLLRequestToDomain(List request);
public partial List MapDomainRequestToBLL(List request); |
|
What compiler version are you using in your docker build? To output your compiler version put |
|
Has anybody found the answer to this issue? I am getting the same error |
|
Not sure this is directly related to OP but maybe the others, i've gotten this issue when analyzers is getting blocked by AppLocker (or similar tooling), generally the builds run fine though. If this indeed is the case for you the solution is for your admins to add a AppLocker rule that either whitelist (ordered by the best to least good solution from a security standpoint):
Paths might be good enough depending on your threat model and rules, and if you have a good curated internal nuget registry the risk is mitigated somewhat. |

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I have a .net framework 4.6.1 Application, and im using few c# libraries which are targeting .net standard 2.0, Im using Mapperly to map my domain to External DTOS.
I am facing an issue when im trying to run my code in a docker container(windows), which im not able to get any build errors in my local Visual studio.
My Sample Implementation of this is
this mapper is implemented in one library and is used in multiple libraries in the application, now when i build this i get the error -
All reactions