Reference

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

Comments and Discussions

Hi everyone can anybody tell me how compatible asp.net project with apache 2.2....we r planning to host website using asp.net with Apache webserver...does this works? if yes can u tell me hw can i implement it...? if no please tell me the reason and in which way it can be implemented....

The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

I had trouble installing Cassini. I ran the build.bat from the Start-Run menu, but it didn't successfully run gacutil. Another reply had mentioned that gacutil doesn't always work, and suggested copying the cassini.dll to the c:\WINDOWS\assembly directory (this is the directory name if you are using Windows XP).I couldn't copy/paste the file, but I was able to tag and drag it to the directory.

That took care of the gacutil problem.

The next problem I ran into was that IIS needed to not be running. It can be turned off from the Apache-Services menu. (Or, Control Panel-Administrative Tools-Internet Information Services, IIS).

I needed to fill in the blanks on the Cassini panel with:Application: c:\inetpub\wwwrootport: 8080 (port 80 didn't work for me, conflict)Virtual Root: /

This worked for me, I could click on the link for the localhost and see the files I'd copied to the inetpub/wwwroot directory. I could click on an aspx file, and the aspx page did work correctly.

I needed to have IIS stopped, and Cassini started, to create a new project in Visual Studio.NET.

Unfortunately, in my attempts to get stuff working, I messed with the virtual directories and their file permissions ... now I can't get Cassini to run the aspx files anymore.

For what it's worth, we got it up and running. The trick is to run the gacutil command in the VS.NET command prompt utility to register the Cassini dll in the global assembly cache. Afterwards, everything worked fine. This whole approach is a bit of a hack, obviously. The cleaner approach is to use the Apache CLI library. If you're running a 1.3 production version, you can install 2.0 side by side and run the CLI on it.

sorry for the confusion. i now understand that the line i typed in the previous post is to be typed at a command prompt, but i'm still unsure as to what "Create a different catalog (not the /aspnet catalog in http.conf) for your ASP.NET files " is asking me to do. thanks.

The advantage as I see it, resides in the freedom to *not* use IIS 5 and this translates in be able to use an older Windows version (supported by the .NET Framework). As far as I know Windows XP Home doesn't have IIS as an install option (without some dark hackings) and you can't upgrade IIS 4 from your Windows2000 to IIS 5. Besides I assume that the IIS that comes with Windows XP Pro is more like the one that came with Windows 2000 Pro, kind of a watered down version with tendencies to PWS. Microsoft will probably encourage you to get Windows 2003 Server for production deployments which is too expensive and inmature for my taste.