Odd Ball Situation

[Steve Repp]

Never seen anything like this. I have a C# app on the web that executes as
expected, except for one subdirectory.

In this particular subdirectory, the application fails to execute the C#
code and just returns the code as static HTML.

No compilation errors. No missing refs.

No idea what could be wrong!

Any ideas?

[Josh Twist]

Sounds like what happens when IIS hasn't had ASP.NET registered with
it. Go to the virtual directory in IIS and view it's properties. Click
the Configuration button on the Directory tab. Under Mappings you
should see that .aspx, .asmx, .asax etc are all registered (and use
..NET's aspnet_isapi.dl l).

If your folder isn't a Virtual Directory then it must be inheriting
it's application configuration from a higher folder.

Is this the case for all folders on this machine? If so, you just need
to register aspnet with IIS (using aspnet_regiis -i at the .NET command
prompt). If it's just the virtual, you could probably delete and
recreate it - it should get the default settings like all the others
then.

Let me know how you get on.

Josh
http://www.thejoyofcode.com/

[Steve Repp]

Appreciate the answer. The topology is as follows:

/root <<< aspx files work.
/root/Sales <<< aspx files work.
/root/MembersArea <<< aspx files fail. (Physical dir, not virt.)

Given this, any other possibilities?
On 3/9/06 3:40 AM, in article
11************* *********@j33g2 00...legr oups.com, "Josh Twist"
<jo********@gma il.com> wrote:

Sounds like what happens when IIS hasn't had ASP.NET registered with
it. Go to the virtual directory in IIS and view it's properties. Click
the Configuration button on the Directory tab. Under Mappings you
should see that .aspx, .asmx, .asax etc are all registered (and use
.NET's aspnet_isapi.dl l).
If your folder isn't a Virtual Directory then it must be inheriting
it's application configuration from a higher folder.

Is this the case for all folders on this machine? If so, you just need
to register aspnet with IIS (using aspnet_regiis -i at the .NET command
prompt). If it's just the virtual, you could probably delete and
recreate it - it should get the default settings like all the others
then.

Let me know how you get on.

Josh
http://www.thejoyofcode.com/

[Josh Twist]

Hmm..

What OS/Version of IIS are you running?

Is the Physical Directory configured to run as an application (If
you're not sure, view the properties of the directory (in iis) and on
the Directory tab you should see a create button. If this button is
disabled your directory is running as an application). If so, click the
configuration button and check that aspx etc are registered properly as
explained above.

Is 'script source access' checked? Are the Execute Permissions set to
'Scripts only' or 'Scripts and Executables'? Is there anything
different about the physical directory's setup (maybe Authentication
for your members area)?

Interesting.

Josh
http://www.thejoyofcode.com/