>>>>>>Dmitry,
>>>>>>I have been working on these same principles the last few months, and I have gotten to a point where I have multiple UI projects per solution. I have gotten into the habit of having a specific name for my UI project, instead of just "UI". I mention this because I recently had a rename a UI project to a more specific name, and it was kind of a pain.
>>>>>>
>>>>>
>>>>>Mike,
>>>>>I appreciate your suggestion to the UI naming convention.
>>>>>
>>>>>Let me ask you, when you are saying "mutiple UI projects", do you mean that you have a project for each Window of your application?
>>>>
>>>>Nope, I have separate UI projects for separate focuses. For example, I have one UI project that is an ASP.NET webform, and that is the main UI project that the customers use. I have another UI project that is another ASP.NET webform, but it is more of an account management type project that only our internal employees use. I also have a few projects which are console applications that I have scheduled on our SQL Server that run data loads. It's nice because they can all use the same business and data layers.
>>>
>>>Thank you for clarifying.
>>
>>No problem. I either seem to be a slower learner than some on this site, or I get busy doing other non-programming related stuff, that I seem to be stuck in newbie mode with this stuff too. It's nice to have a few others around my level.
>
>I think I know how you feel. I have many things I have to constantly juggle and often times it make you go back to the same stuff over and over. It would be nice to spend a solid amount of time on just one project but not possible at this moment.

I am lucky because when I do get to do programming work, I get a solid chunk of time to work on it. The problem is, I am constantly paranoid about doing things the right way... not just making them work. I recently started a new job, and the developer I replaced made things way too complex. My motto is "keep it simple, stupid."