[Question]: Release Package: avoid Microsoft Dependency

[ralf-escher]

Question

Hi,

if we create a release via an AL-Go action, the nuspec of the package contains a dependency for Microsoft.Application and Microsoft.Platform. If we try to deploy this package within our environment this leads to errors, since the dependency will be resolved afterwards when we download the appropriate artifact.

Is there a possibility to avoid these dependency entries?

<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
    <metadata>
        <id>AL-Go-xxxx</id>
        <version>23.5.28.0</version>
        <title>BE-terna Manufacturing</title>
        <authors>BE-terna</authors>
        <repository type="git" url="https://github.com/BE-terna-OneBC/BC.BE-Manufacturing" />
        <dependencies>
            <dependency id="AL-Go-xxxx" version="18.0.0.0" />
            <dependency id="AL-Go-xxxx" version="23.7.6.0" />
            <dependency id="Microsoft.Application" version="23.0.0.0" />
            <dependency id="Microsoft.Platform" version="23.0.0.0" />
        </dependencies>
    </metadata>
    <files>
        <file src="BE-terna_BE-terna Manufacturing_23.5.28.0.app" target="BE-terna_BE-terna Manufacturing_23.5.28.0.app" />
    </files>
</package>

[freddydk]

I am working on the final implementation of the NuGet support and will cycle back to this question after this