3 replies to this topic

[chrisbregg]

I recently came across a list of proposed achievements for visual studio. One of the achievements is "The Organizer – Created a Solution with more than 50 projects" and it occurred to me that I haven't really ever needed to create a solution with 2 projects, let alone 50. I can't for the life of me figure out why anyone would need to have a large number of projects in a single solution.

Does anyone have much experience with this? What is the purpose?

[zeroradius]

lol, it's a joke man. I love the post thou

Quote

The Engineer – Killed a zombie with The Wrench

[chrisbregg]

I know it's a joke, but I do seriously wonder what good multi project solutions are.

[LuthfiHakim]

Do you mean a group of projects? Well, it's not rare that a software project consists of several modules. For example, a project of mine consists of 4 "projects".

1. main executable
2. a dll containing important codes, to make it easier to update the codes
3. registration key deployer, a small executable to make it easy to store registration ke in customer's PC.
4. registration key generator and verifier, to generate registraton key, store it inside key deployer, and email it.

Now that's for one tiny shareware. I have written a project containing around 10-15 projects. only about 3 of them that is totally different, the rest is nearly identical in behavior (the only difference is some texts and internal sql commands). And this is quite common for projects with plug-in approach.

So project grouping is very useful to manage related projects. Although I think 50 projects under one group/solution is rare, but perhaps in large software it's not surprising.