I don't think that's the problem. My laptop PC doesn't have that filter
configured and runs fine. But, just to be sure, I added that filter as you
suggested, rebooted, and tried again. No change. Oh, the "Status" column of
this dll had a red down arrow, and the "Priority" column contained
*Unknown*". Unfortunately, the documentation didn't explain how to change
the Status or Priority.
Incidentally, here is possibly another clue. I get the download dialog box
when I explicitly specify the aspx file name default.aspx. If I leave off
that file, it apparently can't find it, or there is some other problem,
since I then get the error "You are not authorized to view this page". Yet
this works fine with the application on my laptop.
"Robin Bonin" <ro***@guavatools.com> wrote in message
news:gwWmb.31058$iq3.21776@okepread01...
Sounds like the isapi filter is not running, or is not configured
correctly. look in the IIS control pannel and check that aspnet_isapi.dll is listed
under
isapi filters.
"Don Peters" <don-peters@NOSPAM!comcast.net> wrote in message
news:Oz**************@TK2MSFTNGP12.phx.gbl... I'm relatively new to ASP.NET. I'm running it under Win XP Pro, using Visual Studio 2002.NET (haven't migrated to VS2003 yet).
The ASP.NET application I'm having a problem with was initially set up
on a laptop running Win2000, where it ran successfully.
I've copied all the files over to my desktop, intending to support it
there. But it seems to have a problem upon startup: instead of initially
displaying the starting ASP.NET page as it should, it instead brings up the file
download dialog box, trying to download the starting ASP.NET page from
my local PC! If I click on OK, it appears to load the page, then stops
without displaying the page.
I've only tried one other very small ASP.NET application on this desktop
PC, and it seemed to run fine. But this problem application is much bigger.
It appears as if some system parameter is not set correctly, but I have
no idea what it is.
Can anyone offer a suggestion?
Don
ps
I first posted this to newsgroup
microsoft.public.inetserver.asp.general, but was directed here instead.