all groups > visual studio .net general > april 2004 >
You're in the

visual studio .net general

group:

Why did they call a project a solution?


Re: Why did they call a project a solution? Bert Hyman
4/30/2004 6:14:17 AM
visual studio .net general:
blahhh@blahhhhh.com (Claire) wrote in
news:OkaZJ2nLEHA.1892@TK2MSFTNGP10.phx.gbl:

[quoted text, click to view]

Because a Project is not a Solution (in this context anyway).

I'm currently working on a "Solution" that contains 31 "Projects";
most are C# with a few C++ and VB thrown in.

A few of the "Projects" produce EXEs that use the DLLs produced by
the other "Projects".

--
Why did they call a project a solution? Claire
4/30/2004 7:37:04 AM
I hate some overused buzz words and amongst them are "Enterprise" and
"Solution".
Is it possible to get at the string resources in visual studio and change
every instance of "Solution" to something different before I throw up?

thanks

Re: Why did they call a project a solution? CT
4/30/2004 9:34:27 AM
While I agree that some buzz words, such as enterprise, are often used in
the wrong context, I don't think it would help very much if you did manage
to replace every instance of solution in VS .NET. How would you distinguish
between a project and a solution, if you changed solution to say project?

--
Carsten Thomsen
Enterprise Development with VS .NET, UML, and MSF
http://www.apress.com/book/bookDisplay.html?bID=105
[quoted text, click to view]

Re: Why did they call a project a solution? Claire
4/30/2004 10:32:59 AM
Hi Carsten,
Project group, project collection, I'm sure there must be a less cliched way
of describing it.

AddThis Social Bookmark Button