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 was archived by the owner on Apr 11, 2020. It is now read-only.
I like to structure the folders of my code by feature/module, rather than technology. I don't like bouncing around between different folders like controllers, view models, views, etc. when on big projects.
I'm getting nesting issues while using Visual Studio and the RC2 Build that I got from the DevIntersection ASP.NET Core workshop with Damian and Glenn. It's not looking at the extension for nesting, it just nests items with the same name. To me, that seems wrong unless I'm not thinking of a certain scenario.
I tried this with the ASP.NET 4.x VS tooling and I do not have this problem.
Here's a screenshot:
Let me know if you need more info. Thanks.
The text was updated successfully, but these errors were encountered:
I like to structure the folders of my code by feature/module, rather than technology. I don't like bouncing around between different folders like controllers, view models, views, etc. when on big projects.
I'm getting nesting issues while using Visual Studio and the RC2 Build that I got from the DevIntersection ASP.NET Core workshop with Damian and Glenn. It's not looking at the extension for nesting, it just nests items with the same name. To me, that seems wrong unless I'm not thinking of a certain scenario.
I tried this with the ASP.NET 4.x VS tooling and I do not have this problem.
Here's a screenshot:

Let me know if you need more info. Thanks.
The text was updated successfully, but these errors were encountered: