Tags: app, asp, classic, compiling, failed, include, includes, lt-, map, microsoft, msdn, net, path, server, software, studio, visual

"Failed to Map the Path"

On Microsoft » Microsoft Visual Studio

1,273 words with 2 Comments; publish: Sat, 05 Jan 2008 20:35:00 GMT; (300109.99, « »)

Hello,

I'm having a problem compiling my ASP.NET 2.0 app that is using Classic ASP Server Side Includes.<!-- #include virtual="/include/headerlogo.inc" -->

I get this very annoying error "Failed to map the path '/include/headerlogo.inc'." If I actually try to view the site it works fine and their aren't any problems but when I try to Publish the site so I can move it to production this error comes up and the dlls aren't created. I've had no problems using this in Visual Studio .NET 2003 but it seems VS 2005 has some additional validation is performs when building. Is there any way to fix this?

All Comments

Leave a comment...

  • 2 Comments
    • Have you tried using.ClientScript.RegisterClientScriptInclude() method instead? This is the preferred approch for using #include files in .NET
      #1; Sat, 05 Jan 2008 20:36:00 GMT
    • It does not appear to work when I place:

      Page.ClientScript.RegisterClientScriptInclude("HeaderInc","/include/headerlogo.inc")

      Into the Page_Load event of the page.

      Unless i'm using it wrong this does not appear to fix my problem.

      #2; Sat, 05 Jan 2008 20:37:00 GMT