Last post Apr 26, 2018 02:24 AM by Edward Z
Apr 25, 2018 02:44 PM|GregE123456|LINK
I'm trying to setup a simple architecture layer diagram to validate that we don't break our layering rules by using namespaces/dll's from incorrect layers.
I setup a simple solution that has a console app, and 4 dll's (all using .Net Core). The console app calls into Dll1, Dll1 calls into Dll2, Dll2 calls into Dll3, etc. Then I setup a layer diagram to enforce this layering and try to have the console app call
into Dll 4 and expected to get an error; however, I don't.
If I change this to use a windows form app (instead of the .net core console app) and change all the dll's to be .net standard, then I do get the error enforcing the layer diagram.
I've tried adding the Microsoft.DependencyValidation.Analyzers NuGet package to the .net core console app, but that still doesn't work. Is this a problem in .Net Core? Or something I'm missing?
Also tried doing another test with all .net core but used an MVC app instead of a console app. I get the following error when building the solution (and the dependency layer diagram doesn't go instead the MVC app). CSC : warning DV2001: The project
does not reference any Dependency Validation diagrams or referenced diagrams are not valid. Dependency validation will not be performed.
Apr 25, 2018 03:03 PM|bruce (sqlwork.com)|LINK
you should open an issue:
with visual studio dropping diagram support, not sure how supported this feature is.
Apr 25, 2018 03:26 PM|GregE123456|LINK
Visual Studio is dropping support for Dependency Validation Diagrams?
Apr 26, 2018 02:24 AM|Edward Z|LINK
Your issue is related with Architecture Dependency and I found you have submit your issue on github below,
I would suggest you wait for the response from them.