Post by KBHey Lawrence,
Lighten up. The post is legitimate and your response was snippy. While I
agree that you should develop 64 bit with a 64 bit machine, which I am doing,
I also can duplicate the PrintDialog not opening under Vista X64. Anybody
out there have a comment intended to help rather than chastise?
Post by Lawrence Garvin (MVP)Post by VerySeriousI have an ordinary PrintDialog and printing functionality written in C#,
developed with Visual Studio 2008. Printing works fine for users with
32-bit
Vista and XP and Server 2003. For the users who have 64-bit Vista,
nothing
happens at all! No error message, but the PrintDialog simply does
nothing.
Does anyone know what I can do to make the PrintDialog work in 64-bit Vista?
I do not have a machine with 64-bit Vista to test or reproduce the issue.
Then you probably shouldn't be developing software "designed for use on 64
bit systems"!
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website:http://www.microsoft.com/wsus
My Websites:http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile:http://mvp.support.microsoft.com/profile/Lawrence.Garvin- Hide quoted text -
- Show quoted text -
We have the same problem and we can't get it to work either.
And yes we ARE developing on 64 bit Vista. We have brand new Dell quad
proc Vista Business 64 bit machines that are otherwise quite snappy
and run Vista itself, apps, and the development environments (both
VS05 and 08, etc) very well and very fast. They are all fully updated,
tweaked, and configured Vista 64 bit itself, for our network
environment, and for our printers.
But we cannot get the PrintDialog to work no matter what, and yes
we've set UseEx... and have tried all the other tricks and tips out
there.
We wrote a test app that *will* open a PrintDialog, but only AFTER the
process (either our full up app suite or the test app) are left
hanging on the ShowDialog call, completely unresponsive, for 2-10
**MINUTES**!!!!
No Exceptions thrown, no return value, no hanging app interference
from Vista/Windows, no nothing.