Bill Wert's weblogStriving to make managed code fast...Tip: Don't rely on environment variables for critical decisions- February 25, 2008 I saw a mail this week asking how you can determine what bitness your process is running in, and one of the suggestions was to check for the PROCESSOR_ARCHITEW6432 environment variable. If that variable exists, you know you're on 64 bit Windows in a 32 bit process. It's likely that the questioner needs to know which bitness the application is running in so the correct bitness DLL can be loaded, since by default native code is processor agnostic. This is one example, but the broader point really.http://blogs.msdn.com/billwert/archive/2008/02/24/tip-don-t-rely-on-environment-variables-... Use of SGEN.exe to avoid common XmlSerializer performance pitfalls- February 23, 2008 This week, I encountered a test scenario which makes use of an XmlSerializer on it's startup path. Unfortunately, MSDN's documentation for the type is not clear on the performance impact of using an XmlSerializer. The documentation on introducing XML serialization, found here, actually mentions the solution, but it also does not state what the problem is. When you use an XmlSerializer, a helper assembly(1) with a custom type for serializing your type is created. The C CodeDom is used to...http://blogs.msdn.com/billwert/archive/2008/02/23/use-of-sgen-exe-to-avoid-common-xmlseria... |