Caveats?

  • Thread starter Thread starter Luc The Perverse
  • Start date Start date
L

Luc The Perverse

I program on windows XP Prof edition with administrator priviledges. I
remember reading an article that on windows vista it will require
administrator priviledges to run a global keyboard hook - and this becomes
suddenly relevant as I am trying to make an application that responds to
global hotkeys.

I'll figure out a way around this particular issue. But I don't want to
miss the bigger picture. Is there a guide or an article I can read that
will educate me on the most common interoperability problems in C#?
 
Luc The Perverse said:
I program on windows XP Prof edition with administrator priviledges. I
remember reading an article that on windows vista it will require
administrator priviledges to run a global keyboard hook - and this becomes
suddenly relevant as I am trying to make an application that responds to
global hotkeys.

I'll figure out a way around this particular issue. But I don't want to
miss the bigger picture. Is there a guide or an article I can read that
will educate me on the most common interoperability problems in C#?
Click to expand...

Global hooks don't need administrative privileges, they need to run with an
"integrity level" that is at least as high as the" to be monitored
application". Integrity levels can be set in code (to a lower level only) or
via an application manifest file. Current versions of VS do not directly
support manifest files for managed applications, so you need to add a
manifest to the assembly in a post build step by running the mt.exe utility.
A lot more of this can be found on msdn, search for UAC, UIPI and "Integrity
Level", but I would suggest you to start reading this:
http://download.microsoft.com/downl...-932b-38acd478f46d/WindowsVistaUACDevReqs.doc

Willy.
 
Willy Denoyette said:
Global hooks don't need administrative privileges, they need to run with
an "integrity level" that is at least as high as the" to be monitored
application". Integrity levels can be set in code (to a lower level only)
or via an application manifest file. Current versions of VS do not
directly support manifest files for managed applications, so you need to
add a manifest to the assembly in a post build step by running the mt.exe
utility.
A lot more of this can be found on msdn, search for UAC, UIPI and
"Integrity Level", but I would suggest you to start reading this:
http://download.microsoft.com/downl...-932b-38acd478f46d/WindowsVistaUACDevReqs.doc

Willy.
Click to expand...

Awesome - a giant annoying 100 page document - That means it probably has
all the information I need!

Thank you sir
 
Back
Top