[RESOLVED] Windows 7 API Problems

[TTn]

You have absolutely nothing to loose by using DllImport,

Now you missed my points. Things to loose.
A. 16-bit backwards portability without an Alias.
B. Vbx backwards portability, or learning interchange towards .net for doubters.
C. Easier and more elegant to read for all team members, and readers in general.
Vb is more of a human/computer language, and should remain that way, especially for layman, or investors that can't understand C#, but need to look though the developers work. This is a professional tip.
D. Less line spaces, so code is shorter and easier to scroll through. More signifigant in larger projects, which matters to me.
E. No extra overhead to learn the different options, for existing vbers. Newcomers, most of which will not use the options will also save overhead.
F. No need to habit and repeat something(O.C.D), you will rarely if ever use.
When I use my hair brush, I have it in my hand, but I don't hold it evertime I go into the bathroom. Code isn't a place to ritualize, when it's an exception to the rule. This keeps inline with the intent of vb, which is RAD(rapid application development).


Things to gain:
A. If you plan on using C# now or future, imports will be interchangable, across languages. Not really signifigant or time saving for most, but true.
B. If you will be frequently using the rare options. Could be highly signifigant to a few.