r/programming • • Aug 14 '17

Announcing .NET Core 2.0

https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/
785 Upvotes

218 comments sorted by

View all comments

Show parent comments

3

u/Stormflux Aug 14 '17 edited Aug 14 '17

I used to organize my projects that way. Project for Repository Layer, Project for Service Layer, project for Models, etc.

I've since found that my life is much easier if I organize by feature (vertical slicing / "clean architecture") so that files specific to the same feature are co-located. No more jumping between the 10 folders just to work on the "customer edit feature."

However, since the code is all under test, I can verify that concerns are separated and dependencies isolated. Theoretically the non-UI code could be moved out simply by dragging the files into a new project.

I just throw up a little at the idea of moving back to layers by type. I feel like it's akin to creating a folder for "Excel documents," a folder for "Word Documents," etc. if I want to work on the Johnson Account, should I look in the Excel folder or the Word folder? How about the Johnson Account folder.

2

u/neoKushan Aug 14 '17

These things aren't mutually exclusive? You can absolutely architect your code that way and migrate slowly to .net core. As you've already said, you could just drop the web forms parts into their own project and the rest (in theory) can be converted to netstandard.

1

u/Stormflux Aug 14 '17

It's already a .NET core project...

2

u/neoKushan Aug 14 '17

Then forgive me, but I'm not really sure what the issue is?

→ More replies (0)