Installing mod_aspdotnet -- ASP.NET...

[admin]

Have you tried installing it on Apache 2.0?

You are right, the bug db is old.

Try starting apache with...
apache -w -e debug -k start

...and check logs\error.log

[admin]

I'm not sure how this went over me, but...

I realize now that the snapshot could have only been built for Apache 2.0.

The only way to get mod_aspdotnet for Apache 2.2 is to build it yourself form the code in the repository and selecting the Apache 2.2 target.

[admin]

It seems that mod_aspdotnet is here to stay after all -- it might even make it into the official Apache Win32 distibution...

From:   "William A. Rowe, Jr."
Subject:   Announcement; cli-dev@ List Folding into dev@ on May 15
Date:   Thu, 11 May 2006 16:14:28 GMT

cli-dev@ community,

as we polled over the past few months, it seems that most of the dev interest
on this forum remains centered around mod_aspdotnet, and using mono or aspdotnet
tools to proide ASP.NET services from Apache httpd server.  It's the decision
of the httpd PMC to fold all efforts around mod_aspdotnet into the httpd core
community.

You can get a jump on this by subscribing to dev@httpd.apache.org, if you are
not already.  We will move mod_aspdotnet development discussion on Monday, so
email dev-subscribe@httpd.apache.org now to ensure you miss nothing.

This move offers several advantages - better oversight by httpd, better
communications between mod_aspdotnet development and httpd core development,
and so forth.  The core developers learn more about mod_aspdotnet, the
mod_aspdotnet developers learn more about how Apache httpd server is evolving.
And as simultaniously announced, cli-users@ moves to users@ at the same time,
for very similar reasons.

The repository won't move, it will remain a seperate svn module, because it is
built only for one platform using one set of compiler tools.  The binaries would
move directly into the http://www.apache.org/dist/httpd/binaries/win32/ download
location, once voted to release.

In moving, a new release will be submitted Monday for consideration based on
the most recent snapshot (which many already use).  Once it's done, this will
be branched to a vs2002 specific branch, and the main code upgraded for the new
C++ API in Visual Studio 2005.  This should permit more users to roll-their-own
based on the Visual Studio 2005 express edition, and catches up to Microsoft's
current C++.NET programming language (which as some already know, looks little
like the original iteration of C++.NET).  This also catches us up to .NET 2.0.

We hope to see a strong showing in the release vote process, because the release
process is the one and only metric of project health; it will determine if the
mod_aspdotnet continues to survive as an effort of the ASF and the Apache HTTP
Project.  Although non-PMC votes aren't binding, they are very much needed for
other PMC members to guide their votes, please consider testing this candidate
early next week.  (This process, of course, will occur on dev@httpd.apache.org).

On the long-term roadmap, one possibility for Apache 2.2 and onwards is a brand
new mod_proxy_asp implementation, similar to the other proxy connectors; and the
possibility of rebirthing cli-dev soley to focus on developing .NET-authored
Apache HTTP Server module extensions still exists.  However, re-sparking cli-dev
in that form would entail entering the incubator as a new effort, one I'm happy
to contribute to, and mentor, but will not solo.  Ping me if you have interest.

[admin]

cli-dev ->
Mailing list archives: dev@httpd.apache.org
http://mail-archives.apache.org/mod_mbox/httpd-dev/

cli-users ->
Mailing list archives: users@httpd.apache.org
http://mail-archives.apache.org/mod_mbox/httpd-users/

[admin]

From     "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject    Re: [users@httpd] ASPDotNet
Date    Thu, 18 May 2006 04:00:13 GMT

Vic Feria wrote:
> Anything new in the development of mod_aspdotnet?

Yes - on the ASF side, most folks are using the snapshot, not a release,
which is usually a good sign that the snapshot is ready for release.

I'm rolling 2.0.0.4 (last is the release sequence) and 2.2.0.4 binaries
to run in httpd 2.0 and now 2.2 - the modules need to be distinct because
the httpd binary API changed.  Look for this by Saturday morning.

