Our framework build files (like net472.BUILD) don't have dependencies set up correctly. They were hacked up a bit to avoid telling Bazel about .NET Framework's circular dependencies.
We need to fix this. I know how to do it I just haven't had time to sit down and fix the generator.
We will break the cycles in deps, but create alias targets.
For example, @net472//:System.Xml will depend on @net472//:System.Data.SqlXml-somesuffixhere, but @net472//:System.Data.SqlXml-somesuffixhere won't dep on @net472//:System.Xml (even though it does in a CLR sense). We will do alias("System.Data.SqlXml", actual = ":System.Xml") so that when you dep on @net472//:System.Data.SqlXml all the right things happen.
Our framework build files (like
net472.BUILD) don't have dependencies set up correctly. They were hacked up a bit to avoid telling Bazel about .NET Framework's circular dependencies.We need to fix this. I know how to do it I just haven't had time to sit down and fix the generator.
We will break the cycles in
deps, but createaliastargets.For example,
@net472//:System.Xmlwill depend on@net472//:System.Data.SqlXml-somesuffixhere, but@net472//:System.Data.SqlXml-somesuffixherewon't dep on@net472//:System.Xml(even though it does in a CLR sense). We will doalias("System.Data.SqlXml", actual = ":System.Xml")so that when you dep on@net472//:System.Data.SqlXmlall the right things happen.