A StaticResource will be resolved and assigned to the property during the loading of the XAML which occurs before the application is actually run. It will only be assigned once and any changes to resource dictionary ignored. A DynamicResource assigns an Expression object to the property during loading but does not actually lookup the resource … Read more
I’ve not used this method, but Michael Kaplan describes a method for doing so in his blog post (with a confusing title) that talks about stripping diacritics: Stripping is an interesting job (aka On the meaning of meaningless, aka All Mn characters are non-spacing, but some are more non-spacing than others) static string RemoveDiacritics(string text) … Read more
You can’t. There are steps you can take to make it a little more difficult, but ultimately any executable on the local machine is crackable. Eventually, that code has to be converted into native machine code and every application that is runnable is vulnerable. What you want to do is just make it difficult enough … Read more
You should always use the following syntax to rethrow an exception. Else you’ll stomp the stack trace: throw; If you print the trace resulting from throw ex, you’ll see that it ends on that statement and not at the real source of the exception. Basically, it should be deemed a criminal offense to use throw … Read more
Yes, there is a difference. throw ex resets the stack trace (so your errors would appear to originate from HandleException) throw doesn’t – the original offender would be preserved. static void Main(string[] args) { try { Method2(); } catch (Exception ex) { Console.Write(ex.StackTrace.ToString()); Console.ReadKey(); } } private static void Method2() { try { Method1(); } … Read more
If you try to run 32-bit applications on IIS 7 (and/or 64-bit OS machine), you will get the same error. So, from the IIS 7, right click on the applications’ application pool and go to “advanced settings” and change “Enable 32-Bit Applications” to “TRUE”. Restart your website and it should work.
Blanket catch statements that simply retry the same call can be dangerous if used as a general exception handling mechanism. Having said that, here’s a lambda-based retry wrapper that you can use with any method. I chose to factor the number of retries and the retry timeout out as parameters for a bit more flexibility: … Read more
Run a verify after the test with the Times.Never() option. _mock.Object.DoSomething() _mock.Verify(service => service.ShouldntBeCalled(), Times.Never());
This warning seems to have been introduced with the new Visual Studio 11 Beta and .NET 4.5, although I suppose it might have been possible before. First, it really is just a warning. It should not hurt anything if you are just dealing with x86 dependencies. Microsoft is just trying to warn you when you … Read more
Today, I would recommend using Task.CompletedTask to accomplish this. Pre .net 4.6: Using Task.FromResult(0) or Task.FromResult<object>(null) will incur less overhead than creating a Task with a no-op expression. When creating a Task with a result pre-determined, there is no scheduling overhead involved.