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
In the dot net world, the csproj files are required by most of the IDEs and Tools, e.g. Visual Studio or the DotNet CLI.
If I'm using those tools for development, I never can be sure that the Bazel Rule will generate the same as in my dev IDE, which makes it useless for me in Enterprise Projects.
I suggest you'll find a way to use the csproj to configure the rule or even better, make the rule really using the underlying toolset so we have to deference between Bazel builds and csproj builds.
The text was updated successfully, but these errors were encountered:
This use case would probably be better handled by issue #12 instead. Generating a csproj from the bazel rule would be a better direction than the other way around.
In the dot net world, the csproj files are required by most of the IDEs and Tools, e.g. Visual Studio or the DotNet CLI.
If I'm using those tools for development, I never can be sure that the Bazel Rule will generate the same as in my dev IDE, which makes it useless for me in Enterprise Projects.
I suggest you'll find a way to use the csproj to configure the rule or even better, make the rule really using the underlying toolset so we have to deference between Bazel builds and csproj builds.
The text was updated successfully, but these errors were encountered: