Feel free to offer a patch to build under nant, msbuild or any method that proves viable!
The problem, is that the delayimp.lib is not distributed with the .NET Visual C++ compiler - this makes it impossible to build our c++ code outside of the full Visual Studio. I'm actually much more concerned with changes coming in the .NET Visual C++ 2005. They refactored ALOT - and we will be playing catch-up there. The code will be measurably easier to read, but in some ways harder to grok. Bill At 01:06 PM 11/22/2004, Jeff White wrote: >Have any of you "workers" (those with >live and test servers/machines) looked >at starting to use build systems for >mod_aspdotnet? > >Soon Microsoft is going to MSBuild >an XML file build system for developers, >and MSBuild is out now but for .NET 2 and so on but.... > >NAnt (an open source .NET XML build) > >http://nant.sourceforge.net/ >http://nant.sourceforge.net/nightly/latest/help/index.html > >http://nantcontrib.sourceforge.net/help/index.html >http://nantcontrib.sourceforge.net/ >NAnt is out now (for .NET 1.0/1.1/beta2 and Mono) and allows XML builds of >C/C++ (6,7,8) and .NET assemblies, and MSI install and much more.... > >Shouldn't mod_aspdotnet start using >NAnt and be ready this time (to use >MSBuild or NAnt and perhaps since it's XML based both) instead of playing >catch up later? > >Using NAnt the build can search folders, >call exe, Windows Scripting, call .NET written input routines and look like an >GUI build system or stay command line..... > >Perhaps these newer build ways can help on the build of Apache.Web and it's >usage of the other libs.... find the libs, copy/move >them and use them here and then send them back to where they belong.... :) > >Jeff > > >