Otherwise it's mostly the administrative hassles with moving the old URI
for the module effort to http://httpd.apache.org/mod_aspdotnet/ - it's
correctly linked from http://httpd.apache.org/modules/ (this was all just
updated - if you find a broken link, please holler).

So all that is changing between now and Saturday is moving the docs into
the distribution, and deciding what to do with the installer(s) vis a vis
Apache.exe 2.0.x and httpd.exe 2.2.x - it's possible I might have just
one installer which installs either one.

And that's the end of the source code building against Visual C++.NET (2002)
since they redid the entire *language* in Visual Studio 2005 for .NET 2.0.
We'll branch the old source in case we ever need to build it again, but most
likely the following release can be built at-home by anyone with the new
Visual Studio 2005 C++ Express Edition.

So watch for an update announced first to dev@httpd this weekend for a release
vote, and then the general announcement will go out here and announce@httpd.a.o
once a release gets 3 +1 votes.

Help is always welcome, that discussion happens on dev@httpd.apache.org - the
same as most of the ASF's httpd modules.

Bill

[admin]

I'm still not seeing any new releases of mod_aspdotnet. I guess we will have to deal with what we have.

[admin]

Just tried to build mod_aspdotnet (latest svn repo) for Apache 2.2.2 with VS.NET 2002.

Code:

set APACHE22_PATH=C:\www\Apache22

Code:

devenv mod_aspdotnet.sln /useenv /build "Release 2.2" /project installer

...
The application for project 'E:\build\mod_aspdotnet\installer.ism' is not installed.

Make sure the application for the project type (.ism) is installed.
Invalid project
...

So where do I get InstallShield. The VS.NET 2002 install cds do not seem to have it -- unless it is in web tools -- which is greyed out -- no IIS on my system.

Ok. So what does the msi installer do anyways that can not be done manually? Lets skip that garbage and go straight to the source...

Code:

C:\build\mod_aspdotnet>devenv mod_aspdotnet.sln /useenv /build "Release 2.2" /project mod_aspdotnet

Microsoft (R) Development Environment  Version 7.00.9466.
Copyright (C) Microsoft Corp 1984-2001. All rights reserved.

The application for project 'E:\build\mod_aspdotnet\installer.ism' is not installed.

Make sure the application for the project type (.ism) is installed.------ Build started: Project: Apache.Web, Configuration: Release 2.2 Win32 ------

Compiling Apache.Web.Helpers
Compiling...
WorkerRequest.cpp
AssemblyInfo.cpp
Generating Code...
Compiling resources...
Linking...
Exporting .tlb
Types registered successfully
Assembly exported to 'e:\build\mod_aspdotnet\Release22\Apache.Web.tlb', and the type library was registered successfully
Types unregistered successfully

Build log was saved at "file://e:\build\mod_aspdotnet\Release22\BuildLog.htm"
Apache.Web - 0 error(s), 0 warning(s)


------ Build started: Project: mod_aspdotnet, Configuration: Release 2.2 Win32 ------

Compiling...
mod_aspdotnet.cpp
Compiling resources...
Linking...
   Creating library ..\Release22/mod_aspdotnet.lib and object ..\Release22/mod_aspdotnet.exp

Build log was saved at "file://e:\build\mod_aspdotnet\Release22\BuildLog.htm"
mod_aspdotnet - 0 error(s), 0 warning(s)


---------------------- Done ----------------------


    Build: 2 succeeded, 0 failed, 0 skipped

Looks like that built everything successfully -- mod_aspdotnet.lib, mod_aspdotnet.so, Apache.Web.dll

The question is, what now?...

I know nothing about the following...

Deployment Notes
----------------

YOU MUST test both the .NET Framework SDK, as well as the .NET Framework
Runtime environments.  A number of internal behaviors vary between these
two releases, and Exceptions, destruction, construction and failure cases
will manifest differently between the two variants.

