G
Guest
I have the following problem with my application, a product I'm developing
(slimKEYS). This application can launch other processes, either applications,
URLs, etc. It usually starts automatically from a shortcut in the StartUp
folder. It also can target other application's main window for moving them
using hotkeys. The next version will include a manifest with the entry
"uiAccess=true" so it can also target windows belonging to isolated (e.g.:
IE7) or elevated processes. It's a managed strongly-named and
digitally-signed application.
Testing with the new manifest, when started from a StartUp shortcut, every
child application it launches become slow or randomly unresponsive. For
example, if FireFox is the default browser, launching an URL takes 10 seconds
before the FireFox window appears, and scrolling is very slow and glitchy. If
Opera is the default browser, it takes 2 minutes before the window appears,
and it won't even redraw. If IE7 is the default browser, it works, but that
can be explained by the fact that IE7 runs in isolated space.
If I launch Outlook, then click a link from Outlook which opens either
FireFox or Opera, the same problems as above occur. And Outlook itself is
slower than usual. Other applications I start, like Visual Studio .NET, are
very slow or experience apparent periodic timeouts. During those problems, I
do not see any CPU increase. I have tried disabling some services (e.g.
Defender, Application Experience), without success.
If I close my application (which started from a StartUp shortcut), start it
back, then launch other processes, every problem above disappear. Everything
works great. If my application does not have the manifest, everything works
great, even if started from the StartUp shortcut.
I have created a simple WinForms application, with a button that calls
System.Diagnostics.Process.Start with a simple URL. I have embedded a similar
manifest, strongly-named and digitally signed it. If I put a shortcut to it
in the StartUp folder, log-off and back in, and click on the button, the same
behavior occurs. If I close the application and start it from Windows
Explorer, everything works fine.
This problem is putting on hold my next release. Have I found a problem with
Windows Vista?
Thank you.
(slimKEYS). This application can launch other processes, either applications,
URLs, etc. It usually starts automatically from a shortcut in the StartUp
folder. It also can target other application's main window for moving them
using hotkeys. The next version will include a manifest with the entry
"uiAccess=true" so it can also target windows belonging to isolated (e.g.:
IE7) or elevated processes. It's a managed strongly-named and
digitally-signed application.
Testing with the new manifest, when started from a StartUp shortcut, every
child application it launches become slow or randomly unresponsive. For
example, if FireFox is the default browser, launching an URL takes 10 seconds
before the FireFox window appears, and scrolling is very slow and glitchy. If
Opera is the default browser, it takes 2 minutes before the window appears,
and it won't even redraw. If IE7 is the default browser, it works, but that
can be explained by the fact that IE7 runs in isolated space.
If I launch Outlook, then click a link from Outlook which opens either
FireFox or Opera, the same problems as above occur. And Outlook itself is
slower than usual. Other applications I start, like Visual Studio .NET, are
very slow or experience apparent periodic timeouts. During those problems, I
do not see any CPU increase. I have tried disabling some services (e.g.
Defender, Application Experience), without success.
If I close my application (which started from a StartUp shortcut), start it
back, then launch other processes, every problem above disappear. Everything
works great. If my application does not have the manifest, everything works
great, even if started from the StartUp shortcut.
I have created a simple WinForms application, with a button that calls
System.Diagnostics.Process.Start with a simple URL. I have embedded a similar
manifest, strongly-named and digitally signed it. If I put a shortcut to it
in the StartUp folder, log-off and back in, and click on the button, the same
behavior occurs. If I close the application and start it from Windows
Explorer, everything works fine.
This problem is putting on hold my next release. Have I found a problem with
Windows Vista?
Thank you.