I generally operate from the position that code must have a reason to exist. If it doesn't have a reason to be there, or be at this particular place, then it should be deleted, and I don't think twice about deleting code. So I tell my team that every piece
I'm setting up a service using .NET 4.5 to run with a new app we're writing which uses X509CertificateValidationMode: client.ClientCredentials.ServiceCertificate.Authentication.CertificateValidationMode = X509CertificateValidationMode.None; This service was build in .NET 4.0, where that enumeration exists in System.ServiceModel.Security. However, I was getting compilation errors when
Let's see how to use _Layout, RenderBody, RenderSection, and _ViewStart to organize our ASP.NET MVC views.
NOTE: I've got a more thorough version of this post up at Mapping DataTables and DataRows to Objects in C# using Reflection [https://www.exceptionnotfound.net/mapping-datatables-and-datarows-to-objects-in-csharp-and-net-using-reflection] . Check it out! We're in the process of converting an old ASP.NET WebForms application to MVC. For this particular project, we are
> Stop the world, I want to write it all down! > -attributed to Donald Knuth [http://en.wikipedia.org/wiki/Donald_Knuth] Permanent Students In my opinion, a programmer can do his job in the most productive way by believing that he is always a student. There are always multiple paths