Re: When do you add new project?
madflatpicker01 My normal rule however is the same as for classes or a method. Make them as small as possible. I would rather have e.g. 10 small projects in a solution, each of which was dedicated to...
View ArticleRe: When do you add new project?
I suppose the answer to "when?" is a bit subjective in some ways.However, there is no rule that will satisfy all cases; experience, judgement, wisdom. All of those come from doing it and deciding that...
View ArticleRe: When do you add new project?
The project in question is a Web Site project, (not web app) and it does not produce a single DLL.I checked the precompiled /bin folder and there's over 750 dll and application extensions.To take your...
View ArticleRe: When do you add new project?
Dependency is easy; if the project produces a .DLL, or is a web service, for example, and you need to invoke it from another project then there is a dependency.For small projects (like one screen and a...
View ArticleRe: When do you add new project?
madflatpicker01you create multiple projects within the same solution when they have some dependency on each other.That's the part that is unclear. How do you clearly determine...
View ArticleRe: When do you add new project?
re: deciding factors; the solution file (.sln) isn't that big; you create multiple projects within the same solution when they have some dependency on each other. Something like: the data management...
View ArticleWhen do you add new project?
When you start a brand new project, Visual Studio creates a solution.Whenever I need to add extra functionality, I create a subfolder under the project and keep coding.In other words, I have Solution A...
View Article