houldn't affect
dependant references. We use SQL scripts to create the db. I say just skip
that project type even if its in the csproj file.
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 3:49 PM
To: Brian Nantz; [EMAIL PROTECTED]
Su
No I only point to the solution and map the webservices. The csproj files
may refernce the database project I don't know but there are no filesets.
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 12:44 PM
To: Brian Nantz
Subject: Re:
I thought I posted this before but I don’t
think it went through. I tried this with May 25 build and it doesn’t
work.
Brian
From: Gert Driesen
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 9:48
AM
To: Brian Nantz; [EMAIL PROTECTED]
Subject: Re: [nant-dev
I have found that the solution task has greatly matured
since I last used it. I use enterprise templates in my solutions all the
time. At work the master solution contains 109 projects! The NAnt solution
task does pretty well until it gets to a VS.NET database project then it gives
me an
his is a great addition for
NAnt:
http://www.hanselman.com/blog/PermaLink.aspx?guid=10a8f7d4-d555-47a1-be68-f6
8baf9ef4a5
We should pull this into the
NAnt project if possible.
Brian
