Tuesday, March 23, 2004
(0) commentsFriday, March 12, 2004
What's new in ADO.NET version 2.0
Found an interesting article outlining some of the new features in ADO.NET v2.0. The ObjectSpaces concept sounds particularly interesting, although its support for SQL Server only diminishes its usefulness somewhat.
C# Naming Standards
As the C# pioneer at our Company, I've taken it upon myself to decide upon some C# coding standards. These are largely based on the
Microsoft design guidelines, but have been changed to make them (IMHO) friendlier to other .NET languages (e.g. Delphi).
As a result, I've tentatively decided on the following naming standards (I've only stated the ones that differ from the MS recommendations):-
Class instance members
Using camel casing prefixed by m (e.g. mSomeValue)
Method arguments
Using camel casing prefixed by a (e.g. aSomeValue)
Property names
Do not expose a property with the same name as its underlying type. This goes directly against what Microsoft recommends, but makes it easier for compilers that don't employ 'try, try again' scope resolution.
Microsoft design guidelines, but have been changed to make them (IMHO) friendlier to other .NET languages (e.g. Delphi).
As a result, I've tentatively decided on the following naming standards (I've only stated the ones that differ from the MS recommendations):-
Class instance members
Using camel casing prefixed by m (e.g. mSomeValue)
Method arguments
Using camel casing prefixed by a (e.g. aSomeValue)
Property names
Do not expose a property with the same name as its underlying type. This goes directly against what Microsoft recommends, but makes it easier for compilers that don't employ 'try, try again' scope resolution.
Another reason to hate VS.NET 2003
Why oh why does the 'Apply to all items' setting not persist across multiple projects in a solution when working with SourceSafe integration? There is nothing more annoying than having to answer the same question multiple times when you were under the impression you had already told SourceSafe your intentions.
Reminds me of my first SourceSafe install experience. Apart from the fact that the install process required 6 (no exaggeration) reboots, the following dialog took place (paraphrased, but you get the idea)
Stupid SourceSafe Install Script: Install completed successfully. Reboot the computer now?
Me: No
SSIS: 'The computer has to be rebooted in order to complete the installation. The computer will reboot now.
Me: $#%!!
Tuesday, March 02, 2004
Blog This!
I am testing some new blogging software called w.bloggar. It should allow me to post blog entries without needing to use a browser.
