The short answer: interning literal strings is cheap at runtime and saves memory. Interning non-literal strings is expensive at runtime and therefore saves a tiny amount of memory in exchange for making the common cases much slower. The cost of the interning-strings-at-runtime “optimization” does not pay for the benefit, and is therefore not actually an … Read more
You can use _com_error: _com_error err(hr); LPCTSTR errMsg = err.ErrorMessage(); If you don’t want to use _com_error for whatever reason, you can still take a look at its source, and see how it’s done. Don’t forget to include the header comdef.h
I received this error after refactoring. I had two projects compiling to DLLs with the same name. Check the “Assembly name” in the project’s properties’ “Application” section.
You’re always seeding a new instance with the same seed, and then grabbing the first max. By using a Seed, you’re guaranteeing the same results. If you want to have a static, random number generation that does different results, you should rework this a bit. However, since Random is not threadsafe, it requires some synchronization … Read more
The short answer is that the switch statement executes linearly, while the dictionary executes logarithmically. At the IL level, a small switch statement is usually implemented as a series of if-elseif statements comparing equality of the switched variable and each case. So, this statement will execute in a time linearly proportional to the number of … Read more
I think this is a bug. You are seeing the side-effect of automatic layout, it likes to align non-trivial fields to an address that’s a multiple of 8 bytes in 64-bit mode. It occurs even when you explicitly apply the [StructLayout(LayoutKind.Sequential)] attribute. That is not supposed to happen. You can see it by making the … Read more
A more “batteries-included” implementation of this kind of thing, including language support, is now available as of C# 8.0. Now, when using at least C# 8.0 (or higher) with .NET Standard 2.1 (or higher) and/or .NET Core 3.0 (or higher), the code from the original question may be written as follows: private async IAsyncEnumerable<char> TestAsync(string … Read more
Absolutely not! Convert tries to get you an Int32 via “any means possible”. Cast does nothing of the sort. With cast you are telling the compiler to treat the object as Int, without conversion. You should always use cast when you know (by design) that the object is an Int32 or another class that has … Read more
From the Mono Project’s Guide to Porting Winforms Applications: public static bool IsRunningOnMono () { return Type.GetType (“Mono.Runtime”) != null; } I’m sure you’ll have a lot more questions, so worth checking this guide and the mono-forums
a Control that was constructed off the UI thread… Yes, that is a good way to trigger this problem. The underlying problem is caused by the SystemEvents class, it has the unenviable task of raising its events on the correct thread. The UserPreferenceChanged event is the typical trouble-maker, lots of controls subscribe it so they … Read more