I'll second that. We have a project that uses idl files (corba specification). The <solution> task always tried to compile these with midl.exe; but we really wanted to compile them with the omniOrb idl compiler; and I couldn't figure out how to turn off the midl. On top of that, there were strange "non-compile" issues like you describe below. Everything just started working when we used the <exec> task to run devenv.com
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arnette, Bill Sent: Wednesday, April 04, 2007 12:50 PM To: Kyle Schmitt; nant-users@lists.sourceforge.net Subject: Re: [NAnt-users] Solution task and non dot.net code We gave up on using the <solution> task for VC++ (7.1) projects. The dependency analysis just doesn't seem to match devenv so we may have a header file or a resource that changes that should force a recompile but doesn't. Also, one of the advantages of the <solution> task is that you don't have to have VS.NET installed on your build machine. This is true for C# and VB.NET projects because the .NET Framework SDK includes the C# and VB.Net compiler. But it does not include the C++ compiler, so you have to have VS.NET installed on the build machine anyway. We just use the <exec> task to run devenv.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
