Tables Login

Hello,
I've developed an application in VB .NET 2005. To login I've used the login
view control of ASP .NET 2005. But now I've to install it, and I don't know
how could I create the tables to login?.
My apologize for my english.
Thanks for all,
SilviaLl.Which database are you using? I believe that there is an Access membership
provider somewhere, if so it's probably on the www.asp.net website.
You can install the membership to a web server using a utility found in the
Windows\Microsoft.Net\Framework\v2.0.50727 directory. The utility is called
aspnet_regsql.exe. It should launch a wizard that will walk you through
creating all the necessary items for using membership as well as role
management and personalization.
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199...2006
"Silviall" <slladoARROBAgmailPUNTOcoEME> wrote in message
news:O$S9PWq$GHA.3836@.TK2MSFTNGP02.phx.gbl...
> Hello,
> I've developed an application in VB .NET 2005. To login I've used the
> login view control of ASP .NET 2005. But now I've to install it, and I
> don't know how could I create the tables to login?.
> My apologize for my english.
> Thanks for all,
> SilviaLl.
>
Hello Mark,
I'm using SQL Server.
Thanks for all,
SilviaLl.
"Mark Fitzpatrick" <markfitz@.fitzme.com> escribi en el mensaje
news:uH7aGvq$GHA.4024@.TK2MSFTNGP04.phx.gbl...
> Which database are you using? I believe that there is an Access membership
> provider somewhere, if so it's probably on the www.asp.net website.
> You can install the membership to a web server using a utility found in
> the Windows\Microsoft.Net\Framework\v2.0.50727 directory. The utility is
> called aspnet_regsql.exe. It should launch a wizard that will walk you
> through creating all the necessary items for using membership as well as
> role management and personalization.
>
> --
> Hope this helps,
> Mark Fitzpatrick
> Former Microsoft FrontPage MVP 199...2006
> "Silviall" <slladoARROBAgmailPUNTOcoEME> wrote in message
> news:O$S9PWq$GHA.3836@.TK2MSFTNGP02.phx.gbl...
>

Tables Login

Hello,

I've developed an application in VB .NET 2005. To login I've used the login
view control of ASP .NET 2005. But now I've to install it, and I don't know
how could I create the tables to login?.

My apologize for my english.

Thanks for all,

SilviaLl.Which database are you using? I believe that there is an Access membership
provider somewhere, if so it's probably on the www.asp.net website.

You can install the membership to a web server using a utility found in the
Windows\Microsoft.Net\Framework\v2.0.50727 directory. The utility is called
aspnet_regsql.exe. It should launch a wizard that will walk you through
creating all the necessary items for using membership as well as role
management and personalization.

--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006

"Silviall" <slladoARROBAgmailPUNTOcoEMEwrote in message
news:O$S9PWq$GHA.3836@.TK2MSFTNGP02.phx.gbl...

Quote:

Originally Posted by

Hello,
>
I've developed an application in VB .NET 2005. To login I've used the
login view control of ASP .NET 2005. But now I've to install it, and I
don't know how could I create the tables to login?.
>
My apologize for my english.
>
Thanks for all,
>
SilviaLl.
>

Hello Mark,

I'm using SQL Server.

Thanks for all,

SilviaLl.
"Mark Fitzpatrick" <markfitz@.fitzme.comescribi en el mensaje
news:uH7aGvq$GHA.4024@.TK2MSFTNGP04.phx.gbl...

Quote:

Originally Posted by

Which database are you using? I believe that there is an Access membership
provider somewhere, if so it's probably on the www.asp.net website.
>
You can install the membership to a web server using a utility found in
the Windows\Microsoft.Net\Framework\v2.0.50727 directory. The utility is
called aspnet_regsql.exe. It should launch a wizard that will walk you
through creating all the necessary items for using membership as well as
role management and personalization.
>
>
--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006
>
"Silviall" <slladoARROBAgmailPUNTOcoEMEwrote in message
news:O$S9PWq$GHA.3836@.TK2MSFTNGP02.phx.gbl...

Quote:

Originally Posted by

>Hello,
>>
>I've developed an application in VB .NET 2005. To login I've used the
>login view control of ASP .NET 2005. But now I've to install it, and I
>don't know how could I create the tables to login?.
>>
>My apologize for my english.
>>
>Thanks for all,
>>
>SilviaLl.
>>

