Well, I guess only Kevin knows why he decided to structure things the way he did. <g>

Here's a good rule of thumb that Gary taught me: think of how you want to architect your app and then actually design things with one more layer of abstraction. This isn't quite the same thing, but the analogy I'm trying to make is that a lot of times things are a bit more complicated than we originally planned for. <g>

~~Bonnie




>Bonnie,
>
>I do trust your judgement and value your opinion.
>
>But just to add to my previous message, I think Kevin G. (he is not here so we can say anything we want about him <g>) was also "hacking" folder names. I see that he has a folder DataAccess and inside this folder there is a project of a different name (Company.DataAccess) without a folder Company.DataAccess. So I presume that he did what Viv suggested in making folders and projects named as he wanted them.
>
>But I will think again about what you are saying here (about having several different DataAccess.. projects). I was under impression (wrong, of course <g>) that in my application I will have only one DataAccess project. And then all BIZ projects will use it to get data. But I am probably simplifying thing a bit.
>
>Thank you.
>
>>Look at it from this standpoint: in a large application you would most likely break down your DataAccess functionality into several different projects. For example, DataAccessBase, DataAccessPersonnel, DataAccessCustomer, etc. (or however you end up naming the projects).
>>
>>So you'd have a DataAccess folder, with folders under it for each of your projects. Each of those folders could hold lots of classes (.cs files). Trust me, this is an excellent way to organize your stuff.
>>
>>~~Bonnie
>>
>>
>>
>>
>>
>>>Thank you for your explanation on creating Solution Folders (I was actually looking a source of a project that comes with Kevin G's book and could not understand what are those folders in the solution but no physical folder. Now I understand where they came from).
>>>
>>>However, I still have - a minor though - problem with creating a project. Here is what it is. Say I follow your example and create a Solution Folder DataAccess and then create a physical folder DataAccess. Then I right-mouse click on the DataAccess Solution folder and add a project MyCompanyDataAccess. What happens is VS creates a physical folder MyCompanyDataAccess right in the folder DataAccess. So I have this "extra" folder MyCompanyDataAccess. I would prefer that I can create a project MyCompanyDataAccess to be right in the folder DataAccess. That is, I don't want to have an extra folder. I guess I know now how to deal with it from Viv's suggestion. So it is not a major deal. But I thought that VS 2005 would/could provide a little more flexibility.
>>>
>>>Thank you.
>>>
>>>>I agree with Viv that you want to keep the folder named as VS named it (MyCompany.DataAccess). However ... if you have several DataAccess projects and you want to group them all under one umbrella folder called DataAccess, here is what you can do:
>>>>
>>>>1) First, right-click your solution and choose Add | New Solution Folder. Call it DataAccess.
>>>>2) This only creates a "virtual" folder ... IOW, your actual directory structure on your hard-drive will not contain a DataAccess folder.
>>>>3) If you want a real DataAccess folder (and I would), then simply go to Windows Explorer and create the folder (be aware that you have to do it in this order ... Solution Folder first, then real folder in Windows Explorer).
>>>>4) When you want to add a new project under the solution folder, simply right-click and add projects as you normally do. They will show up under the folder (both in your solution and on your hard-drive).
>>>>
>>>>~~Bonnie
>>>>
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>When I add a project to a solution and name the project, say "MyCompany.DataAccess", Visual Studio 2005 creates a physical folder named MyCompany.DataAccess. The folder is created as a subfolder of my solution folder. I see no way to change the name of this folder. I would like the folder name to be something simpler, for example, DataAccess. But I see no options when creating/adding the project to set the folder name. I can specify where the project/folder will be placed (parent folder) but not the name of the folder itself. Strange though, as when I am reviewing a solution from a book I am reading, the author has a project named "HisCompany.DataAccess" but the folder name is DataAccess.
>>>>>
>>>>>What am I missing?