configure WER, windows error reporting

Please, use the following article as the reference, configure WER dump:

Collecting User-Mode Dumps

Please, use the following values:

DumpFolder       – place on the D: drive and make sure it has appropriate permissions for any process to create files in there

DumpCount       – 5 – 10 dumps, depending on the free space available

DumpType          – set to 2 – Full dump

7:05 PM

Perfmon Counters to debug app pool crash for web apps

Create performance counter log to collect every 30 sec in BLG format the following counters:

.NET CLR Exceptions(*)*

.NET CLR Memory(*)*

.NET Memory Cache 4.0(*)*

.NET CLR Networking(*)*



\ASP.NET Applications(*)*

\ASP.NET v4.0.30319*

\ASP.NET Apps v4.0.30319(*)*

\Internet Information Services Global*

\HTTP Service Request Queues(*)*

\Web Service(*)*

\Web Service Cache*







\Server Work Queues(*)*

\Server (*)\

\Network Interface(*)*



actor vs task

Orleans is not the first actor framework for .NET. The NAct open-source project has been there for almost 4 years, and PostSharp has provided an implementation for 2 years.

.Net 4.5 also contains an actors-based library: TPL Dataflow.

async/await is completely unrelated to the Actor Model (Actors). Async/await has more in common with Akka Futures & Akka Dataflow

C#’s await is like Scala’s react, but without having to pass a continuation. Scala has the looprewriting, but C#’s await can rewrite any method. In general, I think C#’s await, Task, and TPL Dataflow are more lower-level than Scala’s actors – but also more flexible. Disclaimer: I learned everything I know about Scala in 5 minutes from this.

Horizontal scalability

Yet, Orleans is a significant release. It is the first actor implementation that really focuses on horizontal scalability. White both NAct and PostSharp Actor were limited to organizing concurrency within a single process, Orleans has been built from the ground up to cross the machine boundary and scale up to the cloud. Orleans is the first to be a real actor platform, not just a framework. The primary production environment of Orleans is Windows Azure. You can run it in-process for testing purposes, but the primary usage scenario is to deploy it on the cloud.


Every actor system seems to pick its own concrete name for the actor concept. Erlang calls them ‘processes,’ and Orleans calls them ‘grains.’


read more:

How to use alternate Fn keys without pressing Fn key

  1. Press the power button to turn your computer on
  2. Press F10 key to enter BIOS setup screen
  3. Use the left right arrow keys to navigate to “System Configuration”
  4. Use the up down arrow keys to navigate to the “action keys Mode”
  5. Press “Enter” to open the Enabled / Disabled menu
  6. Use up down arrow keys to select “Disable”
  7. Press the F10 key
  8. Use arrow keys to select “Yes”
  9. Press “Enter” to save changes and start windows

Now the F1 through F12 keys should all work as they should with just a single press without the fn key.