>
>

Tags vs. code-behind

Hi guys..

I just wanted to know whether its better to use the asp tags (or drag
n drop) or write the actual code-behind for things like login, data
accesses etc. I guess its easier to use the tags but does it have any
disadvantages ?

Thanks !On Feb 27, 10:36 am, "Zeba" <coolz...@.gmail.comwrote:

Quote:

Originally Posted by

Hi guys..
>
I just wanted to know whether its better to use the asp tags (or drag
n drop) or write the actual code-behind for things like login, data
accesses etc. I guess its easier to use the tags but does it have any
disadvantages ?
>

Using code-behind you separate Business Logic and UI design

Using code-inline the script can be changed without re-deploying the
whole application.

http://www.eggheadcafe.com/articles/20030518.asp
Using code-inline the script can be changed without re-deploying the

Quote:

Originally Posted by

whole application.

Something that should be totally avoided in "true MVC" applications.
It's a bad practice.

Looking into the article, which reads "There are certain situations where a
purely inline - code implementation is justified"... I tend to disagree.

Also, the author does not give any concrete examply to substantiate the
statement.

In my view, inline code can be and must be totally avoided. The reason is
obvious - seggregation of the UI from the logic... the heart of MVC
pattern.

--
Happy Hacking,
Gaurav Vaish | www.mastergaurav.com
www.edujini-labs.com
http://eduzine.edujini-labs.com
-------------
"MasterGaurav (www.edujini-labs.com)" <gaurav.vaish.nospam@.nospam.gmail.com>
wrote in message news:esUtIHnWHHA.1180@.TK2MSFTNGP05.phx.gbl...

Quote:

Originally Posted by

Quote:

Originally Posted by

>Using code-inline the script can be changed without re-deploying the
>whole application.

>
Something that should be totally avoided in "true MVC" applications.
It's a bad practice.

I agree.

Quote:

Originally Posted by

In my view, inline code can be and must be totally avoided. The reason is
obvious - seggregation of the UI from the logic... the heart of MVC
pattern.

I would agree, apart from in one specific instance related to ASP.NET -
Global.asax, where there are sometimes justifications for in-line code...
Juan is a particular advocate of this, IIRC...
On Feb 27, 2:16 pm, "MasterGaurav \(www.edujini-labs.com\)"
<gaurav.vaish.nos...@.nospam.gmail.comwrote:

Quote:

Originally Posted by

It's a bad practice.

It depends on the need.
No disadvantage. MS is moving towards "code free" development.

You can expect to see a lot more of this in the future, so you may want to get into it now.

"Zeba" <coolzebs@.gmail.comwrote in message news:1172568997.043126.138660@.a75g2000cwd.googlegr oups.com...

Quote:

Originally Posted by

Hi guys..
>
I just wanted to know whether its better to use the asp tags (or drag
n drop) or write the actual code-behind for things like login, data
accesses etc. I guess its easier to use the tags but does it have any
disadvantages ?
>
Thanks !
>

The base argument is really:

Rapid Code Development VS Good Code Development.

Unless I'm whipping up a demo that needs to be done by yesterday,
I would avoid tags 99.9% of the time.

Rapid <Good most of the time.

Good development means it is maintainable (among other things), and the
<tagsapproach is cumbersome in that regard.

"Zeba" <coolzebs@.gmail.comwrote in message
news:1172568997.043126.138660@.a75g2000cwd.googlegr oups.com...

Quote:

Originally Posted by

Hi guys..
>
I just wanted to know whether its better to use the asp tags (or drag
n drop) or write the actual code-behind for things like login, data
accesses etc. I guess its easier to use the tags but does it have any
disadvantages ?
>
Thanks !
>

On Feb 27, 5:36 am, "Zeba" <coolz...@.gmail.comwrote:

Quote:

Originally Posted by

Hi guys..
>
I just wanted to know whether its better to use the asp tags (or drag
n drop) or write the actual code-behind for things like login, data
accesses etc. I guess its easier to use the tags but does it have any
disadvantages ?
>
Thanks !

I agree with the other posters wholeheartedly. The UI should most
definitely be separated from the business logic. In my personal
experience, even for fast demos, there's no *compelling* reason to
embed the source code right in the Web page. That assumes, of course,
that you're using Visual Studio or a similar editor that's capable of
handling code-behind files. The plumbing is all handled for you, and
the development experience is virtually seamless.

However, that's my *personal* experience, and your mileage may vary.

Another consideration is whether or not you want people to see your
intellectual property. If the source code is embedded right in the
pages, it's a lot harder to protect your source code from casual
viewing. With code-behind, you can compile the business logic into one
or more DLLs and avoid deploying the .VB & .resx files altogether;
that, coupled with a decent obfuscator, helps to protect your
intellectual property.

Mike
On Feb 27, 5:36 am, "Zeba" <coolz...@.gmail.comwrote:

Quote:

Originally Posted by

Hi guys..
>
I just wanted to know whether its better to use the asp tags (or drag
n drop) or write the actual code-behind for things like login, data
accesses etc. I guess its easier to use the tags but does it have any
disadvantages ?
>
Thanks !

I would *especially* use a code-behind for data access. You'd be
divulging details about how you connect to your data source. Big no
no.

Same goes for user authentication and authorization.

Call me paranoid. These days, a determined hacker WILL penetrate your
system if he chooses to do so, and if your code is sitting there with
the instructions for connecting to your database right in the Web
pages, you WILL live to regret it.

Be safe. Move the code into a codebehind file. Obfuscate the code
during the build. Then, prior to deployment, remove any and all source
code files (except the global.asax file). Be sure not to include any
sensitive instructions in the global.asax file. Security is
everything.

Mike

Tags vs. code-behind

Hi guys..
I just wanted to know whether its better to use the asp tags (or drag
n drop) or write the actual code-behind for things like login, data
accesses etc. I guess its easier to use the tags but does it have any
divantages ?
Thanks !On Feb 27, 10:36 am, "Zeba" <z...@.gmail.com> wrote:
> Hi guys..
> I just wanted to know whether its better to use the asp tags (or drag
> n drop) or write the actual code-behind for things like login, data
> accesses etc. I guess its easier to use the tags but does it have any
> divantages ?
>
Using code-behind you separate Business Logic and UI design
Using code-inline the script can be changed without re-deploying the
whole application.
http://www.eggheadcafe.com/articles/20030518.asp
> Using code-inline the script can be changed without re-deploying the
> whole application.
Something that should be totally avoided in "true MVC" applications.
It's a bad practice.
Looking into the article, which reads "There are certain situations where a
purely inline - code implementation is justified"... I tend to disagree.
Also, the author does not give any concrete examply to substantiate the
statement.
In my view, inline code can be and must be totally avoided. The reason is
obvious - seggregation of the UI from the logic... the heart of MVC
pattern.
Happy Hacking,
Gaurav Vaish | www.mastergaurav.com
www.edujini-labs.com
http://eduzine.edujini-labs.com
---
"MasterGaurav (www.edujini-labs.com)" <gaurav.vaish.nospam@.nospam.gmail.com>
wrote in message news:esUtIHnWHHA.1180@.TK2MSFTNGP05.phx.gbl...

> Something that should be totally avoided in "true MVC" applications.
> It's a bad practice.
I agree.

> In my view, inline code can be and must be totally avoided. The reason is
> obvious - seggregation of the UI from the logic... the heart of MVC
> pattern.
I would agree, apart from in one specific instance related to ASP.NET -
Global.asax, where there are sometimes justifications for in-line code...
Juan is a particular advocate of this, IIRC...
On Feb 27, 2:16 pm, "MasterGaurav \(www.edujini-labs.com\)"
<gaurav.vaish.nos...@.nospam.gmail.com> wrote:

