Comments on: VCProjectEngine and x64 http://typedef.org/jcopenha/2007/05/22/vcprojectengine_and_x64/ the stuff Sat, 14 Nov 2009 13:53:30 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: jcopenha http://typedef.org/jcopenha/2007/05/22/vcprojectengine_and_x64/comment-page-1/#comment-905 jcopenha Sat, 15 Nov 2008 15:29:44 +0000 #comment-905 Interesting. But I WAS able to use the COM object to parse the file without [STAThread], I just couldn't get to the x64 definitions of the project. But you bring up a good point, I'm not sure how COM was getting initialized without [STAThread] so.. it is perplexing. Thanks for the comment. Interesting. But I WAS able to use the COM object to parse the file without [STAThread], I just couldn’t get to the x64 definitions of the project. But you bring up a good point, I’m not sure how COM was getting initialized without [STAThread] so.. it is perplexing. Thanks for the comment.

]]> By: John Festa http://typedef.org/jcopenha/2007/05/22/vcprojectengine_and_x64/comment-page-1/#comment-903 John Festa Sat, 15 Nov 2008 11:42:34 +0000 #comment-903 Your post turned up while I was searching for an answer to a problem I'm having under 64bit windows. Unfortunately your post doesnt answer my question, but I believe I can answer yours (better late than never ?). Console applications target the Windows console subsystem, not the windows subsystem. Console subsystems don't by-default initialize COM or have a message pump. Adding [STAThread] to the process entry procedure causes COM to be initialized, and a message pump made available for COM marshalling. Without this attribute you would also have issues popping up say, a FileOpen dialog from the console app. THe dialog would open, but never refresh. Your post turned up while I was searching for an answer to a problem I’m having under 64bit windows. Unfortunately your post doesnt answer my question, but I believe I can answer yours (better late than never ?).

Console applications target the Windows console subsystem, not the windows subsystem. Console subsystems don’t by-default initialize COM or have a message pump. Adding [STAThread] to the process entry procedure causes COM to be initialized, and a message pump made available for COM marshalling. Without this attribute you would also have issues popping up say, a FileOpen dialog from the console app. THe dialog would open, but never refresh.

]]>