NOTE – If this answer doesn’t help you, please take the time to scroll down through the other answers that people have added since. Short answer This can happen if you add a method to an interface in one assembly, and then to an implementing class in another assembly, but you rebuild the implementing assembly … Read more
ASP.NET MVC1 -> MVC3 string path = HttpContext.Current.Server.MapPath(“~/App_Data/somedata.xml”); ASP.NET MVC4 string path = Server.MapPath(“~/App_Data/somedata.xml”); MSDN Reference: HttpServerUtility.MapPath Method
Dapper supports this directly. For example… string sql = “SELECT * FROM SomeTable WHERE id IN @ids” var results = conn.Query(sql, new { ids = new[] { 1, 2, 3, 4, 5 }}); unless you are using Postgres, in which case see this answer
Use the static method Guid.NewGuid() instead of calling the default constructor. var responseObject = proxy.CallService(new RequestObject { Data = “misc. data”, Guid = Guid.NewGuid() });
For short month names use: string monthName = new DateTime(2010, 8, 1) .ToString(“MMM”, CultureInfo.InvariantCulture); For long/full month names for Spanish (“es”) culture: string fullMonthName = new DateTime(2015, i, 1).ToString(“MMMM”, CultureInfo.CreateSpecificCulture(“es”));
In VS – project properties – in the Build tab – platform target =X86
Additionally a simpler example: return (T)Activator.CreateInstance(typeof(T), new object[] { weight }); Note that using the new() constraint on T is only to make the compiler check for a public parameterless constructor at compile time, the actual code used to create the type is the Activator class. You will need to ensure yourself regarding the specific … Read more
RELEASE is not defined, but you can use #if (!DEBUG) … #endif
The way to preserve the stack trace is through the use of the throw; This is valid as well try { // something that bombs here } catch (Exception ex) { throw; } throw ex; is basically like throwing an exception from that point, so the stack trace would only go to where you are … Read more
The difference is that in the first case the retrieved user is not tracked by the context so when you are going to save the user back to database you must attach it and set correctly state of the user so that EF knows that it should update existing user instead of inserting a new … Read more