> It's a bad practice.
It depends on the need.
No divantage. MS is moving towards "code free" development.
You can expect to see a lot more of this in the future, so you may want to g
et into it now.
"Zeba" <zebs@.gmail.com> wrote in message news:1172568997.043126.138660@.a75g2000cwd.goog
legroups.com...
> Hi guys..
> I just wanted to know whether its better to use the asp tags (or drag
> n drop) or write the actual code-behind for things like login, data
> accesses etc. I guess its easier to use the tags but does it have any
> divantages ?
> Thanks !
>
The base argument is really:
Rapid Code Development VS Good Code Development.
Unless I'm whipping up a demo that needs to be done by yesterday,
I would avoid tags 99.9% of the time.
Rapid <> Good most of the time.
Good development means it is maintainable (among other things), and the
<tags> approach is cumbersome in that regard.
"Zeba" <zebs@.gmail.com> wrote in message
news:1172568997.043126.138660@.a75g2000cwd.googlegroups.com...
> Hi guys..
> I just wanted to know whether its better to use the asp tags (or drag
> n drop) or write the actual code-behind for things like login, data
> accesses etc. I guess its easier to use the tags but does it have any
> divantages ?
> Thanks !
>
On Feb 27, 5:36 am, "Zeba" <z...@.gmail.com> wrote:
> Hi guys..
> I just wanted to know whether its better to use the asp tags (or drag
> n drop) or write the actual code-behind for things like login, data
> accesses etc. I guess its easier to use the tags but does it have any
> divantages ?
> Thanks !
I agree with the other posters wholeheartedly. The UI should most
definitely be separated from the business logic. In my personal
experience, even for fast demos, there's no *compelling* reason to
embed the source code right in the Web page. That assumes, of course,
that you're using Visual Studio or a similar editor that's capable of
handling code-behind files. The plumbing is all handled for you, and
the development experience is virtually seamless.
However, that's my *personal* experience, and your mileage may vary.
Another consideration is whether or not you want people to see your
intellectual property. If the source code is embedded right in the
pages, it's a lot harder to protect your source code from casual
viewing. With code-behind, you can compile the business logic into one
or more DLLs and avoid deploying the .VB & .resx files altogether;
that, coupled with a decent obfuscator, helps to protect your
intellectual property.
Mike
On Feb 27, 5:36 am, "Zeba" <z...@.gmail.com> wrote:
> Hi guys..
> I just wanted to know whether its better to use the asp tags (or drag
> n drop) or write the actual code-behind for things like login, data
> accesses etc. I guess its easier to use the tags but does it have any
> divantages ?
> Thanks !
I would *especially* use a code-behind for data access. You'd be
divulging details about how you connect to your data source. Big no
no.
Same goes for user authentication and authorization.
Call me paranoid. These days, a determined hacker WILL penetrate your
system if he chooses to do so, and if your code is sitting there with
the instructions for connecting to your database right in the Web
pages, you WILL live to regret it.
Be safe. Move the code into a codebehind file. Obfuscate the code
during the build. Then, prior to deployment, remove any and all source
code files (except the global.asax file). Be sure not to include any
sensitive instructions in the global.asax file. Security is
everything.
Mike

Target Window question

Im trying to target="top" when the user click on the login button - But its not working for me, any ideas where i put Target="top" sorry im new to .aspx

cheers

ZOIK

Example of code.

<asp:Login ID="Login1" runat="server" BackColor="#F7F6F3" BorderColor="#E6E2D8" BorderPadding="4"
BorderStyle="Solid" BorderWidth="1px" Font-Names="Verdana" Font-Size="Small"
ForeColor="#333333" Height="147px" Width="293px" DestinationPageUrl="~/secure_industry/Default.aspx">
<TitleTextStyle BackColor="#5D7B9D" Font-Bold="True" Font-Size="0.9em" ForeColor="White" />
<InstructionTextStyle Font-Italic="True" Font-Size="Small" ForeColor="Black" />
<TextBoxStyle Font-Size="X-Small" />
<LoginButtonStyle BackColor="#FFFBFF" BorderColor="#CCCCCC" BorderStyle="Solid" BorderWidth="1px"
Font-Names="Verdana" Font-Size="Small" ForeColor="#284775"/>
<LabelStyle Font-Size="Small" />
<CheckBoxStyle Font-Size="Small" />
<HyperLinkStyle Font-Size="Small" />
</asp:Login>

Hi,

I think it is not possible to do that with the inbuilt login control. What you can do is create a login template with the code from the below link and then set the onclick event of the button control to target="_top"

http://quickstarts.asp.net/QuickStartv20/util/srcview.aspx?path=~/aspnet/samples/ctrlref/login/LoginTemplate.src

Let me know if you have any issues.

Thanks mate thats excellent.