how to create user control that cannot seen by other member

Question

0.00/5 (No votes)

See more:

hi everyone.. can somebody give me some reference on how to create user control that cannot seen by other member in a webpage? I already google it but there are links that not exact on what i want to do..

thanks in advance

Posted 11-Jun-13 0:23am

Member 10033107

Add a Solution

Comments

bbirajdar 11-Jun-13 6:28am

if(username!="myuser")
{
ucUserControl1.Visible=false;
}

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-06-11T01:17:00

Solution 1

You did not find anything, because people don't have to create a control to be visible or not; such feature (control visibility) already exists. However, it's simpler than that: your ASP.NET generates the whole Web page, so you can write some elements conditionally, depending on the permissions of current user.

—SA

Posted 11-Jun-13 1:17am

Sergey Alexandrovich Kryukov

Comments

Shahin Khorshidnia 11-Jun-13 7:46am

+5

Sergey Alexandrovich Kryukov 11-Jun-13 7:53am

Thank you, Shahin.
—SA

Member 10033107 12-Jun-13 20:42pm

yes i know that.. okay this is what i meant to say.. I created a user roles in my page wherein the registered roles has different page that can only be access in different user... this is my code:
Protected Sub Page_Load(ByVal sender As Object, ByVal e As EventArgs) Handles Me.Load
Dim user
user = Request.QueryString("muser")

If user = "" Then
Response.Redirect("loginuser.aspx")
Else
labUser.Text = ""
End If

'Dim n As Integer = [String].Compare(Request.QueryString("username"), "")
'If n <= 0 Then
' Server.Transfer("defmain.aspx")
'Else
' labWelcome.Text = "Welcome, " & Request.QueryString("username") & "!"
'End If

Select Case Request.QueryString("userroles")
Case "1"
mnMain.Items(0).NavigateUrl = "~/CyberyaLogo.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username")

mnMain.Items(1).ChildItems(1).NavigateUrl = "~/Sales.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username")
mnMain.Items(1).ChildItems(2).NavigateUrl = "~/RFC.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username") & "&mode=0"
mnMain.Items(1).ChildItems(3).NavigateUrl = "~/Marketing.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username") & "&mode=0"
mnMain.Items(1).ChildItems(4).NavigateUrl = "~/PCExpress.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username") & "&mode=0"
mnMain.Items(1).ChildItems(5).NavigateUrl = "~/Client.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username") & "&mode=0"
ifMain.Attributes("src") = "CyberyaLogo.aspx?userrole=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username")
Exit Select
Case "2"
mnMain.Items(0).NavigateUrl = "~/CyberyaLogo.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username")

mnMain.Items(1).ChildItems(1).NavigateUrl = "~/Sales.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username")
mnMain.Items(1).ChildItems(2).NavigateUrl = "~/RFC.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username") & "&mode=0"
mnMain.Items(1).ChildItems(3).NavigateUrl = "~/Marketing.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username") & "&mode=0"
mnMain.Items(1).ChildItems(4).NavigateUrl = "~/PCExpress.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username") & "&mode=0"
mnMain.Items(1).ChildItems(5).NavigateUrl = "~/Client.aspx?userroles=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username") & "&mode=0"
ifMain.Attributes("src") = "CyberyaLogo.aspx?userrole=" & Request.QueryString("userroles") & "&username=" & Request.QueryString("username")
If Not IsPostBack Then
'mnMain.Items[1].ChildItems.RemoveAt(3);
mnMain.Items.RemoveAt(2)

End If
Exit Select
Case Else
Exit Select
End Select
End Sub

Member 10033107 12-Jun-13 20:45pm

wherein im looking forward to create a login user that he/she only access a limited pages yet i have trouble in here that still he/she saw all pages that not to be access on that page.. i hope you understand what im meant to say thanks

Sergey Alexandrovich Kryukov 12-Jun-13 20:47pm

I think I understand that, I still don't see what's the problem to implement that.
—SA

Member 10033107 12-Jun-13 20:59pm

>.< geez!! yes sir .. i dont have any errors on this code yet.. for example im the user number 3 (wherein i cant post because its too long) as ive been login in that homepage, i expect ONLY to access client.aspx and rfc.aspx that still i been seen the other page i cannot or im not to expect to be access too.. what im gonna suppose to do with that sir >.<

Sergey Alexandrovich Kryukov 12-Jun-13 21:14pm

I did not mean "errors". I don't know what do you mean by "error". Exception? It does not have to be exception, it could be just the "correct" behavior but not that you expect. First of all, how are you going to filter access in principle? It should be some subset of users. What is it? You either have some rule set based on individual users, such as accessibility features attributed to each individual user, or, better, have users classified into "roles", which is a pretty much standard scheme. Where is anything like that. I see a set of redirections, under cases, but cases "1", "2", etc. make no sense, they should be something semantic. If you see some case by who-knows-what discriminant, especially a long one, be sure that it's wrong. So, why redirections? You can generate controls, or at least control controls' visibility property depending on your solutions based on the user (role). If does not look like you are trying it in your code. So, my question is: what's so unclear here? You said "yes, I know that"...
—SA