ASP.NET requires the Apache::Web::Request object to be registered in
the Global Assembly Cache in order to instantiate it's host container.

The Debug build will do so automatically, copying mod_aspdotnet.so + .pdb
into the $(APACHE_PATH)\modules directory, for testing.
Apache.Web.dll + .pdb files are copied into $(APACHE_PATH)\bin
so that it can discover libapr.dll, libaprutil.dll and libhttpd.dll when
running in the System.Web.Hosting's AppDomain.  Apache.Web.dll is then
registered and installed into the Global Assembly Cache by the Debug build's
post-build custom command.

In order to install a reference into the Global Assembly Cache (for testing
the release build instead of the debug build) use;

  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 installs Apache.Web.dll by reference to the built assembly.

This may *NOT* work on an end-user's machine without the .NET Platform SDK.  
Those tools [regasm/gacutil] were not officially going to be distributed
with the retail .NET runtime redistributables.  Instead, the .msi installer,
has all details for registering the Apache.Web assembly into the Global
Assembly Cache, is entrusted to install Apache.Web to the GAC for end-users.

From the little that I can pick up on, the following commands need to be executed on the user's system...

Code:

> regasm C:\www\Apache22\bin\Apache.Web.dll

> gacutil /ir Apache.Web.dll FILEPATH C:\www\Apache22\bin\Apache.Web.dll Apache.Web

Code:

C:\build\mod_aspdotnet>regasm /?

Microsoft (R) .NET Framework Assembly Registration Utility 1.0.3705.6018
Copyright (C) Microsoft Corporation 1998-2001.  All rights reserved.

Syntax: RegAsm AssemblyPath [Options]
Options:
    /unregister          Unregister types
    /tlb[:FileName]      Export the assembly to the specified type library
                         and register it
    /regfile[:FileName]  Generate a reg file with the specified name
                         instead of registering the types. This option
                         cannot be used with the /u or /tlb options
    /codebase            Set the code base in the registry
    /registered          Only refer to already registered type libraries
    /nologo              Prevents RegAsm from displaying logo
    /silent              Silent mode. Prevents displaying of success messages
    /verbose             Displays extra information
    /? or /help          Display this usage message

Code:

C:\build\mod_aspdotnet>gacutil /?

Microsoft (R) .NET Global Assembly Cache Utility.  Version 1.0.3705.0
Copyright (C) Microsoft Corporation 1998-2001. All rights reserved.

Usage: Gacutil <option> [<parameters>]
 Options:
  /i
    Installs an assembly to the global assembly cache.  Include the
    name of the file containing the manifest as a parameter.
    Example:  /i myDll.dll

  /if
    Installs an assembly to the global assembly cache and forces
    overwrite if assembly already exists in cache.  Include the
    name of the file containing the manifest as a parameter.
    Example:  /if myDll.dll

  /ir
    Installs an assembly to the global assembly cache with traced
    reference. Include the name of file containing manifest,
    reference scheme, ID and description as parameters
    Example:  /ir myDll.dll FILEPATH c:\apps\myapp.exe MyApp

  /u[ngen]
    Uninstalls an assembly. Include the name of the assembly to
    remove as a parameter. If ngen is specified, the assembly is
    removed from the cache of ngen'd files, otherwise the assembly
    is removed from the global assembly cache
    Examples:.
      /ungen myDll
      /u myDll,Version=1.1.0.0,Culture=en,PublicKeyToken=874e23ab874e23ab

  /ur
    Uninstalls an assembly reference. Include the name of the
    assembly, type of reference, ID and data as parameters.
    Example:  /ur myDll,Version=1.1.0.0,Culture=en,PublicKeyToken=874e23ab874e23
ab
                       FILEPATH c:\apps\myapp.exe MyApp

  /uf
    Forces uninstall of an assembly by removing all install references
    Include the full name of the assembly to remove as a parameter..
    Assembly will be removed unless referenced by Windows Installer.
    Example:  /uf myDll,Version=1.1.0.0,Culture=en,PublicKeyToken=874e23ab874e23
