CODEWITHSUNDEEP
asp.netasp-classicincludeiis-7.5virtual
Bren
Bren

Reputation: 51

using Classic ASP INCLUDE VIRTUAL in ASP.NET page

I maintain an Classic ASP intranet site. I've developed a new page in ASP.NET that has a link to it from the old site. I would like to use the INCLUDE from the intranet which puts a header with menus on each page. I get a compile error when I run the new page in the debugger. The INCLUDE file contains nested INCLUDE files. The error says it can't find the nested includes. It's looking for them in the C:\xxxxxx when the actual physical path is on the d:\ drive.

Apparently it's resolving the INCLUDE VIRTUAL for the top level include, because it's looking for the nested includes.

Why does it resolve the first include, finding it on the D:\ drive, but is looking for the nested includes on the C:\ drive?

here's the code for the top level include

< !--#include virtual="/includes/page2header.asp"-->

here's the code for the nested includes

< !-- #INCLUDE virtual="/inc/menustyles.txt" -->

< !-- #INCLUDE virtual="/inc/Config.asp" -->

The site is running on IIS 7.5.

The site is located on the server on the default website in a virtual directory in the path D:\inetpub\wwwroot

The compiler is looking for the nested includes in this path with this error, Could not find a part of the path 'C:\inetpub\wwwroot\inc\menustyles.txt'

Upvotes: 1

Views: 4165

Answers (2)

Mike Brind
Mike Brind

Reputation: 30035

Include files don't work in the same way in ASP.NET as they do in classic ASP. When you use the Include directive, it results in the file content being rendered as plain text in the ASP.NET page. You will have to take an ASP.NET route to solve your problem. Typically, User Controls are used to render snippets of reusable HTML.

See my article on this topic for more information: http://www.mikesdotnetting.com/Article/144/Classic-ASP-Include-Files-in-ASP.NET

Upvotes: 1

Bren
Bren

Reputation: 51

The problem I was having here is I was running the debugger on my development machine, and it's virtual directory IS on the C:\ drive for this site, and the first level virtual file did exist in the path where the compiler was looking for it, and the nested files did not exist. The problem was solved when I copied the nested files into place on the development machine.

However, that raised a new problem. The nested files contain server side script, Classic ASP VBScript, and it just won't run in my ASP.NET page. This problem brings this effort to a dead end, unless someone can recommend how to solve this new problem.

Thanks, Bren

Upvotes: 1

Related Questions