departed developer, so was looking for a way round what he had done.
because of that.
"Steve C. Orr [MCSD, MVP, CSM, ASP Insider]" <Steve@Orr.net> wrote in
> Controls shouldn't be tightly coupled with the page on which they are
> hosted.
> Calling the SystemLogin function may work well for now, but what happens
> when you put the control onto another page that doesn't have that
> function? It will blow up, that's what! If your response is that you
> don't ever plan to put the control onto another page then I'd have to
> question the wisdom of creating this functionality as a control in the
> first place.
>
> Generally it is better for controls to raise events to the page on which
> they are hosted, then the page can respond appropriately.
> Here's more info:
>
http://SteveOrr.net/faq/PassDataFromUserControl.aspx >
> --
> I hope this helps,
> Steve C. Orr,
> MCSD, MVP, CSM, ASPInsider
>
http://SteveOrr.net >
>
> "Tony Doyle" <nospam@spamoff.com> wrote in message
> news:u1BJgwiEHHA.1220@TK2MSFTNGP04.phx.gbl...
>> All,
>>
>> Using .NET 1.1, I have built a custom control, however I am having
>> trouble compiling it.
>> For the on click event of the button, I want it to run a function that is
>> already on my aspx page.
>> As the .NET compiler cannot see this page / function at compile time,
>> does anyone know of a way I can call the underlying function.
>>
>> private void ibLogIn_Click( object item, ImageClickEventArgs args )
>>
>> {
>>
>> HttpContext.Current.Session["LoggedInAs"] = tbUsername.Text;
>>
>> SystemLogin(tbUsername.ToString(), tbPassword.ToString());
>>
>> }
>>
>> In this case, it's the systemlogin procedure I'm trying to call.
>>
>> Cheers
>>
>> Tony
>>
>