njlr

 

I updated the repo to the latest `next` but unfortunately the issue persists. You can see the diff report here: https://github.com/njlr/rules-dotnet-issue-296/actions/runs/2965784764

Like this? ```bash $ bazel clean $ bazel build --incompatible_strict_action_env //... $ sha256sum ./bazel-bin/bundle.tar 22b8484107937a16e5219f685159e3c54aa192268aea778efa60cda717d8648f ./bazel-bin/bundle.tar $ bazel clean $ bazel build --incompatible_strict_action_env //... $ sha256sum ./bazel-bin/bundle.tar 4cb0f09b7e894a97a19acca6e01751883ecdeca64130bc950676f55e336b6c50 ./bazel-bin/bundle.tar $...

> I figured out what the issue is. There are absolute paths embedded into the DLLs. We need to use the --pathmap compiler option to make the paths relative and...

Some progress... ```starlark genrule( name = "test", outs = [ "out.txt" ], cmd = "echo \"$(DOTNET_BIN)\" > $@", toolchains = [ "@dotnet_toolchains//:resolved_toolchain", ], ) ``` ```bash cat ./bazel-bin/out.txt external/dotnet_x86_64-unknown-linux-gnu/dotnet ```

My perspective as (primarily) an F# developer is a little different. My ideal scenario would be this: - Bazel build description acts as ultimate source-of-truth - Bazel rules do not...

Yep, renaming it works. Thank you! I have renamed the title of this issue to reflect the real issue.

For example to deploy an AWS Lambda it is necessary to build a `.zip` that contains the .NET library and any dependencies. This can be done outside Bazel with `dotnet...

Thanks for your help. Unfortunately I ran into 2 issues: 1. `pkg_zip` does not have an `include_runfiles` argument 2. using `pkg_tar`, the set of runfiles seems to be too big,...

Thanks @purkhusid. I was thinking a design like this could work well: ```starlark fsharp_library( name = "foo", srcs = [ "Library.fs", ], ) dotnet_publish( name = "foo_pub", lib = ":foo",...