[.NET 3.5 SP1]具有UAC的SendKeys.SendWait(...) [英] [.NET 3.5 SP1] SendKeys.SendWait(...) with UAC

问题描述

大家好，

我在多个博客上读到SendKeys.SendWait(...)不能正常工作，因为它以前在Windows XP，Windows 2003下都可以工作.这很可悲...但是我的用户现在正在迁移到Windows Vista和我的应用程序不再起作用.为什么?仅仅是因为我在多个应用程序中大量使用了SendKeys.SendWait(...).

I read on multiple blogs that SendKeys.SendWait(...) doesn't work as it used to work under Windows XP, Windows 2003. This is very sad... But my users are now migrating to Windows Vista and my application doesn't work anymore. Why? Simply because I do intensive use of SendKeys.SendWait(...) across multiple applications.

我了解Microsoft做出的安全性决定和方向，但是有什么方法可以解决新功能?我知道我可以禁用UAC，并且我的应用程序将再次开始工作，但是这不是我的选择:必须启用UAC，并且我的用户不是其PC的管理员.

I understand the security decision and direction taken by Microsoft, but it there a way to workaround that new feature? I am aware that I can disable UAC and my application will start to work again, but it is not an option for me: UAC has to be enable and my users are not administrator on their PCs.

我读到我需要提升我的应用程序，对其进行签名等.但是，我不知道该怎么办，我希望您的帮助告诉我:

I read that I will need to elevate my application, sign it, etc. However, I don't know how to do that I would like your help to tell me: 

-我想工作SendKeys.SendWait，如果我的应用程序签名，提升等，它可以解决我的问题吗?

- I want to make work SendKeys.SendWait, will it fix my problem if my application is signed, elevated, etc.?

-如果是这样，如何实现?您能给我一个解决方案，推荐我去看书，写博客等吗?

- If so, how do I acheive that? Can you give me a solution, refer me to a book, blog post, etc.?

谢谢！

推荐答案

按下(我知道这是一个很老的线程，但是我遇到了同样的问题，发现了尚无解决方案)

pushed (i know this is a quite old thread but i'm having the same problem and found no solution yet)

这篇关于[.NET 3.5 SP1]具有UAC的SendKeys.SendWait(...)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！