Re: Huge project - long build time
From: Ken Dopierala Jr. (kdopierala2_at_wi.rr.com)
Date: 11/12/04
- Next message: John M Deal: "Re: How do I set "Result Code" (visible in Scheduled Tasks) in VB App"
- Previous message: Marc Robitaille: "VB.NET ide problem -- Am I alone with this problem?"
- In reply to: cody: "Re: Huge project - long build time"
- Next in thread: cody: "Re: Huge project - long build time"
- Reply: cody: "Re: Huge project - long build time"
- Reply: cody: "Re: Huge project - long build time"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 12 Nov 2004 14:26:12 -0600
Hi Cody,
You could try to do what I do. My current web app has over 130 seperate
projects and I'm having no problems whatsoever. Here is what I do.
My solution contains what I'm currently working with. For example, right
now it has the web app itself (that is always there), over a dozen web
services and about 20 class libraries that are consumed by the web services.
As I finish web services and class libraries I remove them from my solution.
For every single project in my solution I reference the DLL directly, not
the project. The only time I have a hassle is when I need to go modify a
class library. Sometimes more than one of my web services reference these
libraries and I need to go back and recompile those web services so they all
have the correct version of my DLL. This is really simple though, I just
browse to the web service, load it up, and recompile.
Yes it is a hassle but when you develop large applications you need to
realize that planning and architecture are the most important things. I
know that when I need to go through that hassle it is due to a failure on my
part and not the IDEs problem. I either didn't debug my class well enough,
or I didn't architect it well enough because I had to go back and make
changes. That is my failure and my frustration is due to my mistake. It
sounds like you didn't do any planning and are frequently going back to
modify projects that projects built on top of them rely on. That is just
inefficient and short-sighted on your part. Sit down, map out your
solution, build it from the ground up and you should see things go a lot
more smoothly for you. Good luck! Ken.
-- Ken Dopierala Jr. For great ASP.Net web hosting try: http://www.webhost4life.com/default.asp?refid=Spinlight If you sign up under me and need help, email me. "cody" <please_dont.spam.deutronium@gmx.de> wrote in message news:uDhlFCPyEHA.3844@TK2MSFTNGP12.phx.gbl... > > Try creating two seperate solutions. One is your working solution where > you > > just pull in the projects you are working on. The other solution is your > > full build solution that has all the projects in it. Never tried that but > > it might work. Good luck! Ken. > > > What does that help? The information wheather dll references or project > references are used are stored in each project separately, so if I use one > solution for building the whole stuff I still have to take care of the build > order manually. > > I cannot believe that nobody else here has experience with large projects. > > -- > cody > > [Freeware, Games and Humor] > www.deutronium.de.vu || www.deutronium.tk > >
- Next message: John M Deal: "Re: How do I set "Result Code" (visible in Scheduled Tasks) in VB App"
- Previous message: Marc Robitaille: "VB.NET ide problem -- Am I alone with this problem?"
- In reply to: cody: "Re: Huge project - long build time"
- Next in thread: cody: "Re: Huge project - long build time"
- Reply: cody: "Re: Huge project - long build time"
- Reply: cody: "Re: Huge project - long build time"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|