Web Connection looks at the markup file on disk to figure out what the name of the class and/or FXP file is that it needs to run so the markup files are required. However, only for the <%@Page %> header is required when you're running precompiled. Everything else is not used.

Not sure if that's worth the hassle of removing though...

+++ Rick ---

Hi Jim,

Thanks for your reply.

Yes, this is how it works, it is just I do not want to include the pages on the production server once the Exe has compiled the pages. If the files are strictly required, can I remove the markup from the files to reduce the footprint on the production server?

Bascially I want to distribute the app as "Run Only" in the server and avoid the external file dependency or at least remove as much of the markup as possible within the files themselves? I do not see the point of distributing all of the markup in files where the markup is not used at all.

Thanks

Richard

If the server is running as a complied EXE, the pages at the time of the complile will be executed.

The files must be on the server but they are not executed and do not need to be updated.

You must set your status as "Precompiled FXP Files" and "Run Only" if you are running in File Mode.

Jim

Hi all,

I'm trying to work out the dependency of the web control pages when the server is set in compiled mode. The server always refers to the compiled version of the page and ignores any changed markup in the external pages.

If I remove the pages from the virtual the application fails? Is there a way to avoid the need to include these pages when the server references them internally? If not, can the markup be removed from the file and the ASP.NET header code left in?

I want to avoid publishing the markup when the pages are read from the compiled versions. I see no need for the markup to exist externally in production. Any tips on this?

Thanks

Richard

Rick Strahl West Wind Technologies Where do you want to surf today?

Reader Version: 5.0

from Maui, Hawaii

---