ab

  /l
    Lists the contents of the global assembly cache. Allows optional
    assembly name parameter to list matching assemblies only

  /lr
    Lists the contents of the global assembly cache with traced
    reference information. Allows optional assembly name parameter
    to list matching assemblies only

  /cdl
    Deletes the contents of the download cache

  /ldl
    Lists the contents of the downloaded files cache

  /nologo
    Suppresses display of the logo banner

  /silent
    Suppresses display of all output

  /?
    Displays this help screen

Looks like both are under .NET Framework Runtime -- I think.

Guess I will try it out later and report back.

If everything works, I'll post the mod_aspdotnet files on the d/l page for Apache 2.2.x.

[Jorge]

InstallShield is payware... http://www.installshield.com

but should be needed a bat script could register the dll and copy it for you...

but you need vs.net for the register command :(

[admin]

Yes, but I could have sworn that InstallShield DevStudio or some other InstallShield product came with VS.NET. Either way, both commands are part of .NET Framework -- you can not call them from the regular command line, you need to have the env set with .NET Framework. Just find the .NET Framework v1.0 or v1.1 path on the user's system and call the cmds. That and I also need the uninstall cmds -- the build does a quick register (different from above) and unregister so I should be able to figure it out... Actually, the  help text of the cmds is pretty clear.

[Jorge]

Yes, but I could have sworn that InstallShield DevStudio or some other InstallShield product came with VS.NET. Either way, both commands are part of .NET Framework -- you can not call them from the regular command line, you need to have the env set with .NET Framework. Just find the .NET Framework v1.0 or v1.1 path on the user's system and call the cmds. That and I also need the uninstall cmds -- the build does a quick register (different from above) and unregister so I should be able to figure it out... Actually, the  help text of the cmds is pretty clear.

There is the microsoft packaging thing that comes with VS.net... but its rather limited in costumization... while DevStudio is very flexable!

[admin]

Got everything working with mod_aspdotnet -- now I need to get mod_fcgid to work and figure out why PHP wont work as cgi and the new Suite will be out.

[GCam]

Are you suppose to place the index.aspx file into the ASP folder?  Or into the folder holding all your documents?  I currently have placed it into the ASP folder, and regardless of what I do, when I navigate to the root directory, it just automatically goes to the ASP folder and loads up the index.aspx file.  If i place the index.aspx file into the desired folder, it just gives me a Forbidden Error.  Any ideas?

Thanks

Greg

[admin]

Sounds like its working just as it should.

[admin]

It looks like the new mod_aspdotnet should be officially released soon...

From   "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject   [VOTE] Release mod_aspdotnet build 2004?
Date   Fri, 07 Jul 2006 05:40:52 GMT

Build 2004 of mod_aspdotnet is prepared (after a number of abortive
attempts due to the whole 2.0/2.2 partitioning and renaming of apache.exe,
along with switching flavors of InstallShield to a version I have installed)
and seeking voters.  The update is here;

   http://httpd.apache.org/dev/dist/mod_aspdotnet/

Please cast your +/- 1's to release mod_aspdotnet-2.x.0.2004-source.zip
(along with associated binaries ...2.0.0.2004.msi and ...2.2.0.2004.msi,
one corresponding to 2.0.44 and later, the other to 2.2.2 and later).

This is the last expected release on the Visual Studio .NET (al la 2002)
compiler toolchain; the next effort is porting it to VS 2005 (al la, the
one available in a free flavor).  Porting breaks compatibility with the
older tools, since VS 2005's C++.NET schema is miles beyond 2002.  For
example, a reference becomes a reference, not an overloaded psuedo-pointer.

Bill

[admin]

Only .NET v1.1 SP1 will work with our register/unregister mod_aspdotnet scripts.
http://forums.devside.net/viewtopic.php?t=1044