In software engineering, an anti-pattern (or antipattern) is a pattern that may be commonly used but is ineffective and/or counterproductive in practice.
Type the comment marker (//) followed by the word TODO where ever you want in the .cs or .vb file. Then it will appear in the Task List window. Later on you can see all the todo list you have added and then do the task correspondingly.
"Web garden" can be configured by using process model settings in "machine.config" or "Web.config" file. The configuration section is named and is shown in the following example. The process model is enabled by default enable="true"). Below is the snippet from config file.
From the above processModel section for web garden we are concerned with only two attributes "webgarden" and "cpuMask".
webGarden : Controls CPU affinity. True indicates that processes should be affinitized to the corresponding CPU. The default is False.
cpuMask : Specifies which processors on a multiprocessor server are eligible to run ASP.NET processes. The cpuMask value specifies a bit pattern that indicates the CPUs eligible to run ASP.NET threads. ASP.NET launches one worker process for each eligible CPU. If webGarden is set to false, cpuMask is ignored and only one worker process will run regardless of the number of processors in the machine. If webGarden is set to true, ASP.NET launches one worker process for each CPU that corresponds to a set bit in cpuMask. The default value of cpuMask is 0xffffffff.
Use 1 for the processor that you want to use for ASP.NET. Use 0 for the processor that you do not want to use for ASP.NET. For example, if you want to use the first two processors for ASP.NET of a four-processor computer, type 1100.
* Low (IIS process) In this main IIS process and ASP.NET application run in same process. So if any one crashes the other is also affected. So all application and the IIS process runs on the same process. In case any website crashes it affects everyone. * Medium (Pooled) In Medium pooled scenario the IIS and web application run in different processes. So in this case there are two processes process1 and process2. In process1 the IIS process is running and in process2 we have all Web applications running. * High (Isolated) In high isolated scenario every process is running is there own process. This consumes heavy memory but has highest reliability.