design-decisions

Possible Duplicate: MVC versus WebForms ASP.NET MVC Performance I'll be starting a new web project in the coming weeks. It's a public facing web site for a somewhat famous person. I have 2 choices: use good-old ASP.NET 4 or new ASP.NET MVC 3 with Razor. I do not plan to do any kind of unit testing. It's rather simple website mainly consisting of javascript, html and css. I'll need to build an admin panel to create/delete/edit pages; add/remove pictures to portfolio gallery. And that's probably all I need from an admin panel. Nothing complicated. Disclaimer : I do not have much experience with

When should I not use the ThreadPool in .Net? It looks like the best option is to use a ThreadPool, in which case, why is it not the only option? What are your experiences around this? Will The only reason why I wouldn't use the ThreadPool for cheap multithreading is if I need to… interract with the method running (e.g., to kill it) run code on a STA thread (this happened to me) keep the thread alive after my application has died ( ThreadPool threads are background threads) in case I need to change the priority of the Thread. We can not change priority of threads in ThreadPool which is by

Is there a reason Microsoft decided to make these structs? All three are mutable. I would find them much easier to deal with if they were either immutable, or if they were reference types. If there are reasons they must be structs, why are they mutable? Why are they Structs Value Semantics There is no essential difference between two identical instances of these values. Any Point with coordinates, [2,3] is equal to any other point with the same coordinates, much like any two int s with similar value are equal. This is in conformance with the design guideline: It logically represents a single

This is something I had not noticed until today. Apparently, the .NET implementation of the much used tuple classes ( Tuple<T> , Tuple<T1, T2> etc) causes boxing penalties for value types when equality based operations are performed. Here is how the class is kind of implemented in the framework (source via ILSpy): public class Tuple<T1, T2> : IStructuralEquatable { public T1 Item1 { get; private set; } public T2 Item2 { get; private set; } public Tuple(T1 item1, T2 item2) { this.Item1 = item1; this.Item2 = item2; } public override bool Equals(object obj) { return this.Equals(obj,