Changes between Version 11 and Version 12 of CodeBestPractices

Timestamp:

2012-02-22 13:57:48 (12 years ago)

Author:

jeroens

Comment:

--

CodeBestPractices

@@ -16 +16 @@
 
 == Target processor ==
-The EwE source code now fully utilizes 64-bit capabilies. In order to make sure that Windows finds the correct 32 or 64 bit Access drivers make sure you always compile your EwE6 main project against x86 or x64, never against AnyCPU in Menu > Build > Configuration Manager.
+The EwE source code now fully utilizes 64-bit capabilies. In order to make sure that Windows finds the correct 32 or 64 bit Access drivers make sure you always compile your EwE6 main project against x86 or x64, never against AnyCPU in'' Menu > Build > Configuration Manager''.
 
 Note that 64-bits EwE will not be able to find 32-bit Access database drivers and vice-versa.
 
 == Nasty experiences ==
- * Always override Dispose(bDisposing) to clean up UI elements, do not use !OnHandleDestroyed because the .NET framework, which wraps Win32 controls, may call this method during the regular life span of a .NET control to do housekeeping. The call may be followed by !OnHandleCreated - it's simply not a valid trigger to assume your control is dying. 
- * Note that the Visual Studio designer automagically places a Dispose method in its *.designer.vb files which is blocked from debugging. You may want to manually move this method to your main vb file and strip off !DebuggerNonUserCode tags that prevent the debugger from stepping through the code.
+ * Always override ''Dispose(bDisposing)'' to clean up UI elements, do not use ''!OnHandleDestroyed'' because the .NET framework, which wraps Win32 controls, may call this method during the regular life span of a .NET control to do housekeeping. The call may be followed by ''!OnHandleCreated'' - it's simply not a valid trigger to assume your control is dying. 
+ * Note that the Visual Studio designer automagically places a Dispose method in its *.designer.vb files which is blocked from debugging. You may want to manually move this method to your main vb file and strip off ''!DebuggerNonUserCode'' tags that prevent the debugger from stepping through the code.