Thread: SF.net SVN: mod-aspdotnet: [167] mod_aspdotnet/trunk/docs

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Revision: 167
          http://svn.sourceforge.net/mod-aspdotnet/?rev=167&view=rev
Author:   wrowe
Date:     2006-10-12 10:46:02 -0700 (Thu, 12 Oct 2006)

Log Message:
-----------
Now hosted at Sourceforge, the source site generation files don't
make much sense anymore.

Removed Paths:
-------------
    mod_aspdotnet/trunk/docs/introduction.xml
    mod_aspdotnet/trunk/docs/mod_aspdotnet.html
    mod_aspdotnet/trunk/docs/mod_aspdotnet.xml
    mod_aspdotnet/trunk/docs/mod_aspdotnet.xml.meta

Deleted: mod_aspdotnet/trunk/docs/introduction.xml
===================================================================

--- mod_aspdotnet/trunk/docs/introduction.xml	2006-09-07 19:00:16 UTC (rev 166)
+++ mod_aspdotnet/trunk/docs/introduction.xml	2006-10-12 17:46:02 UTC (rev 167)
@@ -1,193 +0,0 @@
-<?xml version="1.0"?>
-<document>
-  <properties>
-    <author email="us...@ht...">Apache httpd users</author>
-    <title>Introduction to mod_aspdotnet</title>
-  </properties>
-<body>
-
-<section id="Server">
-<title>What is the Apache HTTP Server?</title>
-
-<p>The Apache HTTP Server is a robust implementation of an HTTP/1.1 server
-which runs on Windows, various flavors of unix and other modern operating
-systems.  It is a modular framework, which allows modules supporting various
-features to be loaded, or not, as required by the administrator.</p>
-
-<p>The mod_aspdotnet module is provided only for the Windows operating system,
-and this module won't work for the other operating systems.  See the
-<a href="http://httpd.apache.org/mod_aspdotnet/">mod_aspdotnet main page</a>
-for alternatives available to users of other operating systems.</p>
-
-<p>This document will introduce you to all of the key concepts you might be
-unfamiliar with, introduce you to mod_aspdotnet and the purpose it serves,
-and what you can accomplish with it.  This document is a work in progress,
-feedback is welcome at the users mailing list.</p>
-
-<p>See the <a href="http://httpd.apache.org/mod_aspdotnet/">mod_aspdotnet
-pages</a> for information about mailing lists, other resources and how to 
-participate in these ongoing efforts!</p>
-
-</section>
-<section id=".NET">
-<title>What Is .NET?</title>
-<p>Microsoft's marketing of .NET is a vision encompasing a wide spectrum of 
-technologies, not one specific new technology.  This leads to much confusion 
-about .NET development, and what web development under .NET really entails.</p>
-
-<p>The deepest underpinning of .NET is a new program execution model, the CLR
-(Common Language Runtime), which hosts IL (Intermediate Language) code.  
-This model is very similar to Java's JVM running .class'es compiled into
-Java bytecode.  Far different than the classic interpreted script (such as
-Perl) or compiled machine code (such as C or C++), the CLR enforces rules 
-to ensure code trust, machine security and data integrity.  Many languages 
-are already available for writing code to run within the CLR, including 
-C#, and Microsoft's C++.NET, VisualBasic.NET and J#.  Many third party 
-companies are bringing additional languages to the .NET managed code world, 
-there are more than 20 different languages shipping today.</p>
-
-<p>Microsoft's .NET Framework includes many core facilities, packaged as 
-language-agnostic classes that can be generally used by any .NET language.
-It includes the C# compiler, and the ASP.NET related classes.</p>
-
-</section>
-<section id="ASP.NET">
-<title>What Is ASP.NET?</title>
-<p>ASP.NET (known inside the .NET framework as System.Web) is a hosting 
-environment for web applications that provides facilities to query and 
-collect information about the current request, prepare the response, and 
-maintain session state information.  ASP.NET simplifies the chore of 
-building web applications down to the essential task of generating and 
-serving content.</p>
-
-<p>The converse question, "are ASP.NET and ASP the same thing?", deserves 
-a resounding answer of <strong>NO</strong>.  Although in some respects 
-they offer similar facilities, they have no relation to each other.  
-mod_aspdotnet only provides the ASP.NET environment, and does nothing 
-for ASP content.  Simply put, ASP.NET has replaced ASP, and ASP runs in 
-its own environment(s), (one per scripting language) and not inside the 
-.NET framework.</p>
-
-<p>If you have ASP pages to serve, consider porting them to ASP.NET.
-There are many fine books and online guides to assist you.</p>
-
-</section>
-<section id="mod_aspdotnet">
-<title>What is mod_aspdotnet?</title>
-
-<p>This is actually two modules; the first, mod_aspdotnet.so, is an in-process 
-Apache 2.0 module, which starts the ASP.NET engine and hands off requests
-to the ASP.NET engine.  There is a second module compiled for .NET, which
-is named Apache.Web.dll.  The Apache.Web.dll is loaded into Microsoft's ASP.NET
-host environment, and dispatches request and response operations back to
-the mod_aspdotnet.so.  This combination of managed (.NET-side) and 
-unmanaged (Apache-side) code, running in the same process as the Apache 2.0 
-server, attains very optimal performance for serving ASP.NET content.  The 
-solution maintains tight compatibility with existing, IIS-hosted ASP.NET,
-because the same Microsoft ASP.NET hosting environment is running under 
-either of these scenarios.</p>
-
-<p>Multiple ASP.NET virtual webs are supported by the mod_aspdotnet module.  
-A request is directed to the asp.net handler using conventional Apache 
-configuration options, and is mapped to a specific ASP.NET virtual web by
-matching the requested URI to the AspNetMount directives given for the 
-specific Apache virtual host, uri, and file location.  The same AspNetMount 
-can be given in multiple Apache virtual hosts.  Any given AspNetMount is 
-created only once for all Apache virtual hosts that share the same AspNetMount,
-conserving memory and resources.</p>
-
-<p>AspNetMount and other directive changes are processed when the server is 
-restarted.  With Apache 2.0, the original Windows child process continues to 
-serve requests until a new child process is ready to process requests itself. 
-This provides minimal interruption of service when modifying the web server 
-configuration.  The restart option begins a graceful restart sequence, loading 
-and initializing the new server while the old server finishes fulfilling open 
-requests, and there is no interruption in web services during the transition 
-from the old to the new configuration.</p>
-
-<p>This is not a module for Unix platforms.  The Mono project's mod_mono 
-provides very similar features for non-Win32 machines, with their own 
-implementation of ASP.NET for Apache httpd server.</p>
-
-</section>
-<section id="Starting">
-<title>Getting Started</title>
-
-<p>Microsoft's .NET Framework is available as a free download for Windows 2000 
-or 2003 Professional and Server versions, XP Professional, and .NET Server 
-platforms from 
-<a href="http://asp.net/download.aspx">http://asp.net/download.aspx</a>.
-You must minimally install the .NET Framework Resdistributable version, while 
-developers will prefer to install the .NET Framework Software Development Kit, 
-or another .NET development tool such as VisualStudio .NET.</p>
-
-<p>This module effort explicitly does not support Windows NT, ME, or 9x.  If you
-are using a version of Windows prior to Windows 2000, your results will vary.
-Please don't waste the developer's time contacting the project with questions
-about these historical footnote platforms.</p>
-
-<p>Once you download and install the mod_aspdotnet .msi package, it will 
-install both mod_aspdotnet.so into your Apache2/modules/ directory, and the 
-Apache.Web.dll into the Global Assembly Cache.  You then need to modify your 
-Apache2/conf/httpd.conf file to load the mod_aspdotnet.so module, and declare 
-what content you will serve.  See the <a href="mod_aspdotnet">mod_aspdotnet</a>
-module documentation for the directives to add for a typical scenario, or 
-follow the Example below.</p>
-
-</section>
-<section id="Example">
-<title>An Example Configuration - Microsoft's IBuySpy Sample</title>
-
-<p>The following configuration will support the Microsoft IBuySpy sample, an 
-illustration of a web storefront.  IBuySpy is available as a free download 
-from <a href="http://asp.net/ibuyspy/">http://asp.net/ibuyspy/</a>.  Note that 
-Microsoft SQL Server version 7.0 must be installed before installing the 
-Microsoft IBuySpy sample.  The configuration below illustrates configuration 
-for the C# flavor of the IBuySpy Store sample, installed into the default 
-installation directory:</p>
-
-<pre>
-LoadModule aspdotnet_module modules/mod_aspdotnet.so
-
-# Use the asp.net handler for all common ASP.NET file types
-AddHandler asp.net asax ascx ashx asmx aspx axd config cs csproj \
-                   licx rem resources resx soap vb vbproj vsdisco webinfo 
-
-&lt;IfModule mod_aspdotnet.cpp&gt;
-
-    # Mount the IBuySpy C# example application
-    AspNetMount /StoreCSVS "C:/StoreCSVS/StoreCSVS"
-
-    # Map all requests for /StoreCSVS to the IBuySpy application files
-    Alias /StoreCSVS "C:/StoreCSVS/StoreCSVS"
-
-    # Allow asp.net scripts to be executed in the IBuySpy example
-    &lt;Directory "C:/StoreCSVS/StoreCSVS"&gt;
-        Options FollowSymlinks
-        AspNet Files
-        Order allow,deny
-        Allow from all
-        DirectoryIndex Default.htm Default.aspx
-    &lt;/Directory&gt;
-
-    # For all virtual ASP.NET webs, we need the aspnet_client files 
-    # to serve the client-side helper scripts.
-    AliasMatch /aspnet_client/system_web/(\d+)_(\d+)_(\d+)_(\d+)/(.*) \
-          "C:/Windows/Microsoft.NET/Framework/v$1.$2.$3/ASP.NETClientFiles/$4"
-    &lt;Directory \
-          "C:/Windows/Microsoft.NET/Framework/v*/ASP.NETClientFiles"&gt;
-        Options FollowSymlinks
-        Order allow,deny
-        Allow from all
-    &lt;/Directory&gt;
-
-&lt;/IfModule&gt;
-</pre>
-
-<p>Configuring the VisualBasic.NET version is very similar, simply change the 
-<code>StoreCSVS</code> directory names above, to <code>StoreVBVS</code>.</p>
-
-</section>
-</body>
-</document>
-

