If CodeFile="MyFile.cs" is what you mean, yeah.
<%@ Page Language="C#" MasterPageFile="~/MasterPages/Main.master" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" Title="Untitled Page" %> That's one that uses a MasterPage as well (from a site I'm building right now). Mind you, VS takes care of this. Yet in still, you can't control the page in the component or tag in CF like you can in ASP.NET. I don't wanna start a flame war of ASP.NET and CF. Bottom line, code-behind is not the same as invoking a tag or component in CF. On 11/29/06, Aaron Roberson <[EMAIL PROTECTED]> wrote: > > > - 100% complete separation of code and visuals (no instantiation of > objects, > > etc at the top of the page...they are already there) > > In .NET you have to supply a page directive for the .cs file, which is > similar to instantiating an object at the top of a CF page if all of > the control is encapsulated in the object. > > -Aaron > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:262170 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
