Home/ Questions/Q 101487
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T00:46:50+00:00

I’m using a web deployment project in order to precompile my ASP.NET 3.5 web

  • 0

I’m using a web deployment project in order to precompile my ASP.NET 3.5 web project. It creates a single extra DLL for the code in aspx and ascx files. And, for every aspx file there is a placeholder aspx file (empty) which needs to be copied to the server.

I’d like to simplify the deployment process. Is there a way (configuring the IIS site and adding some sort of http handlers etc.) to get rid of these aspx placeholders?

Also, I’d like to know if there is a way to get rid of the .compiled files in the bin folder. It would make the deployment process smoother.

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I discovered it by myself. It is much easier than I thought (IIS 6.0):

    In Internet Information Manager go to the property page of the site, then chose the tab ‘Home Directory’ and click on the button ‘Configuration…’.

    Click ‘Edit…’ for the .aspx ISAPI extension and uncheck ‘Verify that file exists’. At this point, no aspx file is needed anymore.

    alt text

    Update

    One important thing: I had to create an empty ‘default.aspx’ file in the root of the application in order to allow the default document for requests like ‘http://www.example.com/‘ (without calling an aspx).

    Update 2

    Another very important thing: if you’re using ASP.NET Ajax PageMethods, then you have to keep the aspx placeholder of that page. If you’re omitting the file, a javascript ‘PageMethods is undefined’ error will be thrown on the browser.

    • 0