In a website, if I have a class:
[code]....
How many times the query will be compiled? Every time the page loads...? Once in the application...?
I have a tricky situation. My application got deployed in production. A lable value needs to be changed but the problem is am setting the label value dyanamically from page load of my page. Is there way to change the label value withour redeploying? i can change the logic on codebehind but that requires another deployement which i don't want to do that as it is production.
View 1 RepliesI would like to wrap Session variables in a manner similar to that discussed on CodeProject.
[code]....
Here is my question: if I have to access CurrentUser multiple times in the same page, would I get a performance improvement by assigning it to a local variable instead of accessing the wrapping property? Or does the HttpSessionState make sure the object is only deserialized once per request, so that subsequent calls in the same http request don't cost any more?
how can i bind data to gridview when using compiles query?
load all country
[code]....
how can I build 'compiled query' includes lots of paramters. Example. I use only one parameter in this code.
[Code]....
How can I write a query that it can takes lots of dynamic parameters and dynamic conditions.
Is there anyway except changeing and saveing the web.config file to make an ASP.net application to recompile itself?...
My teacher told the that by changeing the web.config file..the application whould get recompiled...but I concider that sort of an "hack" to have to change the web.config to recompile the application..is there any other way? I have tried to find something about this over the internet but I wasn't realy sure about what to search for...
I've written a singleton class that exposes the web.config properties in a nice get property kind of way.
I want a Load method to parse the data in the config and set the public properties, and I want to throw exceptions (so they are logged in the EventLog) when a configuration key is missing or can't be parsed.
I tried placing the Load() code in Application_Start of the global.asax but then remembered this will only be run once, or until the application restarts.
Where is the best place to put code that you need to run 'everytime' your site is started/run by the user? I basically want the website to stop functioning if certain config properties cannot be loaded.
I'm using "VS 2010 Ultimate" "Web Application" project.
The problem is that web application compilation occurs at run-time.
My steps:
1) change Wep Application source code (*.cs files)
2) rebuild "Web Application" in Visual Studio
3) run web site's(mapped under IIS 7.5) start page via browser
4) Problem: CSC.EXE starts compiling wep application for the second time! Despite I've done it on step 2)
What should I do to escape step 4) ? I don't need re-compilation at run-time!
I've tried "to play" with <compilation batch="false" but it seems to be ignored.
I have read under: Compiling Web Application Projects [URL]
... this compilation model creates a single assembly, you can specify attributes, such as assembly name and version.
You can supply a PATH (directory name only) in the Visual Studio "Build Options".
But where can the file name for the assembly be specified?
Does code in an .aspx page (in between <% %> tags) get compiled in a web application or is it treated like markup where you can just change it without recompiling the solution? Does compiling only compile the code behind code in the .cs and designer.cs files ?
View 2 RepliesI want to publish my web application as a single .dll file without all the source code and .aspx markup pages.
I am using VS 2010 with the "Web Deployment Project" add-in. In the compilation settings, I unchecked "make this site updatable" because I want the .aspx files to be compiled as well.
Publishing my web application using the publish feature in VS 2010 works fine, and a single .dll file is created in the "bin" directory.
But all the .aspx markup files are still copied to the web server! I've read that those files are merely marker files which can be deleted, but not in my case. They still contain the whole markup and when I delete them, my application won't run anymore.
It's like I had checked the "make this site updatable" option, but I haven't!
[code]....
I have a web application and I'm using asp.net routing. When I publish it with the Only files needed to run this application selected it gives me an error when I'm loading any of the page "HTTP Error 404 - File or directory not found."
but if I choose publish All files it works fine.
Do you know how to resolve this issue?
I have the following attributes in my table
[code]....
how do I create sql query to find out the number of times participant A took part in the club activity?
I have a ASP.NET 3.5 web application and I would like to allow users to install this web application multiple times on the same server.
--------
WebApp1 - database1
WebApp2 - database2
WebApp3 - database3
In my MVC application ,I am updating my web.config at runtime through application_start event.So, ideally it should be done only when the application is started.BUT in MY mvc application the application_start event of global.asax is being called multiple
times , even when i have not restarted the application.
Its being repetadly called when i am calling different actions , so the webconfig is repetedly updating & making my application very very slow. what's the reason & how to handle this .
I have a web application that was working fine. I had to make minor changes that had nothing to do with the Session object in any way. When I run local everything works fine. When I publish to our testing box it all runs fine. When I publish to production it times out on the Session object. Dozens of other applications on the production server run fine and have no trouble with Session.
It does not matter if the line is:
Session("PreferredName") = sPreferredName
or:
sPreferredName = Session("PreferredName")
I had the server admin remove the application pool and directory and recreate them and then I republished and it still happens.
Web application initialization is as follows:
As we know when IIS receives the first request for a particular Asp.net application resource, IIS creates an instance of a HttpApplication (defined in global.asax codebehind).When this new instance is created it's initialization happens that also checks all configured HTTP modules.All modules are then instantiated and put in the application's Modules collection (of type HttpModuleCollection)modules are looped through and their Init() method is called (when they register for request events)
As far as I understand it the above scenario happens when a web application is started/initialized (hence application start event).What happens with modules?
Are they (re)instatiated on each request or reused from the Modules property on each consecutive request while the web application is alive? As I understand IIS and Asp.net they are reused through the whole life of a web application.
If they are reused, can we assume that their Init() method is actually a pseudo event handler for application start event? The thing is we can't attach to application level events within http modules. But if they are being reused we could use Init() as application start event and do whatever we'd put in global.asax instead.
Question,Can we assume that module's Init() method is called only on application start event? Could we use this assumption to i.e. register routes for applications whose global.asax codebehind we can't change? web.config is usually accessible and we can change it the way we want.Would this actually work?
Additional info,We can check HttpApplication code and check its InitModulesCommon() method. This one actually calls Init() of each registered HTTP module. What is more interesting is that this method is only used by InitIntegratedModules() and InitModules() methods. Which are both used only in HttpApplication.InitInternal() method. This is the basis of my assumptions, but I would like to know whether someone has abused IHttpModule.Init() for application start event.
We have an MVC.NET application that encounters fatal errors when it restarts. In our Session_Start event handler, we add the session id to a dictionary. In the Session_End handler, we remove it. Consider the following sequence of requests:
GET home.mvc
<application restarts>
GET main.css
GET banner.jpg
GET somedata.mvc
...
Because of the way the application is architected, this sort of sequence happens fairly frequently if you do a rebuild while the application is open in a browser window. That wouldn't be terribly concerning except that I see it in production environments too. For example, it will occur (albeit rarely) when you edit web.config.
The requests following the restart are all due to links in the home page or AJAX calls from JavaScript.
What I observe is that .NET handles the first 5 requests in parallel. Each such request causes it to fire the Session_Start event. After a short time, it fires the Session_End event 3 times. To be clear, each Session_Start corresponds to the exact same session. They all have the same session id and the IsNewSession property is true for all session state objects. Also, the Session_End events do not correspond to the session being killed. The session persists, along with any data stored in session state.
I need to either prevent it from firing Session_Start more than once or figure out how to tell when Session_End doesn't really mean that the session has ended.
I downloaded VWD 2008 express months ago. Don't know what happened but my design view went.I have reinstalled the application several times but no success. I posted this problem on several forums and got many suggestions like uninstall office 2007, reinstall web authoring component, install n et.framework 3.5 which is not compatible with Win7 and does not install, so I have net.framework 4.0. I tried to bburn the iso file installation package, burnt it to a dvd and install it from the media, nothing.My pc is a Compaq Presario CQ61 Notebook running Win7 Home Edition.
View 2 RepliesI am looking at how best to prevent a single user account logging on multiple times in a webforms application. I know that MembershipUser.IsOnline exists, but I've read a few forum and blog entries suggesting that this can be unreliable, particularly in scenarios where a user closes a browser (without logging out) and attempts to logon with a different machine or browser.I looked at implementing a last past the post type system; when a user logs on older users are simply kicked off. It seems that FormsAuthentication.Signout() only works for the current user.
View 2 RepliesI've done a bit of searching on this subject and haven't found anything so far. I am successfully using the Profile object and am saving Profile records away into my SQL Server Database. I have checked using the stored procedures and viewed the individual records to know they are there. However, I want to create a WebForm that can enumerate through all of the users in my Membership DB (Same DB as the Profile DB) and list each user in a grid showing what values each user has within their profile. For example:
Username
Profile Element 1
Profile Element 2
Profile Element 3
bob
true
false
true
fred
true
false
true
I want however to replace the 'Profile Element 1' etc etc to display the actual name of the Profile. I would like to do this programmatically so I don't have to recompile the website everytime I add a new Profile element.
How to pass query string from one application to another application, i need to send values through one page of application to another application,I am using inprocess session state.
from loging page i need to send sessions to another applicaion but here sending sessions are some what diffcult (after googling).so is it possible through query strings???if yes How pass them please tell me the sample example.will it be possible through coockies?? or query strings. How
i am using sql server inbuilt mail system for sending mail.and i made SP to call dbmail sp
now my problem is when i call sp it get executed fine but in last suppose 1000 mails queued then 1000 times i get mail queued.and that my connection time out .i extend connection time out limit but i get error msg like
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Mail queued."
my mail get queued well proper but due to 1000 or 100000 mail queued its lost of msg make problem.
In building custom controls, I've seen two patterns for using the viewstate. One is to use properties to disguise the viewstate access as persistent data.
public bool AllowStuff
{
get
{
return (ViewState[constKeyAllowStuff] != null) ?
(bool)ViewState[constKeyAllowStuff] : false;
}
set { ViewState[constKeyAllowStuff] = value; }
}
The other is to use private member fields and to override the Load/SaveViewState methods on the control and handle it all explicitly:
protected override object SaveViewState()
{
object[] myViewState = new object[2];
myViewState[0] = base.SaveViewState();
myViewState[1] = _allowStuff;
return myViewState;
}
protected override void LoadViewState(object savedState)
{
object[] stateArray = (object[])savedState;
base.LoadViewState(stateArray[0]);
_allowStuff = (bool)stateArray[1];
}
(I cut out a lot of safety checking for clarity, so just ignore that.) Is there are particular advantage to one method over the other? I can't see how they'd differ much performance wise. Version 1 is lazy, so I guess you save a bit if you don't need that particular value during a pass. Version 1 is also more abstract, hides the details better. Version 2 is clearer about when the data is actually valid and ok to read or modify (between the load and save) because it more clearly works within the ASP.NET lifecycle. Version 2 does tend to require more boilerplate code though (a property, a backing private field, and viewstate handling in two places) as opposed to Version 1 which combines all that into one place.
I'm using a file manager-type WebControl that does lots of postbacks. It's placed inside a Page that is relatively complex. I would like to prevent the WebControl from causing the whole Page to go through the lifecycle.
Is there any way to isolate the WebControl from the rest of the Page? The only way I can think of is sticking the WebControl in a separate Page and creating an iframe in the original Page. Unfortunately that also means my WebControl properties/settings are no longer in the original Page. If I want two instances of the WebControl with different settings, then I have to create a Page for each setting and reference the correct one in my iframes. Not quite as "drag & drop" as I would like.