Great structure, I have been, for a long time, following Fowlers old gist. And try to get everyone else to follow it :) The biggest issue is that people create the project in VS and if they let VS decide it will need some hands on.
Yes, itβs very similar and it inspired me a few years ago.
I didnβt invent nothing new π
By the way I have a PowerShell script to launch in the root folder when I create a new project to define the folders structure.
I think I should create VS extension.
What do you think?
IΒ΄d say an extension could be nice. But then again, its kind of good to fix it manually, at least in the start, to learn how to handle it (edit the .sln and so on)
A question, I usually put my yaml pipelines (CI/CD) in a folder named /build, where do you put yours ?
Great structure, I have been, for a long time, following Fowlers old gist. And try to get everyone else to follow it :) The biggest issue is that people create the project in VS and if they let VS decide it will need some hands on.
gist.github.com/davidfowl/ed756429...
Yes, itβs very similar and it inspired me a few years ago.
I didnβt invent nothing new π
By the way I have a PowerShell script to launch in the root folder when I create a new project to define the folders structure.
I think I should create VS extension.
What do you think?
IΒ΄d say an extension could be nice. But then again, its kind of good to fix it manually, at least in the start, to learn how to handle it (edit the .sln and so on)
A question, I usually put my yaml pipelines (CI/CD) in a folder named /build, where do you put yours ?
yes, in the build folder.
I see a lot of people with a folder called "deploy" for the same reason.