Thursday, March 29, 2012
html frames and forms authentication
a frame wrapper on their corporate site, so my website will run in a frame
like this.
<frameset rows="134,*" cols="*" framespacing="0" frameborder="NO"
border="0">
<frame src="http://pics.10026.com/?src=http://www.aWebsiteMarketing.com/top.html" name="topFrame"
frameborder="yes" scrolling="NO">
<frame src="http://pics.10026.com/?src=http://www.aWebsiteMarketing.com/bottom.html"
name="mainFrame">
</frameset>
In the bottom.html there is a link to my www.aWebsite.com.
So the URL in the title bar will read http://www.aWebsiteMarketing.com, but
in the bottom frame my website
www.aWebsite.com will be showing.
my www.aWebsite.com requires a login via formsauthentication. the method:
FormsAuthentication.SetAuthCookie(customerID, RememberLogin.checked)
is not working. I don't have this problem on my WinXpsp1, but on any other
Win2k in my office.
this is probably one of the most frustrating things I have ever had to deal
with...
help, ~psb
html frames and forms authentication
a frame wrapper on their corporate site, so my website will run in a frame
like this.
<frameset rows="134,*" cols="*" framespacing="0" frameborder="NO"
border="0">
<frame src="http://pics.10026.com/?src=http://www.aWebsiteMarketing.com/top.html" name="topFrame"
frameborder="yes" scrolling="NO">
<frame src="http://pics.10026.com/?src=http://www.aWebsiteMarketing.com/bottom.html"
name="mainFrame">
</frameset
In the bottom.html there is a link to my www.aWebsite.com.
So the URL in the title bar will read http://www.aWebsiteMarketing.com, but
in the bottom frame my website
www.aWebsite.com will be showing.
my www.aWebsite.com requires a login via formsauthentication. the method:
FormsAuthentication.SetAuthCookie(customerID, RememberLogin.checked)
is not working. I don't have this problem on my WinXpsp1, but on any other
Win2k in my office.
this is probably one of the most frustrating things I have ever had to deal
with...
help, ~psb
Thursday, March 22, 2012
HTML controls in ASP.NET
http://www.visual-basic-data-mining.net/forum <simiking@.gmail.com> wrote:
> Could you tell me how to hide an HTML list box using client side script.
I believe the JS is:
var oCtrl = document.getElementById('myControlClientID');
Are you asking how to emit this script from an ASP.NET form? See
Page.RegisterClientScriptBlock and/or Page.RegisterStartupScript.
Craig Deelsnyder
Microsoft MVP - ASP/ASP.NET
<html_list_box_id>.style.display = 'none';
"http://www.visual-basic-data-mining.net/forum" <simiking@.gmail.com> wrote i
n message news:#5XbyWtlEHA.2380@.TK2MSFTNGP14.phx.gbl...
Could you tell me how to hide an HTML list box using client side script.
Craig Deelsnyder:
Thanks a lot for answering my question. I appreciate it.
--
forum member
http://www.visual-basic-data-mining.net/forum
"Craig Deelsnyder" <cdeelsny@.no_spam_4_meyahoo.com> wrote in message
news:opsd3adelo75dg5d@.g51y101...
> On Fri, 10 Sep 2004 08:38:42 -0700,
> http://www.visual-basic-data-mining.net/forum <simiking@.gmail.com> wrote:
>
> I believe the JS is:
> var oCtrl = document.getElementById('myControlClientID');
> Are you asking how to emit this script from an ASP.NET form? See
> Page.RegisterClientScriptBlock and/or Page.RegisterStartupScript.
> --
> Craig Deelsnyder
> Microsoft MVP - ASP/ASP.NET
Shiva:
Thanks a lot for your time. I appreciate it
--
forum member
http://www.visual-basic-data-mining.net/forum
"Shiva" <shiva_sm@.online.excite.com> wrote in message news:%23panoBvlEHA.596
@.TK2MSFTNGP11.phx.gbl...
<html_list_box_id>.style.display = 'none';
"http://www.visual-basic-data-mining.net/forum" <simiking@.gmail.com> wrote i
n message news:#5XbyWtlEHA.2380@.TK2MSFTNGP14.phx.gbl...
Could you tell me how to hide an HTML list box using client side script.
HTML controls in ASP.NET
http://www.visual-basic-data-mining.net/forum <simiking@.gmail.com> wrote:
> Could you tell me how to hide an HTML list box using client side script.
I believe the JS is:
var oCtrl = document.getElementById('myControlClientID');
Are you asking how to emit this script from an ASP.NET form? See
Page.RegisterClientScriptBlock and/or Page.RegisterStartupScript.
--
Craig Deelsnyder
Microsoft MVP - ASP/ASP.NET
<html_list_box_id>.style.display = 'none';
"http://www.visual-basic-data-mining.net/forum" <simiking@.gmail.com> wrote in message news:#5XbyWtlEHA.2380@.TK2MSFTNGP14.phx.gbl...
Could you tell me how to hide an HTML list box using client side script.
Craig Deelsnyder:
Thanks a lot for answering my question. I appreciate it.
--
forum member
http://www.visual-basic-data-mining.net/forum
"Craig Deelsnyder" <cdeelsny@.no_spam_4_meyahoo.com> wrote in message
news:opsd3adelo75dg5d@.g51y101...
> On Fri, 10 Sep 2004 08:38:42 -0700,
> http://www.visual-basic-data-mining.net/forum <simiking@.gmail.com> wrote:
> > Could you tell me how to hide an HTML list box using client side script.
> I believe the JS is:
> var oCtrl = document.getElementById('myControlClientID');
> Are you asking how to emit this script from an ASP.NET form? See
> Page.RegisterClientScriptBlock and/or Page.RegisterStartupScript.
> --
> Craig Deelsnyder
> Microsoft MVP - ASP/ASP.NET
Shiva:
Thanks a lot for your time. I appreciate it
--
forum member
http://www.visual-basic-data-mining.net/forum
"Shiva" <shiva_sm@.online.excite.com> wrote in message news:%23panoBvlEHA.596@.TK2MSFTNGP11.phx.gbl...
<html_list_box_id>.style.display = 'none';
"http://www.visual-basic-data-mining.net/forum" <simiking@.gmail.com> wrote in message news:#5XbyWtlEHA.2380@.TK2MSFTNGP14.phx.gbl...
Could you tell me how to hide an HTML list box using client side script.
Wednesday, March 21, 2012
HTML Client Control versus. HTML Server Control versus. Web Server Control
and advantages of each one in ASP.NET web application. Here's what I know so
far..
1. HTML Client Control: understood by the client only. e.g. <input
type="text" name="emp_name">
2. HTML Server Control: understood by the server only. e.g. <input
type="text" name="emp_name"
runat="server">
3. Web Server Control: understood by the server only. e.g. <asp:TextBox
id="emp_name"
runat="server"></asp:TextBox
I tried to use all, but yield the same output. I am sure there are
advantages of each one, please advise!
Thanks!The HTML controls (client controls) are the same HTML 4.01 controls that
have been part of the HTML language for a very long time. Use these when
their native client-side functionality serves your purpose (lowest overhead
with these controls).
The HTML Server controls are the same as above but with added server-side
programming/viewstate capabilities. Use these when migrating a "Classic
ASP" application to ASP.NET and you won't have to completely replace all
your old controls with new ones to get the .NET benefits of them. While you
do get some server-side programming capabilities with these, you don't get
the full range of properties, methods & events that pure server-side
controls offer.
The Web Form controls (a.k.a. Web Server controls) provide .NET native
server-side programming support. The properties, methods and events of
these controls are more VB like than the HTML controls. These controls
offer the widest range of flexibility from a programming standpoint, but can
(if not used correctly) create more overhead (viewstate) for your .aspx
pages.
The Web Form controls also feature controls that don't have an HTML
equivalent (validation controls, data controls, other rich controls
[calendar]). No matter which Web Form control you use, they render
themselves to the client as pure HTML/JavaScript, so they can be used in any
client!
-Scott
"Matthew Louden" <jrefactors@.hotmail.com> wrote in message
news:ezrMcGCkDHA.2616@.TK2MSFTNGP11.phx.gbl...
> Personally, I am totally confused with the following control terms and
usage
> and advantages of each one in ASP.NET web application. Here's what I know
so
> far..
> 1. HTML Client Control: understood by the client only. e.g. <input
> type="text" name="emp_name">
> 2. HTML Server Control: understood by the server only. e.g. <input
> type="text" name="emp_name"
> runat="server">
> 3. Web Server Control: understood by the server only. e.g. <asp:TextBox
> id="emp_name"
> runat="server"></asp:TextBox>
> I tried to use all, but yield the same output. I am sure there are
> advantages of each one, please advise!
> Thanks!
>
>
HTML Button running at=server
I have a HTML button that can be accessed server-side too - the only problem
is when the button is disabled in the client (via onclick="this.disabled=tru
e")
it doesn't reflect this when a post-back occurs.
Any ideas?
Thanks
KevAny ideas about what? Client side changes simply are not sent back the
server. If you want it disabled on the server, you have to disable it on
the server, or do some hack like set some hidden fields that indicate your
state.
"Kevin Lawrence" <spamthis@.spam.com> wrote in message
news:3a030fc3eb1a8c7f63317398a0a@.news.rmplc.co.uk...
> Hi
> I have a HTML button that can be accessed server-side too - the only
> problem is when the button is disabled in the client (via
> onclick="this.disabled=true") it doesn't reflect this when a post-back
> occurs.
> Any ideas?
> Thanks
> Kev
>
> Any ideas about what?
Any ideas about how I can work around it...
Client side changes simply are not sent back
> the server. If you want it disabled on the server, you have to
> disable it on the server, or do some hack like set some hidden fields
> that indicate your state.
Well is there a way I can use a server control and NOT have it post back?
I hate having to work around evey god-damn flaw in web dev.
Kev
HTML Button running at=server
I have a HTML button that can be accessed server-side too - the only problem
is when the button is disabled in the client (via onclick="this.disabled=true")
it doesn't reflect this when a post-back occurs.
Any ideas?
Thanks
KevAny ideas about what? Client side changes simply are not sent back the
server. If you want it disabled on the server, you have to disable it on
the server, or do some hack like set some hidden fields that indicate your
state.
"Kevin Lawrence" <spamthis@.spam.com> wrote in message
news:3a030fc3eb1a8c7f63317398a0a@.news.rmplc.co.uk. ..
> Hi
> I have a HTML button that can be accessed server-side too - the only
> problem is when the button is disabled in the client (via
> onclick="this.disabled=true") it doesn't reflect this when a post-back
> occurs.
> Any ideas?
> Thanks
> Kev
> Any ideas about what?
Any ideas about how I can work around it...
Client side changes simply are not sent back
> the server. If you want it disabled on the server, you have to
> disable it on the server, or do some hack like set some hidden fields
> that indicate your state.
Well is there a way I can use a server control and NOT have it post back?
I hate having to work around evey god-damn flaw in web dev.
Kev