You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the Azure.Bicep.MSBuild package and its associated command line package to compile one of our projects which has bicep files into its associated ARM templates. We are noting during dotnet publish that the compiled json files are not being copied to the publication directory. I've found a couple of issues on here regarding publishing with bicep being wonky and I think I have found another case where this does not work if you are attempting to save time by specifying --no-build.
To Reproduce
Steps to reproduce the behavior:
Compile solution with a csproj that references bicep msbuild package and compiles a json file.
Try to dotnet publish (with --no-build) the individual project after sln build, observe that the json files are not present in the output directory.
Additional context
We've worked around the problem in the meantime by removing --no-build but I want to ensure we avoid any redundant build steps during publication given the solution has already been pre-built.
The text was updated successfully, but these errors were encountered:
Bicep version
0.23.1
Describe the bug
We have a build pipeline that does the following-
dotnet build someproject.sln
dotnet publish <project> --no-build --no-restore -out ./somedir
We use the Azure.Bicep.MSBuild package and its associated command line package to compile one of our projects which has bicep files into its associated ARM templates. We are noting during dotnet publish that the compiled json files are not being copied to the publication directory. I've found a couple of issues on here regarding publishing with bicep being wonky and I think I have found another case where this does not work if you are attempting to save time by specifying --no-build.
To Reproduce
Steps to reproduce the behavior:
Compile solution with a csproj that references bicep msbuild package and compiles a json file.
Try to dotnet publish (with --no-build) the individual project after sln build, observe that the json files are not present in the output directory.
Additional context
We've worked around the problem in the meantime by removing --no-build but I want to ensure we avoid any redundant build steps during publication given the solution has already been pre-built.
The text was updated successfully, but these errors were encountered: