You are misusing the API. Here’s the situation: in ASP.NET, only one thread can handle a request at a time. You can do some parallel processing if necessary (borrowing additional threads from the thread pool), but only one thread would have the request context (the additional threads do not have the request context). This is … Read more
Some of these fall into the category of general NLog (or logging) tips rather than strictly configuration suggestions. Here are some general logging links from here at SO (you might have seen some or all of these already): log4net vs. Nlog Logging best practices What’s the point of a logging facade? Why do loggers recommend … Read more
You can specify a MaxDegreeOfParallelism in a ParallelOptions parameter: Parallel.ForEach( listOfWebpages, new ParallelOptions { MaxDegreeOfParallelism = 4 }, webpage => { Download(webpage); } ); MSDN: Parallel.ForEach MSDN: ParallelOptions.MaxDegreeOfParallelism
To understand event handlers, you need to understand delegates. In C#, you can think of a delegate as a pointer (or a reference) to a method. This is useful because the pointer can be passed around as a value. The central concept of a delegate is its signature, or shape. That is (1) the return … Read more
What’s new in .NET Framework 4 Client Profile RTM explains many of the differences: When to use NET4 Client Profile and when to use NET4 Full Framework? NET4 Client Profile: Always target NET4 Client Profile for all your client desktop applications (including Windows Forms and WPF apps). NET4 Full framework: Target NET4 Full only if … Read more
After having the same problem as you and doing some reading, I discovered the solution – Pack URIs. I did the following in code: Image finalImage = new Image(); finalImage.Width = 80; … BitmapImage logo = new BitmapImage(); logo.BeginInit(); logo.UriSource = new Uri(“pack://application:,,,/AssemblyName;component/Resources/logo.png”); logo.EndInit(); … finalImage.Source = logo; Or shorter, by using another BitmapImage constructor: … Read more
The await inside your asynchronous method is trying to come back to the UI thread. Since the UI thread is busy waiting for the entire task to complete, you have a deadlock. Moving the async call to Task.Run() solves the issue. Because the async call is now running on a thread pool thread, it doesn’t … Read more
What is it? When you create an object in a .Net framework application, you don’t need to think about how the data is stored in memory. Because the .Net Framework takes care of that for you. However, if you want to store the contents of an object to a file, send an object to another … Read more
Look at the inner exception that you are getting. It will tell you which field/property it is having trouble serializing. You can exclude fields/properties from xml serialization by decorating them with the [XmlIgnore] attribute. XmlSerializer does not use the [Serializable] attribute, so I doubt that is the problem.