applications below CS

Did you set the second app to be a virtual directory?

I asked my provider to designate the directory of the second app as an asp.net 2.0 application, and they said they did that.

The problem that you are having is an IIS configuration issue.  Either the Virtual Directory does not exist with that name, the folder/file does not exist, or the "Local Path" of the Virtual Directory is pointing to a folder that is different from where you placed the application files.  It all depends upon how the Virtual Directory was created.

If you created the application folder under the CS root, then your host provider went into the IIS Manager, clicked on "Properties" for that folder, and clicked on "Create" under Application Settings, this should work.  I have a feeling that he went the other route which asks for a "Local Path" and did not tell you where that folder is.

I hope this helps,
Bill

flashie_dirk:

I'm using CS2.1 (running on ASP.NET 2.0) and I'm trying to get another asp.net 2.0 application below cs to work.

My CS installation is at the root of my domain: http://questmaster.net/

I would like to have another application here: http://questmaster.net/qml/default.aspx. When I try to call this page, however, I get a page not found error.

I'm not asking you to debug my own application of course - all I want to know is if there is anything in CS 2.1 that would prevent "subapplications" from working.  Thanks!

 

This tutorial written by Tod Birdsall might help.  

I hope CS 3.0 will bring a cleaner solution to this scenario.  While we embrace CS in some of our work it's not the only application and we can't assume, for the sake of performance, that we'll want to load it up all the time.

I was quite surprised to see that we were unable to strong name the assemblies for GAC'ing because of circular references.  It seems like there are better ways to design around circular references (e.g. interfaces).

Cheers,
Colin & the officalCOMMUNITY team.
 

I don't think the tutorial is relevant for me because my own "qml" application can/should be blissfully unaware of community server.  And communitserver should be unaware of qml.

Bill Bosacker:

The problem that you are having is an IIS configuration issue.  [...]  I have a feeling that he went the other route which asks for a "Local Path" and did not tell you where that folder is.

I hope this helps,
Bill

 So what you are saying is basically "there's nothing in CS that should prevent your scenario from working, and it's probably your provider who messed up" - right?

The Wizard:

This tutorial written by Tod Birdsall might help.  

 I'll be <something nasty>.  After trying around for some time and being baffled every second of it, I decided to give the tutorial a trial.  I did everything described in there, and suddenly my own application worked.

This is so wrong - why should I have to link to 4 MB worth of CS-dlls and two config files, just to get my own app working that doesn't even use any CS features in the first place?!?  I hope CS 3.0 will fix this, and I hope that it will come soon.

flashie_dirk:

So what you are saying is basically "there's nothing in CS that should prevent your scenario from working, and it's probably your provider who messed up" - right?

That is correct, but I just remembered one thing.  There is a feature that I have never been forced to use, but one that CS heavily uses.  I forget what the feature is called, but it allows you to intercept all IIS requests for your application folder tree prior to .NET page request, this was only available through the ISAPI interface, but it is now configuarable in the web.config of any web application.  The authorization and error handling systems are heavily entangled in this interface.

If done properly, objects using this interface will run faster than those that do not, but they are much more difficult to design and debug and usually are not worth the added effort if you have designed a scalable web farm system.  If you look into the web.config, the configuration/system.web/httpModules section is what is performing the overrides.  It forces every request to go through CommunityServerComponents20/HttpModule/CSHttpModule.cs.

I hope this helps,
Bill

Bill, that sounds very intriguing - I hadn't heard of this feature but in the light of this, a lot of the mystery begins to make sense.  I'll check this out tomorrow.