I fixed the GUID problems in my solution/project files. I build the solutions using VS.NET to make sure they still work. I tried to build one of the solutions using NAnt and I get the following error:
<cmd.exe> T:\FireBox>nant /f:FireBox.build.xml NAnt 0.85 (Build 0.85.1653.0; net-1.0.win32; nightly; 7/11/2004) Copyright (C) 2001-2004 Gerry Shaw NAnt Team Buildfile: file:///T:/FireBox/FireBox.build.xml Target(s) specified: build build: [solution] Starting solution build. BUILD FAILED INTERNAL ERROR System.ArgumentNullException: Value cannot be null. Parameter name: path2 at System.IO.Path.Combine(String path1, String path2) at NAnt.VSNet.VcConfiguration.get_OutputPath() in C:\DOCUME~1\drieseng\LOCALS ~1\Temp\tmp76E.tmp\src\NAnt.VSNet\VcConfiguration.cs:line 161 at NAnt.VSNet.ProjectBase.GetOutputPath(String configuration) in C:\DOCUME~1\ drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.VSNet\ProjectBase.cs:line 183 at NAnt.VSNet.Solution.GetDependenciesFromProjects() in C:\DOCUME~1\drieseng\ LOCALS~1\Temp\tmp76E.tmp\src\NAnt.VSNet\Solution.cs:line 603 at NAnt.VSNet.Solution..ctor(FileInfo solutionFile, ArrayList additionalProje cts, ArrayList referenceProjects, TempFileCollection tfc, SolutionTask solutionT ask, WebMapCollection webMaps, FileSet excludesProjects, DirectoryInfo outputDir , GacCache gacCache, ReferencesResolver refResolver) in C:\DOCUME~1\drieseng\LOC ALS~1\Temp\tmp76E.tmp\src\NAnt.VSNet\Solution.cs:line 131 at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask() in C:\DOCUME~1\drieseng\LOCALS ~1\Temp\tmp76E.tmp\src\NAnt.VSNet\Tasks\SolutionTask.cs:line 375 at NAnt.Core.Task.Execute() in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\ src\NAnt.Core\Task.cs:line 176 at NAnt.Core.Target.Execute() in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tm p\src\NAnt.Core\Target.cs:line 249 at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\Project.cs:l ine 873 at NAnt.Core.Project.Execute() in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.t mp\src\NAnt.Core\Project.cs:line 830 at NAnt.Core.Project.Run() in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\s rc\NAnt.Core\Project.cs:line 898 Please send bug report to [EMAIL PROTECTED] Total time: 1.2 seconds. </cmd.exe> It looks like the error is related to generation of the output path. I would like Nant to use the output path information in the project files... I hope this the default behavior... Judging from the error it seems that one of my project files is missing the output path information. Any help determining the cause of the problem would be appreciated! -- Edwin G. Castro [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Castro, Edwin Gabriel (Firing Systems Engr.) > Sent: Friday, July 09, 2004 12:30 PM > To: [EMAIL PROTECTED] > Subject: RE: [Nant-users] Project with GUID 'xxx' must be > included for the build to work error > > I don't think the problem is with NAnt. I think it's with > Visual Studio. > There is a comment on line 554 of Solution.cs that checks > that project GUIDs match GUIDs in the solution file. This > would be a place where my build would die but it doesn't. It > dies earlier. The fact that the build dies earlier is > unfortunate because I don't get the warning that says that > there is some corruption in the solution and project files. > > I traced my build in the Visual Studio debugger and found > that I'm getting an exception on line 46 of > VcConfiguration.cs that tries to find the project directory. > The problem here (which might be fixed in a newer NAnt > nightly build) is that the code uses the project GUID to > check in the solution. The exception occurs because the GUID > in the project file does not match the GUID in the solution file. > > In my case, the project was created in its own personal > solution. The project was later added to the "master" > solution. I *think* that Visual Studio simply created a new > GUID when the project was added to the master solution > instead of using the one in the project file. > > I have also encountered problems when the project file does > not have a GUID. I think this problem is due to Visual Studio > upgrades and its conversion utility. > > Both cases can be considered "solution and project file corruption" > caused by Visual Studio. I'm fairly certain that we did not > manually corrupt the files because my team does not touch the > files manually. I'm a little more daring and I look in them, > but I still don't change any of the contents. > > I think a tool that could read these files and build a > dependency graph between solution and project files could be > really useful. Such a tool could then change the GUID of a > project and automatically change the GUID in the solutions > that depend on that project. My master solution has 38 > projects and each project is in at least one other solution. > A dependency tool like the one I described above would be > really useful to me... Perhaps I might try to write such a > tool at some point. Until then, we will need to fix our > project and solution files by hand. > > I think Visual Studio does not use the GUIDs internally and > that is why I can still use my solutions and projects find in > Visual Studio. > > My suggestion to anyone encountering an exception about GUIDs > when using the <solution> task is that you verify that the > GUIDs match in the solution and project files for the > solution and projects you are trying to build. > > The references to source are from the following nightly build: > NAnt 0.85 (Build 0.85.1606.0; net-1.0.win32; nightly; 5/25/2004). > I know it's old, but the examples show what I'm trying to say... > > Gert, I find it difficult to reproduce the issues I see > without sending you our code. I can't send the code since it > is not open source. I might be able to "clone" the situation > by copying all the files and changing names, file paths, etc. > to names that are non-descript and make sure that the source > files are "empty". This process could take some time so I > want to know how much help this would really be. I don't want > to go through it if it really won't help NAnt developers. > > Perhaps the Docs for the <solution> task could mention the > possibility of solution/project file corruption especially as > it pertains to GUIDs. > That way users can at least have a warning about this > potential problem... > > -- > Edwin G. Castro > [EMAIL PROTECTED] > > > > > -----Original Message----- > > From: Gert Driesen [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 02, 2004 4:11 PM > > To: Castro, Edwin Gabriel (Firing Systems Engr.); Brian Yeo; > > [EMAIL PROTECTED] > > Subject: Re: [Nant-users] Project with GUID 'xxx' must be > included for > > the build to work error > > > > Castro, > > > > It would be great if you could submit a bug report for this > containing > > the absolute minimum set of files necessary to reproduce > this issue ? > > > > Thanks ! > > > > Gert > > > > ----- Original Message ----- > > From: "Castro, Edwin Gabriel (Firing Systems Engr.)" > <[EMAIL PROTECTED]> > > To: "Gert Driesen" <[EMAIL PROTECTED]>; "Brian Yeo" > > <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Friday, July 02, 2004 9:46 PM > > Subject: RE: [Nant-users] Project with GUID 'xxx' must be > included for > > the build to work error > > > > > > Hi Gert, Brian, > > > > I've had this problem come up when I tried to build some > C++ projects > > I have. The projects have been upgraded from Visual Studio 6 and I > > thought that could be part of the problem. > > From what I can tell a project specified in the solution file has a > > different GUID than the GUID specified in the project file. > > > > I have not been able to determine under what conditions > Visual Studio > > generates different GUIDs but I think it may be related to when you > > add an existing project. I think that if you create a > project under a > > particular solution (A) and then try to add that project to a > > different solution (B) then Visual Studio creates a new GUID for > > solution B and never changes the GUID in the project or in > solution A. > > Anyway, that's my hypothesis. > > > > I've also run across situations where a GUID exists in the solution > > file but the project file does not have a GUID. This issue, > I think, > > is related to the format conversion required when you > upgrade Visual > > Studio. > > > > One way I fixed all this was to open the appropriate files > in a text > > editor and make sure that all GUIDs matched! In my case I have a > > solution with 38 projects and almost each of those projects where > > created in their own separate solution and added to the big > solution > > afterwards. That's a lot of files to check... Much easier > in my case > > to run devenv! > > > > In the end this problem, I think, is related to behavior in Visual > > Studio and I'm not sure that Nant is at fault here. > > Then again, I don't know what Nant should do about it, if anything. > > > > -- > > Edwin G. Castro > > [EMAIL PROTECTED] > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:nant-users- > > > [EMAIL PROTECTED] On Behalf Of Gert Driesen > > > Sent: Friday, July 02, 2004 12:31 PM > > > To: Brian Yeo; [EMAIL PROTECTED] > > > Subject: Re: [Nant-users] Project with GUID 'xxx' must be > > included for > > the > > > build to work error > > > > > > Brian, > > > > > > Can you package up a zip file containing the minimum set of files > > necessary > > > to reproduce this issue ? > > > > > > Thanks, > > > > > > Gert > > > > > > ----- Original Message ----- > > > From: "Brian Yeo" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Friday, June 18, 2004 3:39 AM > > > Subject: [Nant-users] Project with GUID 'xxx' must be > > included for the > > build > > > to work error > > > > > > > > > > > > > > Hi, > > > > I am getting a message stating that a project must be > included for > > the > > > build > > > > to work. Does anyone have an answer to this?. > > > > > > > > <target name="Build-Ent-APAB" > description="Build-Ent-APAB"> <echo > > > > message="Build-Ent-APAB"/> > > > > <solution configuration="${release.state}" > > > > outputdir="${drive}\${src.path.apab}\bin\${release.state}" > > > > failonerror="${failonerr}"> > > > > <projects> > > > > <includes > > name="${drive}\${src.path.apab}\*.csproj" /> > > > > </projects> > > > > <referenceprojects> > > > > <includes > > > > > name="${drive}\${src.path.common}\${PTA.Ent.Common}\*.csproj" /> > > > > </referenceprojects> <assemblyfolders> > > > > <includes name="${drive}\${src.bin.ent}" /> > </assemblyfolders> > > > > </solution> > > > > The message is: Project with GUID > > '{79F1FE34-BCF0-45F1-ACAE-3AF429CB364D}' > > > > must be included for the build to work.: > > > > > > > > Regards, > > > > > > > > Brian Yeo > > > > > > > > > _________________________________________________________________ > > > > Get a Credit Card - 60 sec online response: > > > > > > > > > http://ad.au.doubleclick.net/clk;8097459;9106288;b?http://www. > > anz.com/au > > s/pr > > > omo/qantas5000ninemsn > > > > [AU only] > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by The 2004 JavaOne(SM) > Conference > > > > Learn from the experts at JavaOne(SM), Sun's Worldwide Java > > Developer > > > > Conference, June 28 - July 1 at the Moscone Center in San > > Francisco, > > CA > > > > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code > > NWMGYKND > > > > _______________________________________________ > > > > Nant-users mailing list > > > > [EMAIL PROTECTED] > > > > https://lists.sourceforge.net/lists/listinfo/nant-users > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email sponsored by Black Hat Briefings & Training. > > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 > > - digital > > > self defense, top technical experts, no vendor pitches, unmatched > > > networking opportunities. Visit www.blackhat.com > > > _______________________________________________ > > > Nant-users mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/nant-users > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 > - digital > > self defense, top technical experts, no vendor pitches, unmatched > > networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > Nant-users mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/nant-users > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor > pitches, unmatched networking opportunities. Visit > www.blackhat.com _______________________________________________ > Nant-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-users > > ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
