You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cli-dev@httpd.apache.org by wr...@apache.org on 2004/07/19 22:48:13 UTC
svn commit: rev 23068 - incubator/httpd/cli/trunk/mod_aspdotnet
Author: wrowe
Date: Mon Jul 19 13:48:12 2004
New Revision: 23068
Modified:
incubator/httpd/cli/trunk/mod_aspdotnet/README
Log:
Another round tuit, consider making this buildable by anyone
with a .bat file and the MS VC++ Toolkit free .NET compiler.
Modified: incubator/httpd/cli/trunk/mod_aspdotnet/README
==============================================================================
--- incubator/httpd/cli/trunk/mod_aspdotnet/README (original)
+++ incubator/httpd/cli/trunk/mod_aspdotnet/README Mon Jul 19 13:48:12 2004
@@ -21,7 +21,7 @@
Note that the Apache.Web.dll is temporarily registered, it's type library
(.tlb file) is extracted, and it is unregistered as a post-build step for
both the Debug and Release builds of the Apache.web. This assures us that
-the usual build machines remain clean of excess COM registration gunk.
+the usual build environment remains clean of excess COM registration gunk.
We build Apache.Web.dll with delay-load of libhttpd, libapr and libaprutil
dll's. This is important since Apache.Web.dll can't be touched unless
@@ -56,8 +56,8 @@
regasm d:\path-to-apache\bin\Apache.Web.dll
gacutil /ir Apache.Web.dll FILEPATH d:\path-to-apache\bin\Apache.Web.dll Apache.Web
-This will *NOT* work on a customer's machine without the .Net SDK. Those
-tools [regasm/gacutil] aren't installed with the retail .Net install.
+This will *NOT* work on an end-user's machine without the .Net SDK. Those
+tools [regasm/gacutil] aren't installed with the retail .Net-redist install.
TODO
@@ -101,4 +101,9 @@
installer.msi project, and sets that default as the targetdir for
the installation.
+It is entirely possible for the project to also create a .bat file
+build script using the http://msdn.microsoft.com/visualc/vctoolkit2003/
+Visual C++ Toolkit for .NET (a free download.) Of course, it would not
+be possible to create the .msi installer using that file. It would be
+possible to use the free XML-based .msi packaging techology, however.