What you're missing is
1. mapping the application to aspnet_isapi.dll.
drive:\WINDOWS\MICROSOFT.NET\FRAMEWORK\Vx.x.xxxxx\aspnet_isapi.dll
There's several extensions which you should map to aspnet_isapi.dll.
See a list at :
http://www.microsoft.com/mspress/books/sampchap/6667.asp
You probably should look at running aspnet_regiis.exe for the virtual
root you created, with the parameters you desire, typically -i .
and
2. setting the default document to "default.aspx".
You'd have to use ADSI for that :
'Only setting two properties
vDir.DefaultDoc = vDir.DefaultDoc & ",default.aspx"
'Write information back to Metabase
vDir.SetInfo
See http://www.15seconds.com/issue/980304.htm for an example.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================
>I came up with a work-around; but I'd still appreciate any suggestions so that I don't
>have to do this work-around:
[quoted text clipped - 37 lines]
>>
>> Thanks!
Frankie - 15 Jul 2005 22:39 GMT
Thanks Juan,
What my utility was missing was a call to AppCreate2.
Basically the application wasn't being created correctly in IIS even though
I was explicitly setting all of the metabase properties (or at least those
properties that I could see through Metabase Explorer).
And, just in case others are interested in this thread, I tried
aspnet_regiis as suggested, but it didn't solve the problem. I'm not sure
what all AppCreate2 does behind the scenes, but whatever it does is
apparently necessary; and not all of its changes are apparent in Metabase
Explorer.
Thanks again!
-F
> What you're missing is
>
[quoted text clipped - 77 lines]
>>>
>>> Thanks!