We are using OutSystems 11.7.2, so the latest compatible version is 5.0.1. We are facing a similar situation with Ultimate PDF version 5.0.1. If so, I would assume they are seeing that the DLL doesn't need to be updated because the 4.5.1 version is what is currently installed in the extension espace in IIS. What I don't know is does OutSystems use this when they compile the extension during deployment. From my understanding of NuGet, that is the minimum version the package can accept. I also observed your NuGet "nfig" file had the 4.5.1 in it.
What I did notice is the Tasks Extension comes from a NuGet package and the new DLL comes from the 4.5.2 or greater version. In our case and probably Nelson's case, the one that doesn't have the new ValueTask class. It keeps the original DLL that came with the first install of the application. But when I publish the solution to the server, that DLL doesn't publish.
When I do that, I get a new (v 4.2.0.1) DLL in the bin folder. I opened your extension in Integration Studio and recompiled it. That is the part that I don't quite understand. Replying to Leonardo Fernandes' comment on 12:07:03
0 kommentar(er)
