organizing you source code

re: organizing you source code

Uwe — Sun, 13 Jun 2004 11:04:00 GMT

You can use the VS File Finder plugin, maybe this helps a little bit (at least for me, it does :-)): http://www.codeproject.com/dotnet/VS_File_Finder.asp

Source Code Organization

Being Scott Densmore — Sun, 13 Jun 2004 21:44:00 GMT

re: organizing you source code

Barry Dorrans — Sun, 13 Jun 2004 20:15:00 GMT

I assume that you're not actually doing them as \MSCorLib, but rather something in the recommended MSBuild style, projects\name\main, projects\name\1001 etc, otherwise how are you going to deal with branching and pulling old versions out to fix problems without rolling out all your changes?

re: organizing you source code

Brad Abrams — Sun, 13 Jun 2004 20:25:00 GMT

That is fair, it is actually "ndp\clr\src\bcl\", but I didn't want confuse the issue...

re: organizing you source code

Rick Childress — Mon, 14 Jun 2004 03:04:00 GMT

re: organizing you source code

Rick Childress — Mon, 14 Jun 2004 03:05:00 GMT

ahh, my spaces were eaten....

that was *supposed* to be a tree, System under mscorlib.... :-)

Visual Studio: Living in peace with namespaces

Ken Brubaker — Tue, 15 Jun 2004 16:14:00 GMT

How to organize your Visual Studio project to best leverage namespaces.

Geek Notes 2004-06-24

Geek Noise — Thu, 24 Jun 2004 18:25:00 GMT

re: organizing you source code

Greek Geek — Thu, 15 Jul 2004 18:32:00 GMT

It is logical to have each namespace a directory and each class a file. It is also logical to keep version trees separate. My question is, should we include major version information in the namespace root.

namespace XYZ.MyProject.V1.Reports {}
namespace XYZ.MyProject.V2.Reports {}

and then just change the imports/using statements to include new versions.