IIS 6.0, InterDev 6.0 and DTC

External Since: Mar 10, 2004 Posts: 6

I have moved a site designed in Visual InterDev 6.0 and it uses Design Time Controls. The ASP pages have this line of code automatically enterred at the top of each page that uses these controls:

<% ' VI 6.0 Scripting Object Model Enabled %><% if StartPageProcessing() Then Response.End() %><FORM name=thisForm METHOD=post>

By default IIS 6.0 has Disallowed Parent Path set to false in it’s metabase for security reasons. This prevents the use of syntax that has:


When we try to navigate to one of these pages the browser pops up a File Download box to Open, Save or Cancel the document loading.

Can this be fixed withOUT re-Enabling Parent Paths in IIS 6.0?

Thanks,
- bostonnole -

External Since: Aug 25, 2003 Posts: 2419

If you do not change existing pages, then it is impossible for your syntax
to work without ASPEnableParentPaths.

My suggestion is to make the include using "virtual" instead, which can
easily have their mappings changed without needing to use relative ..
reference schemes.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Robert" <anonymous DeleteThis @discussions.microsoft.com> wrote in message
news:06503018-9626-4D34-98DF-13C5E1AFB900@microsoft.com...
I have moved a site designed in Visual InterDev 6.0 and it uses Design Time
Controls. The ASP pages have this line of code automatically enterred at
the top of each page that uses these controls:

<% ' VI 6.0 Scripting Object Model Enabled %><% if StartPageProcessing() Then
Response.End() %><FORM name=thisForm METHOD=post>

By default IIS 6.0 has Disallowed Parent Path set to false in it's metabase
for security reasons. This prevents the use of syntax that has:


When we try to navigate to one of these pages the browser pops up a File
Download box to Open, Save or Cancel the document loading.

Can this be fixed withOUT re-Enabling Parent Paths in IIS 6.0?

Thanks,
- bostonnole -