Mischa Kroon

Roy Osherove put together a bit of code which let you databind using attributes.

It uses reflection so it might be a bit slow...
Might be a good place to try and implement code generation instead.

http://weblogs.asp.net/rosherove/archive/2004/08/31/222948.aspx

The following website contains amongst other things a lot of error strings on which people can search through google.
Great stuff for security auditing of websites :)

http://johnny.ihackstuff.com/

Windows XP SP2 Full

“Overview

Microsoft Windows XP Service Pack 2 (SP2) provides new proactive security technologies for Windows XP to better defend against viruses, worms, and hackers.  In addition to a more robust security infrastructure, SP2 improves the security configuration options of Windows XP and provides better security information to help users faced with security decisions.

DO NOT CLICK DOWNLOAD IF YOU ARE UPDATING JUST ONE COMPUTER: A smaller, more appropriate download will be available soon on Windows Update. To receive this download, turn on the Automatic Updates feature in Windows XP to receive an optimized download of SP2. Please visit Protect Your PC for more information on receiving Windows XP SP2. “

Just read something quite disturbing on Rockford Lhotka's weblog.

It seems that the Command object when used in conjunction with OLEDB.
Uses unmanaged resources and should be disposed.

The long version can be found here

Post by Rockford Lhotka:

Read complete post here

The list:

1. One key VB feature is that it eliminates an entire class of runtime error you get in case sensitive languages - where a method parameter and property in the same class have the same name but for case. These problems can only be found through runtime testing, not by the compiler. This is a stupid thing that is solved in VB by avoiding the archaic concept of case sensitivity.
2. Handle multiple events in single method (superior separation of interface and implementation).
3. WithEvents is a huge difference in general, since it dramatically simplifies (or even enables) several code generation scenarios.
4. In VB you can actually tell the difference between inheriting from a base class and implementing an interface. In C# the syntax for both is identical, even though the semantic meaning is very different.
5. Implement multiple interface items in a single method (superior separation of interface and implementation).
6. Also, independent naming/scoping of methods that implement an interface method - C# interface implementation is comparable to the sucky way VB6 did it... (superior separation of interface and implementation).
7. Multiple indexed properties (C# only allows a single indexed property).
8. Optional parameters (important for Office integration, and general code cleanliness).
9. Late binding (C# requires manual use of reflection).
10. There are several COM interop features in VB that require much more work in C#. VB has the ComClass attribute and the CreateObject method for instance.
11. The Cxxx() methods (such as CDate, CInt, CStr, etc) offer some serious benefits over Convert.xxx. Sometimes performance, but more often increased functionality that takes several lines of C# to achieve.
12. The VB RTL also includes a bunch of complex financial functions for dealing with interest, etc. In C# you either write them by hand or buy a third-party library (because self-respecting C# devs won't use the VB RTL even if they have to pay for an alternative).
13. The InputBox method is a simple way to get a string from the user without having to build a custom form.
14. Sound a Beep in less than a page of code.

Finally had some time today to do some research on how to use it in the things I do at work. <

Figured I could at least find a stored procedure generator to work with and hoped there would be some sort of a UI generator script which I could use for simple admins which I could tinker with.

First thing is found, UI will have to wait till tomorrow.

To be honest I expected a little more from CodeSmith ... although it has provided me with a stored procedure Lib already.

MyGeneration Looks really good will have a better look at that tommorow am curious what my other options are...

I know I've been a little light on technical content for a while.  So time to start posting things which are actually usefull to developers...

How to turn off the horizontal scrollbar, I take it that this one is a bit hard to find since it's not in the intellisence off VS.NET :)

In the CSS of your body tag use:
overflow-x: hidden;

Or if you want the vertical bar hidden:
overflow-y: hidden;

And if you want to hide both:
overflow: hidden;