Why would you ever use asp.net’s ViewState storage object over the Session storage object?
Other than because session storage is session-global to more than one page, why would you ever want to use the viewstate to hold values?
Other than because session storage is session-global to more than one page, why would you ever want to use the viewstate to hold values?
I am trying to use OpenID in my website using asp.net_c#. I am working on asp.net forms website with asp.net v4. The issue i am having is with openidselector control from my toolbox generated from dotnetopenauth.dll. It does not work and not even displays. Any help?
how do you set css to add an asp img?
How to change table names in ASP.net Identity 3.0?
I have a Web Application running in one machine and the services in another machine (i.e.both are in different App domains). I have a workflow service in my service layer which gets the Synschronization Context from SynchronizationContext.Current. I get the SynchronizationContext.Current always as null. But If I run both my application and service layer in the same machine (i.e. same appdomain) the SynchronizationContext.Current is AspNetSynchronizationContext and it works fine. Can somebody help me to resolve this to run different app domains.
I am new to ASP.NET and wanted to capture details about people on my site. So I capture the Request.UserAgent
attributes to file. Can anyone explain how to deconstruct these so I know what they mean? I am actually stumped by some of the user agents I see. Examples:
here is the code I create textbox from C# code..
I work on a Comet application written in ASP.NET. There is an array of active connection contexts (HttpContext). And there is a thread that should periodically iterate through the collection and check theirs state. So application architecture is not thread-per-request.
This is the JavaScript that is errored on in IE but works in FF (error – “document.getelementsbyname(…).0.innerhtml is null or not an object”: