I was told by someone that Visual Studio 2005 has moved away from multiple projects in a solution. I don't believe this for a second, but I wanted to see if 1) it really was true and 2) if there is any info I could draw from to counter that argument.
Also, do many of you consider the information in this article:
(
http://msdn.microsoft.com/library/default.asp url=/library/en-us/dndotnet/html/designnetapp.asp)a bit outdated And by outdated I don't mean unusable, I just mean that it seems a bit simplistic for many projects.

VS 2005 and multiple projects.
Adiraz
Mihir101
dotcom23
Not as far as I know - The only thing you *may* want is to ship less DLLs (but that doesn't have to mean fewer projects). During development it is much easier to have separate projects for non-dependent chunks
Arnon
Simon Clark
you CAN have multiple projects in one solution under vs2005.
You must consider that your programmer is a penguin (you know, all day thinking in how to put linux/java in your company :))
anarbek
Umm you can certainly create multiple projects in a VS 2k5 solution ... I can post a screen shot if you need one :D Although I tend to limit my projects within a solution to functional groupings and use Nant to do my building for me.
I agree that this article is not very sophisticated but I fear this is more of a social problem with .NET as opposed to a technical one. I would wager that because you are questioning the article you are probably within the top 25% of developers. Unfortunately the top 25% are not really the ones who need such articles ;) They think about such things as coupling as opposed to finding some code that works on a website some place and copy/paste reusing it into their own code. I find master pages to be a similar concept targetted towards a different type of development. I put up some arguments on master pages here http://geekswithblogs.net/gyoung/archive/2006/01/24/66892.aspx
Cheers,
Greg
JTechOnlineGuy
I can not imagine that there has been. With things like inversion of control finally becoming mainstream in the .NET community this would be quite counter-intuitive :) Frankly I find the idea obsurd although I would be very interested in hearing any supporting evidence. In fact I would say they are moving more in the direction of seperation (take the gratuitous use of the provider pattern).
Cheers,
Greg