Project structure [modified]
-
I normally have a structure like this solution ---bin ---projectA ------source files ---sub-solution ------projectB ---------source files however, many projects I seens are structured like this solution ---bin ---projectA ---projectB ---src ------source files of projectA and B -- modified at 7:42 Friday 10th November, 2006
-
I normally have a structure like this solution ---bin ---projectA ------source files ---sub-solution ------projectB ---------source files however, many projects I seens are structured like this solution ---bin ---projectA ---projectB ---src ------source files of projectA and B -- modified at 7:42 Friday 10th November, 2006
-
I normally have a structure like this solution ---bin ---projectA ------source files ---sub-solution ------projectB ---------source files however, many projects I seens are structured like this solution ---bin ---projectA ---projectB ---src ------source files of projectA and B -- modified at 7:42 Friday 10th November, 2006
that is really useful know....
Regards Ray "Je Suis Mort De Rire" Blogging @ Keratoconus Watch
-
I normally have a structure like this solution ---bin ---projectA ------source files ---sub-solution ------projectB ---------source files however, many projects I seens are structured like this solution ---bin ---projectA ---projectB ---src ------source files of projectA and B -- modified at 7:42 Friday 10th November, 2006
Thats really good to know I have seen projects like this Project bin Images Documents Classes Pages Usercontrols
"a fool will not learn from a wise man, but a wise man will learn from a fool" "It is hard to fail, but it is worse never to have tried to succeed." - Theodore Roosevelt "Success is going from failure to failure without losing your enthusiasm." - Winston Churchill
-
I normally have a structure like this solution ---bin ---projectA ------source files ---sub-solution ------projectB ---------source files however, many projects I seens are structured like this solution ---bin ---projectA ---projectB ---src ------source files of projectA and B -- modified at 7:42 Friday 10th November, 2006
You don't know how we manage our code, running around five concurrent projects (each made of hundreds of separate systems) that share some parts of the same code base, on at least 7 different platforms (with varying degrees of endianness) :sigh:
-- Help me! I'm turning into a grapefruit! Buzzwords!
-
I normally have a structure like this solution ---bin ---projectA ------source files ---sub-solution ------projectB ---------source files however, many projects I seens are structured like this solution ---bin ---projectA ---projectB ---src ------source files of projectA and B -- modified at 7:42 Friday 10th November, 2006
what about:
workspace
- projectA
-- inc
-- src
-- (res) - projectB
-- inc
-- src
...
- projectA
-
what about:
workspace
- projectA
-- inc
-- src
-- (res) - projectB
-- inc
-- src
...
- projectA
-
VAIO Blue wrote:
Are there any advantages on having a src folder
to locate the sources !? :rolleyes:
You don't know where to start ? ask a good friend
-
I normally have a structure like this solution ---bin ---projectA ------source files ---sub-solution ------projectB ---------source files however, many projects I seens are structured like this solution ---bin ---projectA ---projectB ---src ------source files of projectA and B -- modified at 7:42 Friday 10th November, 2006
This is the structure that we use:
[product]
\bin
\build_logs
\docs
\extras
\installer
\interop
\references
\src
\vendor
[product]
The main root folder for the particular product. This is the only part of the directory structure that changes, since the folder name is the product name or product code name.
bin
Used to hold the compiled project binaries when built through the build scripts.
build_logs
Used to hold the log files generated by the build scripts.
docs
Code generated/automated documentation (FxCop, NDoc, etc.).
extras
Utility applications used for developing or testing.
installer
The InstallShield project file and any additional resources required by the installer.
interop
Any .NET interop libraries required by the project.
references
Documents that reference websites and articles used.
src
Project source code, usually broken down into separate folders for the actual VS projects. The main solution file is located here.
vendor
Third-party binaries and source code, if available.
We are also looking at adding a "build_system" folder that would contain all of the build system related files, such as the build scripts and the CI project settings.
----------------------------- In just two days, tomorrow will be yesterday.
-
I normally have a structure like this solution ---bin ---projectA ------source files ---sub-solution ------projectB ---------source files however, many projects I seens are structured like this solution ---bin ---projectA ---projectB ---src ------source files of projectA and B -- modified at 7:42 Friday 10th November, 2006
I'll attempt to understand the question, if there was one... for C++ I use:
bin
obj
proj a
proj b
proj a
inc
src
res
proj b
inc
src
resAnd the reason is so that I can easily delete the obj directory and copy the bin directory, as well as copy the individual project source trees without being encumbered by the temp files. Which .NET doesn't allow me to do, as the temp obj dirs reside in the project folder and can't be moved. :mad:
What's in a sig? This statement is false. Build a bridge and get over it. ~ Chris Maunder