Skip to content

Commit

Permalink
[#33] update for Solution and Project structure
Browse files Browse the repository at this point in the history
  • Loading branch information
nickwesselman committed Oct 22, 2019
1 parent 219a08a commit 239e9ba
Show file tree
Hide file tree
Showing 8 changed files with 7 additions and 28 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file removed helix/principles/visual-studio/_static/image14.png
Binary file not shown.
Binary file removed helix/principles/visual-studio/_static/image15.png
Binary file not shown.
Binary file removed helix/principles/visual-studio/_static/image16.png
Binary file not shown.
13 changes: 4 additions & 9 deletions helix/principles/visual-studio/projects.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,17 +10,12 @@ connection to a module – and never by type.
Projects are grouped together in a solution by the layer and module to
which they belong.

.. admonition:: Habitat Example
.. admonition:: Sitecore Helix Examples

.. figure:: _static/image16.png
:scale: 75%
.. figure:: _static/basic-company-navigation-module.png

Figure: Project grouping. Please note that even though the
SpecFlow (see :doc:`/devops/testing/integration-testing`) projects
might test the individual features, they are grouped with the
Sitecore.Habitat project because they depend on
the entire running website, and therefore the Sitecore.Habitat
module.
Figure: Navigation module in Helix Basic Company with website,
TDS, and unit test Visual Studio projects.

A project, and assembly, should be named in a namespace-like fashion
with:
Expand Down
22 changes: 3 additions & 19 deletions helix/principles/visual-studio/solutions.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,24 +7,8 @@ folders for Project, Feature and Foundation layers and separate solution
folders for each module. If there are any additional grouping of
modules, these can have their own solution folders.

The VS solution can have other solution folders (beyond Project, Feature
and Foundation) in the root of the solution, to increase discoverability
for specific files. However, these folders will never represent new
layers and must not contain any module projects.
.. admonition:: Sitecore Helix Examples

.. admonition:: Habitat Example
.. figure:: _static/basic-company-solution-structure.png

.. figure:: _static/image13.png
:scale: 75%

Figure: Habitat solution with feature and foundation modules

.. figure:: _static/image14.png
:scale: 75%

Figure: Demo solution with specific feature and foundation modules

.. figure:: _static/image15.png
:scale: 75%

Figure: Simple demo solution without feature or foundation modules
Figure: Helix Basic Company solution with Project, Feature, and Foundation modules

0 comments on commit 239e9ba

Please sign in to comment.