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
{{ message }}
This repository has been archived by the owner on Oct 31, 2024. It is now read-only.
Hi @oakad, thanks for your interest! We have forked rules_dotnet but have since heavily diverged. Our fork can be found at https://github.com/AFASResearch/rules_dotnet and contains more information about the different approach. Please note that our implementation is currently heavily tailored towards a single consumer (us) and and some information / code might be missing to get it working. If you are still interested I will be happy to assist you and provide you with a sample project. We do not work with Blazor ourselves but implementing rules for support should not be too difficult.
As I'm using dotnet core here, I will need to do some alterations to replace the bat files with something I can run on linux/mac.
The razor part amounts to several (4?) rules msbuild somehow decides to run without any explicit statements in the csproj file. But yes, it should not be something too exotic.
I have set up an example project in this PR: AFASResearch/rules_dotnet#6 and I have documented some sidenotes on the pull request. if you need anything else just give me a ping.
I am most interested to unify builds of my dotnet components with the rest of my projects (which happen to use Bazel throughout).
Unfortunately, rules_dotnet are barely usable. Does your implementation depends on rules_dotnet or is it completely unrelated?
Do you have any plans to support blazor project compilation? Those require an extra rule to process razor files.
The text was updated successfully, but these errors were encountered: