After attempting to create a new copy of my old C++ projects under VS.NET 2K3 I did notice that the VS.NET 2K3 C++ project does in fact contain a GUID and my converted projects do not. I bet that the conversion process left out some important information (from NAnt's point of view) out and the XML is simply not parsing correctly.
I suspect that anyone else trying to build converted solutions will have the same problem.... I did not convert the project. Another developer did and then he checked in the newly converted project into VSS. I wonder if that had anything to do with the problem.... -- Edwin G. Castro Firing Systems Engineer [EMAIL PROTECTED] -----Original Message----- From: Scott Ford [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 11:12 AM To: Castro, Edwin Gabriel (Firing Systems Engr.) Cc: [EMAIL PROTECTED] Subject: RE: [Nant-users] <solution> task will not compile my C++ project Edwin, I am replying this back to the list in case it helps anyone else out in the future. Don't worry about not sending in project files. I completely understand the intellectual property concerns in doing so. The C++ project that I was using when I modified the C++ support was produced from an upgrade. One thing that I noticed early on is that VS does not always use the exact values that are specified in the project file when building the project. This is especially true if the settings are invalid for the command line switch that they get sent to. The documentation for the compiler notes what the valid ranges are. Sometimes the compiler ensures that the settings are correct, and sometimes it does not. One instance where it does not is the ImageBase setting. (I have mentioned this on the list before, I think.) My recommendation is to either recreate the project, or go into the project settings and delete any settings that are in bold text. VS uses bold text to help you identify that a setting is not the default. Make sure that all the settings that are in bold are settings that you really want/need when you compile. This will help make the build process go more smoothly when using the solution task. Ideally, solution task would be able to enforce the project settings as well, but that is a pretty daunting task at the moment. The ProjectType enumeration (if I remember correctly) is used for the class that represents C# and VB.Net projects. The C# and VB.Net project files follow a very similar structure. A project factory was created (not by me, but the initial implementer of C++ support) to return either a C#/VB.Net project class or a C++ project class. This caused me some confusion when I first started digging into the code as well. I will keep you in mind if I start working on the solution task again. I really wanted C++ build support for in-house use, and we decided that it was worth the effort for me to get the solution task to fit our needs. I feel really bad about this selfish approach to the development, because I knew it would come back to bite someone one day. When I get rolling again, I may send you custom builds (or links to them rather) to try out before I send changes to the dev list. But only if that would be acceptable. Best of luck, -Scott -----Original Message----- From: Castro, Edwin Gabriel (Firing Systems Engr.) [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 1:06 PM To: Scott Ford Subject: RE: [Nant-users] <solution> task will not compile my C++ project Scott, Unfortunately I cannot send the actual solutions and projects, but I will try to create generic ones. I looked through one of the project files and I did notice that it did not contain a GUID. I looked through a C# project file and it contained a GUID. We recently converted our solutions and projects from VS.NET to VS.NET 2003. Could this have anything to do with this? I think I will try to create a new C++ project and add the existing code as a test to see if VS.NET 2K3 will generate a GUID for the new project. I did notice that, although the solution task source code advertises that it supports C++ projects, the ProjectType enumeration only contains values for C# and VB projects. This may not have anything to do with the problem, but I wonder if a C++ ProjectType value should be added for completeness... Anyway, that not my decision. Please feel free to ask me any questions you may have in the future to solve this issue. Is there a way to filter the output NAnt generates? Thanks for any help you can provide! -- Edwin G. Castro Firing Systems Engineer [EMAIL PROTECTED] -----Original Message----- From: Scott Ford [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 9:53 AM To: Castro, Edwin Gabriel (Firing Systems Engr.); [EMAIL PROTECTED] Subject: RE: [Nant-users] <solution> task will not compile my C++ project Edwin, I did a little bit of work getting C++ projects to compile, but I identified that what worked for me might not (most likely will not) work for others. Sadly, I have not had a chance to work on this anymore. I really do what to get back to working on it, but I am not sure when I am going to have time. It might be helpful to send in your solution and your projects (or generic ones that produce the problem) to the dev list. If I get time I can take a quick look at what might be wrong, but I am not sure when I will get to it. -Scott -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Castro, Edwin Gabriel (Firing Systems Engr.) Sent: Thursday, December 18, 2003 5:25 PM To: [EMAIL PROTECTED] Subject: [Nant-users] <solution> task will not compile my C++ project I have a solution with 3 C++ projects. When I try to build the solution using the <solution> task I receive the following messages: Target(s) specified: build build: [solution] Starting solution build. BUILD FAILED Project with GUID '' must be included for the build to work. Total time: 0.1 seconds. I looked through the code and I found a comment about this problem and how it's not fixed yet. From the users list it seems that other folk can compile solutions with C++ projects although they do have other problems. I'm I out of luck here or is there some way around this? I tried using both version 0.84-rc1 and nightly build version 20031218 with the same results. --Edwin G. Castro [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
