Here is example of what I need:
default.aspx.vb on load:
Dim strA as String = "good title"
default.aspx
<a class='colorboxLogin_aspx' href="zamjenaslike.aspx" title="*****here should be value of strA******">
in old fashion .asp i jused <% =strA%> and it was great, what is alternative here?
I have done a web appllication and when run simultaneously from different locations, the one that is started first would use the one that is started late's session variable and datatable contents. This is an exams web app and pageone.aspx results should never be used for pagetwo.aspx's results, because they are not the same questions.
What can I do to prevent this from happening. I am desperate, people are standing by to do exams and time is not on my side.
I know there are at least 2 ways to send Variables to another ASPX page.
The first way is the use <form> and <input type="hidden">
The second way is the put the variable(s) in the URL such as http://www.joesmith.com/Sample.aspx?var1=bob&var2=cunningham
Is there a 3rd way to send variables using VBScript inside the <script runat="server"> tag?
I've scoured through the Forums about how 2 windows can interact with each other. There had been a lot of solutions involving parent-child windows, or modal pop-up wiows. However, my problem involves 2 aspx windows that show data from the same datasource, but should be able to update the data from either window, and after saving in either window shows the updated data
View 2 Replieswhere the static variables are stored in asp.net aspx page.Is it in the view state? If so I guess you wouldn't want to stored big complex objects?
View 2 RepliesI want to pass the value to ASPX.CS file to ASPX file.
So how can i pass the value in the ASPX file.
how can i cache aspx page?
View 2 Repliesi want to pass values from html to aspx page.....Html PageTextBox 1 , TextBox 2 & onClick textBoxs values Pass to aspx Page...
View 4 RepliesIve created an object and placed it in the session, then in my .ashx handler I want to get that object from the session. The problem is that its always null !
heres how ive placed the object into the session from an aspx page
[Code]....
Here is my scenario.In default.aspx page user selects the country, state, city from drop down list, and store them in cache for further use. but when other user open the web site from other computer it shows the same country, state, and city selected by user 1. Is there any problem related to cache? I have stored data as following.
cache["ctryID"] = ctryID;
cache["stateID"]= stateID;
cache["cityID"]= cityID;
I want to show default country, state , city at page load of default.aspx
can you tell Will sessions kill when application error occurs which is in global.aspx ?
ex:
[code]....
What is the easy/safe way to get all HttpContext.Current data (like querystring, etc) in the previous page, after response.redirect or server.transfer to another page?
I am using .net 3.5
I am working on an asp.net website using C#. The site deals with orders and therefore order lines. I would like to store the order in memory whilst it is being populated (with order lines) and once it gets submitted write it to a database.
The above logic has been implemented, but sometimes when accessing session state or storing a variable in it information gets lost. Take note that the web server is running a dual-core processor. I am also using the in proc session state server.
I tried changing over to using the out proc session state server (asp.net state service), but it requires serialization. Since the order and orderlines are actually linq to sql classes, the entitysets and entityref's fail to serialize.
Does anyone know the reason why session state loses information occasionally and possibly how to eliminate the problem?
I'm doing nothing special with session...
I just put some value on button_click event handler and then redirect to another page
like this { Session["key"]="value"; Responde.Redirect("AnotherPage.aspx"); }
And then I try to read Session["key"] on Page_Load of AnotherPage.aspx but it's null!
What can cause this?
P.S. When I use Server.Transfer() instead of Response.Redirect() it works fine.
I've begun building a bit of a framework that I wouldnt mind working with. The idea is to create a framework that makes it even easier to create CMS addons (So basically a CMS framework).
One of my goals with this project, was having all modules made within the framework automatically support version without any extra coding.
More to the point, the way that I started building this, many pieces (Lots had to do with the versioning system) became interlinked. A version Object in the code related directly to a Module Object and vice versa, therefore the class definitions for each relate to eac otherh. (So having only the Module object, i could access the versioning object and all of its properties). My issue with this is of course what happens if i have both the module and versioning objects in my code simoultaneously, resulting in having not just duplicates of the data within the code, but (perhaps) infinite amounts, killing the app.
So what im wondering is, what if my modules properties where stored within the cache? Ie if i had the Module object, and it had the property ID -- Then the data for ID would be stored in the cache within the module object. Referencing the value simply retrieves the value from the cache if it exists there, and the SQL database if it doesnt. This way, all instances of the module that may be running at the same time will have access to the same information, at the same time, and hopefully causing it to use less space in total.
I would then add a function, so that if a developer was loading a rarely used module, or dident want to occupy cache space with large amounts of data, then they could just call a Dispose function that would remove the data from the cache.
Does this method sound reasonable? I know this probably isnt what the cache is designed for -- but I cant think of any other way to do this without having an infinite loop of objects referring to each other, or causing huge discrepencies from having different instances of objects referencing values that should be the same, but arent because they are technically different instances.
[Code]....
I have a slight delemma that I have not been able to work out.
My Scenario is:
Page_Loads > Calls Sub Random Data Retrieved from a Table - Displayed on screen & Sets Variables from Row(0) for an Insert Statement > Click Button to Insert those Variables.(essentially, the Insert Statement Parameters are Dynamic in that they change each time the page loads)
The Problem I am having, is that each time the page loads, I need a New DataSet, and the Page_Load is operating too quickly, changing my variables on postBack and ultimately, inserting the new values that are now loaded.
How can I:
Page_Loads > Get and Set the Variables I need > Protect Those Variables from changing on the Next Postback (so the insert statement gets the values Iwant to insert but also set and get the next ones)?
If Not Page.IsPostBack Doesnt Work for me in my Page_Load because each time the page.loads, I need those new Random Variables from a DataSet
Someone had Mentioned ViewState, but I am uncertain how to use it. I just want to protect the variables so that it inserts properly
I've been building ASP.Net applications for a few years now but most of my work is focused on business apps that'll be used by less than 50 people, running on an Intranet.
Today I had a conversation with a colleague who is thinking of using ASP.Net to build a commercial application that could potentially be used by 1 Million users. He wanted to know about the scalability of ASP.Net apps and how much (or how little) of stateful objects likes Session variables he could use and still keep his app scalable. To this I did not have an answer, which is why I'm turning to the community.
Striving to keep your bias to a minimum, if you were going to build an ASP.Net application for 1 Million users that provided a rich UI experience, what parts of Microsoft's technologies to keep track of state would you avoid or keep to a minimum?
We are working in a web application using Session variables to store the clients ID to operate with them in all app (making orders, reports, etc....) but randomly users get the client ID of another user in any moment using the application.
I have tried to solve it in a first step adding to system.web section in the web.config file this:
[Code]....
ASP.NET State Service is running in server normally, It began run just before this last change, but we have not solved the problem either with this solution.
The server is Windows Server 2003 Standard Edition SP2 32bits running IIS 6.0, and the application is made with Framework 2.0
There are a couple of user's experiences session variable loss after they've clicked a confirm button and their information is email via a relay hosting server. Below, I commented exactly where the session variables get lost.
What could be causing the session variable loss? So far, this only happens to a few users.
Part of the email that gets sent out:
[Code]....
Web config file:
[Code]....
How to keep the session variables even after closing the browser?
Everytime I close the browser, I lose all the session variables.
Is there any way to keep them?
How can I retain the value of variables that I fill from CodeBehind throughout the session? (C#). For example, I do a LINQ query from the log in "on-Click" button event. The query produces a bunch of data about the user that I want to access throughout the session on additional ASP pages. I know that I can pass a large query string but I suspect that there is a better way. Here's a specific...
from the db function I product: COS=2 (class of service). Throughout the session, I test for COS and display appropriate pages. Assume that the LINQ query is accomplished in the CodeBehind attached to the "loginButton" within the "login.aspx" page.
I am using Session ID Manager in all the pages of the website, but I am losing session variables in between the pages. what should I do to save the values of session variables.
Anoop
We are in the process of refactoring from cf to .net, so, I am working on the Login page and converting it from cf to .net. So, when I am autheticated and enter into our website, I need to redirect it to a cfm page (just temporary, since we will be refactoring that also eventually).
So, I am autheticated (using CustomMembership Provider model for sql server) and then when I redirect to the cfm, the app.cfm should validate the .net session variables. Here is where i am stuck:
I have the .net session variables in the aspx side:something like Session["UserId"].ToString() = Value from a login txt box (also authenticated against data in the database)
Session["UserName"].ToString() = Value from the db corresponding to the User Name entered in the text box.
So, now I have all the session variables in the .net side. Now, how do I retreive these .net session in the cf side? Any small peice of code to retrive the asp.net session variable in the application.cfm side would be great.
if using session variables to store and retrieve information is a bad practice? Let me give you some background:
I am developing a site for a friend of mine, and his site is hosted by Go-Daddy. My feeling is that Go-Daddy is not the best place to host a .NET site, but it is what it is.
After the first version of the site was published and people started using it, users immediately started having session time-out problems and null exceptions when referencing session variables. I researched everything I could and tried everything I could think to do, but I just could not correct the issue.
Then, while doing some testing, I discovered that users weren't individually timing-out and losing their session information, but, rather, all users where timing out at exactly the same time, regardless of how long they had been logged in or what they were doing. So, for whatever reason, the server was just dumping all sessions at random intervals.
At this point I needed to move on with the project so I added a number of cookies to replace the session variables, and everything began working properly.
in a hosted environment, should I avoid using session variables? Is it as problamatic as my research and experience would indicate, or is this simply due to the fact that I am working with a poor hosting company in Go-Daddy?
i have 2 different sites under different subdomains.
www.company.com
and e-order.company.com
i want to have SSO so i have tried to make a global cookie.
my question is :does the global cookie keeps the session variables when i am going from one site to another?
if not how can i pass a session variable for ex. session("userName") from one site to the other on redirect?