Deleted: mod_aspdotnet/trunk/docs/mod_aspdotnet.html
===================================================================
--- mod_aspdotnet/trunk/docs/mod_aspdotnet.html	2006-09-07 19:00:16 UTC (rev 166)
+++ mod_aspdotnet/trunk/docs/mod_aspdotnet.html	2006-10-12 17:46:02 UTC (rev 167)
@@ -1,3 +0,0 @@
-URI: mod_aspdotnet.html.en
-Content-Language: en
-Content-type: text/html; charset=ISO-8859-1

Deleted: mod_aspdotnet/trunk/docs/mod_aspdotnet.xml
===================================================================
--- mod_aspdotnet/trunk/docs/mod_aspdotnet.xml	2006-09-07 19:00:16 UTC (rev 166)
+++ mod_aspdotnet/trunk/docs/mod_aspdotnet.xml	2006-10-12 17:46:02 UTC (rev 167)
@@ -1,227 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE modulesynopsis SYSTEM "http://httpd.apache.org/docs-2.0/style/modulesynopsis.dtd">
-<?xml-stylesheet type="text/xsl" href="http://httpd.apache.org/docs-2.0/style/manual.en.xsl"?>
-<!-- $LastChangedRevision$ -->
-
-<!--
- Copyright 2002-2004 The Apache Software Foundation
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-
-<modulesynopsis metafile="mod_aspdotnet.xml.meta">
-
-<name>mod_aspdotnet</name> 
-<description>Provides an interface for ASP.NET content between Apache HTTP
-Server 2.0 and Microsoft's ASP.NET host.</description>
-<status href="http://httpd.apache.org/mod_aspdotnet/">External</status>
-<sourcefile>mod_aspdotnet.cpp</sourcefile>
-<identifier>aspdotnet_module</identifier>
-<compatibility>Compatible only with httpd 2.0.44 and later.</compatibility>
-
-<summary>
-    <p>The <directive module="mod_aspdotnet">AspNet</directive> and
-    <directive module="mod_aspdotnet">AspNetMount</directive> directives
-    and asp.net handler provided by <module>mod_aspdotnet</module> are used
-    to configure content to be served of the ASP.NET engine.</p>
-
-    <p>The current version is compatible with the .NET Framework versions 1.x
-    (1.0, 1.1, etc).  The current version is not compatible with .NET Framework 
-    version 2.0 although this may be addressed in the future.</p>
-
-    <p>Only modern Windows NT-based operating systems (2000, XP, 2003, etc) are 
-    supported.  Older versions such as Windows 98 and ME are not, Windows NT 6 
-    requires Service Pack 6, and the module authors will not invest time or
-    effort on these older versions.  Do not contact the project regarding 
-    support of older operating systems.</p>
-</summary>
-
-<seealso><a href="../handler.html">Configuring Handlers</a></seealso>
-
-<section id="usage"><title>Usage</title>
-    <p>Several global configurations must be given to enable the Apache
-    HTTP Server to correctly serve ASP.NET application content.</p>
-
-    <example><title>Example:</title>
-LoadModule aspdotnet_module modules/mod_aspdotnet.so <br />
-<br />
-AddHandler asp.net asax ascx ashx asmx aspx axd config cs csproj \<br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-                   licx rem resources resx soap vb vbproj vsdisco webinfo<br />
-<br />
-AliasMatch "^/(?i)aspnet_client/system_web/(\d+)_(\d+)_(\d+)_(\d+)/(.*)" \<br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-           "C:/Windows/Microsoft.NET/Framework/v$1.$2.$3/ASP.NETClientFiles/$4"<br />
-<br />
-&lt;Directory "C:/Windows/Microsoft.NET/Framework/v*/ASP.NETClientFiles"&gt;<br />
-&nbsp;&nbsp;&nbsp;&nbsp;Options FollowSymlinks<br />
-&nbsp;&nbsp;&nbsp;&nbsp;Order allow,deny<br />
-&nbsp;&nbsp;&nbsp;&nbsp;Allow from all<br />
-&lt;/Directory&gt;<br />
-    </example>
-
-    <p>This will direct all requests for ASP.NET-releated files to the 
-    mod_aspdotnet handler, and serve Microsoft's ASP.NET client files 
-    and support scripts as expected by ASP.NET applications.</p>
-
-    <p>Provide individual <directive module="mod_aspdotnet"
-     >AspNet</directive> and <directive module="mod_aspdotnet"
-     >AspNetMount</directive> directives for each application (containing 
-    a unique web.config file at it's application root.)</p>
-
-    <example><title>Example:</title>
-AspNetMount /app-uri "C:/path/to/app"<br />
-Alias /app-uri "C:/path/to/app"<br />
-&lt;Directory "C:/path/to/app"&gt;<br />
-&nbsp;&nbsp;&nbsp;&nbsp;Options FollowSymlinks Indexes<br />
-&nbsp;&nbsp;&nbsp;&nbsp;AspNet files<br />
-&nbsp;&nbsp;&nbsp;&nbsp;Order allow,deny<br />
-&nbsp;&nbsp;&nbsp;&nbsp;Allow from all<br />
-&nbsp;&nbsp;&nbsp;&nbsp;DirectoryIndex default.htm default.aspx<br />
-&lt;/Directory&gt;<br />
-    </example>
-
-</section>
-
-<directivesynopsis>
-<name>AspNet</name>
-
-<description>Enables mod_aspdotnet to process ASP.NET content</description>
-<syntax>AspNet [[<var>Files</var>] [<var>Directories</var>] 
-                [<var>Virtual</var>] [<var>Errors</var>]]
-              | [<var>All</var>] | [<var>None</var>]</syntax>
-<default>AspNet None</default>
-<contextlist><context>server config</context><context>virtual host</context>
-<context>directory</context><context>.htaccess</context>
-</contextlist>
-<override>Options</override>
-<compatibility>Build 2004 and later</compatibility>
-
-<usage>
-
-    <p>The <directive>AspNet</directive> directive determines what content
-    may be served by the ASP.NET host.  This directive does -not- actually 
-    expose the content or mount the URI to physical files, you must use the 
-    <directive module="mod_alias">Alias</directive> and
-    <directive>AspNetMount</directive> directives to expose the content
-    to the remote user.</p>
-
-    <p>The <directive>AspNet</directive> <var>files</var> directive is
-    the equivilant for ASP.NET files to the behavior of Options ExecCGI 
-    for CGI content.  In the original version of mod_aspdotnet, in fact,
-    Options ExecCGI was used to determine if ASP.NET content would be
-    invoked through mod_aspdotnet.  In version 2.0.2 and later, this is
-    no longer true, and your configuration files must be updated from
-    Options ExecCGI to AspNet files.</p>
-
-    <p>The None option disables all ASP.NET processing, while the individual
-    options below enable ASP.NET processing for specific request types:</p>
-
-    <dl>
-      <dt><code>All</code></dt>
-
-      <dd>All options below. This is generally not a recommended setting.</dd>
-
-      <dt><code>Files</code></dt>
-
-      <dd>Files that exist in the filesystem, which are directed to the
-      asp.net handler.</dd>
-
-      <dt><code>Directories</code></dt>
-
-      <dd>Directories that exist in the filesystem, which are directed to the
-      asp.net handler.  This can be used to invoke an HttpHandler to produce
-      custom directory listings.</dd>
-
-      <dt><code>Virtual</code></dt>
-
-      <dd>Requests that map to neither a file nor directory in the filesystem,
-      which are directed to the asp.net handler.  This is used to invoke any
-      HttpHandler which accesses non-file based resources, such as ASP.NET
-      remoting requests.</dd>
-
-      <dt><code>Error</code></dt>
-
-      <dd>Error result pages generated by ASP.NET.  This option bypasses the
-      normal Apache ErrorDocument error content.  This is required to return
-      the full debugging results from the ASP.NET environment in development
-      environments.  Caution is urged before using this option in production
-      environments, where path-revealing flaws should be avoided.</dd>
-
-    </dl>
-
-    <p>Normally, if multiple <directive>AspNet</directive> directives could
-    apply to a directory, then the most specific one is used and others are
-    ignored; the AspNet directives are never merged.  See <a
-    href="../sections.html#mergin">how sections are merged</a> for a better
-    understanding of which Files, Directory, or Location section will take
-    precedence.</p>
- 
-</usage>
-</directivesynopsis>
-
-<directivesynopsis>
-<name>AspNetMount</name>
-
-<description>Mounts a URI to a physical ASP.NET directory</description>
-<syntax>AspNetMount <var>URL-path</var> <var>directory-path</var></syntax>
-<contextlist><context>server config</context>
-</contextlist>
-
-<usage>
-
-    <p>The <directive>AspNetMount</directive> directive determines which
-    physical directory is mounted by the ASP.NET host.  This directive
-    does -not- actually expose the content, you must use the 
-    <directive module="mod_alias">Alias</directive>
-    directive to expose the content to the remote user.</p>
-
-</usage>
-</directivesynopsis>
-
-<directivesynopsis>
-<name>AspNetVersion</name>
-
-<description>Force a specific .NET Framework version to be loaded</description>
-<syntax>AspNetVersion <var>versionstring</var></syntax>
-<contextlist><context>server config</context>
-</contextlist>
-<compatibility>Build 2004 and later</compatibility>
-
-<usage>
-
-    <p>The <directive>AspNetVersion</directive> directive will override the
-    default (most current) .NET Framework environment, and elect a different
-    installed version of the .NET Framework.  The chosen version must be
-    installed on the machine.</p>
-
-    <p>If this directive is not present, the most current .NET Framework version
-    is used.  This directive should be specified only once, only the last occurance
-    in the httpd.conf file is used to elect the .NET Framework version.</p>
-
-    <p>See the c:\Windows\Microsoft.NET\Framework\ directory for all installed
-    versions and their version tags (the actual directory names).</p>
-
-    <example><title>Example:</title>
-# Load mod_aspdotnet using the 1.0 release version of the .NET Framework
-AspNetVersion v1.0.3705<br />
-    </example>
-
-    <example><title>Example:</title>
-# Load mod_aspdotnet using the 1.1 release version of the .NET Framework
-AspNetVersion v1.1.4322<br />
-    </example>
-
-</usage>
-</directivesynopsis>
-</modulesynopsis>

Deleted: mod_aspdotnet/trunk/docs/mod_aspdotnet.xml.meta
===================================================================
--- mod_aspdotnet/trunk/docs/mod_aspdotnet.xml.meta	2006-09-07 19:00:16 UTC (rev 166)
+++ mod_aspdotnet/trunk/docs/mod_aspdotnet.xml.meta	2006-10-12 17:46:02 UTC (rev 167)
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" ?>
-
-<metafile>
-  <basename>mod_aspdotnet</basename>
-  <path>/mod/</path>
-  <relpath>..</relpath>
-
-  <variants>
-    <variant>en</variant>
-  </variants>
-</metafile>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.




Thread: SF.net SVN: mod-aspdotnet: [167] mod_aspdotnet/trunk/docs

mod-aspdotnet-svn