Dev with what?

I'm just wondering who is using what? Dreamweaver? VS.Net? What version VS.Net? Sharp Dev? Ugh FrontPage? Notepad?

What do you publish with? I am not happy with VS.Net in terms of publishing or working with web applications. I love the designers and intergration of code/compling, but I want to work with smaller groups of files and control application scope and so on.

I already break apart my data access layer and my ui layer into seperate projects. I want to find a clean easy way to break the UI into smaller projects.

Let us say I am working on netnsite.com and it has a guestbook, code lib, chatroom, and a few games. I want to break each of these and each game into it's own project space (namespace) and group these sub projects under a root project with a default page.

I want to do this to control my dll's on a higher level.

Is there a solution to this other than manual project management?

I understand what you are saying, but if you want the cleanest approach (with .net anyway) you are probably looking to have your UI in one project for all of them. Now, that doesn't mean you are SOL. Why don't you seperate the pages by folders? You can right-click your project and add folders. This will organize your code much better. Also, if your pages are sharing things accross them, build web user controls or web custom controls. This helps minimize code and helps in the sharing. I don't know how much Visual Studio .NEXT is going to help us, but for now, these are they things I have done to make things easier.

Quote:

---

Originally Posted by hellswraith

I understand what you are saying, but if you want the cleanest approach (with .net anyway) you are probably looking to have your UI in one project for all of them. Now, that doesn't mean you are SOL. Why don't you seperate the pages by folders? You can right-click your project and add folders. This will organize your code much better. Also, if your pages are sharing things accross them, build web user controls or web custom controls. This helps minimize code and helps in the sharing. I don't know how much Visual Studio .NEXT is going to help us, but for now, these are they things I have done to make things easier.

---

This is what I'm doing now. Exactly what your saying and most likely doing. I'm hoping for a way to turn the sub folder into a sub project. I don't know though it isn't as easy to do as it sounds, but I think it is within the realm of posability; at least with some kind of IIS FrontPage Ext. tie in. The sub folder/project would refreance the dll for the main project automaticly and any kind of link checking cold be controled through the FP Ext.

I'm just tired of digging through all the files and folders and so on. It's almost as bad as when you have 200 or so Stored Procedures in a DB. Thats something else that would be just awsome being able to put Stored Procedures in "Folders" and group them for quick access. Couldn't this be done by adding a field or two to the INFORMATION_SCHEMA?

I'm still using VS.Net 2002; I'm holding out for a stable 2005 and hoping it is going to be great. When I tried the beta I noticed things to do with Themes and some other interesting stuff, but I only had it for a few days it put my system out of whack and killed my debuger....