|
Abhijit Jana wrote: if(Session["UserID"] != null)
{
//Do Operation
}
else
{
Response.Redirect("Login.aspx");
}
This is only valid if a session for that variable was created and you are checking for its value.
But if someone requests this page directly, it will throw an error stating
Object refrence not set.
Aspiring Techie,
Vishnu Nath
|
|
|
|
|
|
Buy a really basic book and read it. The code is CHECKING if the value is null.
Christian Graus
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
|
|
|
|
|
Thanx for your suggestion and advice,
will surely do the same.
I have implemented my own logic on it. 
Aspiring Techie,
Vishnu Nath
|
|
|
|
|
What logic u applied.Beacuse back button take page from cache.so it take old session value.
so to avoid this wat u did?
I also want to know
|
|
|
|
|
U r right.
And to stop a user accessing a page even after logout, i simply disabled the browsers back button after logout through javascript.
Aspiring Techie,
Vishnu Nath
|
|
|
|
|
U means u disable ur back button in ur whole project.
|
|
|
|
|
What was the Wrong with CG's Answer ?
|
|
|
|
|
No he wasn't wrong.
I had a bit concern, if a user tries to access the page directly, without following the normal routine, then the session variable which i would be checking on my page, would never have existed.
Hence i put out a check over there nd followed with the rest of the suggestions provided by all of u.
Aspiring Techie,
Vishnu Nath
|
|
|
|
|
cgs ans not wrong but if we hav secure page in our site. user can view secure information
|
|
|
|
|
Make all the session variables null before logout.
modified on Thursday, October 8, 2009 4:04 AM
|
|
|
|
|
Thanks for everyone's active participation in helping me.
Aspiring Techie,
Vishnu Nath
|
|
|
|
|
Hi friends,
I've a vb source code for a dll. now i want change something on the Dll.
Though i edit and registerthat component it's not wokring fine.How can fix the pblm.
Cheers,
Mahesh
|
|
|
|
|
You need source code for that to make changes.
ksss_maheshece wrote: Though i edit and registerthat component
Is that a COM dll? You don't need to register .NET DLL's.
|
|
|
|
|
i have the source code.
i'm using that component in my applicatiASP on.
here i register my component in component liberary.Before it's working fine .now i want to change the dll.
Shalln't need to register once again?
can i know why? and how?
Thanks,
Mahesh
|
|
|
|
|
You seem to be pretty damn clueless. If you change a COM object, make sure you register the changed version. Simple really.
Christian Graus
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
|
|
|
|
|
I've Edit the Dll source file and registered as well.But it doesn't reflect in the application.What would be the problem?
for Examble,
I have the connection string in my dll.I'd change the server and Database name.but it didn't reflect.Still remains in the same connection.
Thanks,
Mahesh
|
|
|
|
|
Have you unregistered the previous one before you register new one? COM is mess and you will run into DLL hell issues.
|
|
|
|
|
Add a message box or other marker to prove that your new code is what is being run.
Christian Graus
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
|
|
|
|
|
I tried my level best but it doesn't reflect that changes.
Thanks,
Mahesh
|
|
|
|
|
hi,
you need to open that source code ,after making changes set it binary compatible then create dll and then add this to your another project as reference.
Cheers,
Praveen.
|
|
|
|
|
how can set as a binary compatible.Plz help
cheers,
Mahesh
|
|
|
|
|
I have a growing number of functions that look like some variation of the below, and it seems like there's got to be a way to generalize the whole process. Any suggestions?
Basically what I want is to load datatables from stored procedures.
Public Function UsersGetIconList(ByVal UserID As String, ByVal SPName As String, ByVal ParamArray args() As String) As DataTable
Dim DS As New DataSet("ResultSet")
Dim dt As DataTable = DS.Tables.Add("ResultTable")
Dim CON As New SqlConnection(strConnString)
Dim CMD As New SqlCommand(SPName, CON)
Dim reader As SqlDataReader
CMD.CommandType = CommandType.StoredProcedure
Try
'Use Parameters defined in Stored Procedure to pass on Variables.
Dim Param As SqlParameter = CMD.Parameters.Add("@UserID", SqlDbType.VarChar, 36)
Param.Value = UserID
Param = CMD.Parameters.Add("@User_Icon_FileLocation", SqlDbType.NChar, 256)
CMD.Parameters("@User_Icon_FileLocation").Direction = ParameterDirection.Output
'Open Database and Execute Query as defined in Stored Procedure.
CON.Open()
reader = CMD.ExecuteReader()
dt.Load(reader)
Catch ex As Exception
'MsgBox(ex.Message)
Finally
CON.Close()
End Try
'Data is accessible through the DataReader object here.
Return dt
End Function
|
|
|
|
|
You need a generic method that gives you a DataTable after executing a stored-procedure? If yes, how about a function signature like
Public Function GetDataTable(ByVal SPName As String, ByVal ParamArray parameters() As SqlParameter) As DataTable
You need to create and pass SqlParameter instances. Inside this function, add all parameters to the command and fill a datatable. Using strongly typed data structures is the preferred method. If you want to use DataTable, use typed DataTable and enjoy the advantages of type safety.
I'd personally avoid DataTable or DataSet. If I have to use, I prefer typed ones. Usually data access methods should return typed POCO (plain old CLR object) or DTO (data transfer object) objects. You will have a common method that will do data access and return a SqlDataReader or IDataReader if you care about extending to other databases.
Your UsersGetIconList() method can utilize the common method and get a data reader. Using this reader, create your own DTO object and return.
|
|
|
|
|
Thanks N a v a n e e t h.
Of course now I'm thoroughly confused.
I'm a bit beyond my comfort zone here. I know how to deal with datatables, and it seems like Stored Procedures are something that I definately need to learn about. I just bought a SQL Server Dev book, so hopefully that'll help.
It seems to me like getting data into the Stored Procedure is easier than getting it back out, and I think I'm thinking about something dreadfully wrong about the process...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
