Faulty Code generation

[corelogiclayer-WI]

Describe the bug
When using the Modelbuilder with PAC Versions greater than 1.44.2, this leads to invalid code (see screenshot) while generating C# Models for my Custom API causing CS1061 to be thrown.

This is not a production bug of the build tools (yet?). I'm quite sure this will be an issue as soon as the build tools switch to later pac versions internally which will be a breaking szenario for my use case.

Fehler (aktiv) CS1061 "translateKeyResponse" enthält keine Definition für "Parameters", und es konnte keine zugängliche Parameters-Erweiterungsmethode gefunden werden, die ein erstes Argument vom Typ "translateKeyResponse" akzeptiert (möglicherweise fehlt eine using-Direktive oder ein Assemblyverweis). Plugin, RulesEvaluation.UnitTests
<>EarlyBoundTypes\Messages\translateKey.cs 112

Thank you very much for your support!
Best regards!

To Reproduce
Steps to reproduce the behavior:

1. Create a custom API
2. Generate C# Class Model with >1.44.2 und <= 1.44.2

Expected behavior
The Model generator should generate correct c# (v4.6.2) Sourcecode

Screenshots
Versions > 1.44.2

Versions <= 1.44.2

My BuilderSettings.json

My Custom API

Desktop (please complete the following information):

• Windows x64

[daryllabar]

Andrew Petrochuk (@petrochuk) this is a Dup of #35 and #31. Any chance it will ever get fixed?

[petrochuk]

@petrochuk this is a Dup of #35 and #31. Any chance it will ever get fixed?

I assigned it to Copilot first

[daryllabar]

@petrochuk this is a Dup of #35 and #31. Any chance it will ever get fixed?

I assigned it to Copilot first

As the creator of the Early Bound Generator, I heavily use this utility, and frequently have to do my own work arounds for things that are broken. Let me know if there is anything I can do. Thanks!

[frozzen10]

What about this issue? is it going to be resolved in the near future?
Thanks! 🙏

[corelogiclayer-WI]

Andrew Petrochuk (@petrochuk) Hi, this issue is still present in the latest release of the PAC Tools. We're still stuck with PAC 1.44.2 for this reason. What could i do to accellerate the progress?

[petrochuk]

@petrochuk Hi, this issue is still present in the latest release of the PAC Tools. We're still stuck with PAC 1.44.2 for this reason. What could i do to accellerate the progress?

This is clearly a bug. It might help to open support case with Microsoft referencing this discussion.

[corelogiclayer-WI]

Andrew Petrochuk (@petrochuk) ok, thank you! I'll create a bug using using my companys support plan. Is there a best practice how to reference this Bug / Share the link to your Investigation?

Thank you and best regards!

[corelogiclayer-WI]

I've created a ticket at Microsoft. The ticket ID is: 2602251410001370

Best regards

[corelogiclayer-WI]

A brief update from my side:
This topic is still ongoing and I am actively pushing the MS Support to provide a solution for this issue.

Best regards!

[corelogiclayer-WI]

Well - what should i say. This issue is now also present within the default PowerPlatform Build Tools for Azure DevOps.

The only solution I could come up with is dropping it entirely and using
dotnet tool install --global Microsoft.PowerApps.CLI.Tool --version 1.44.2
for now and rewrite all of my pipeline steps as a PS Script.

[daryllabar]

The early bound generator does resolve this, and does provide a nuget API that you can use in your pipelines