search

tunglam236 / QLBH

Automatically exported from code.google.com/p/wittytwitter
0 stars 0 forks source link

witty and growl on 64bit OS #254

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
0. get a 64bit system/OS 
1. download trunk/nightly version of witty
2. launch witty
3. get target invocation exception

log file 
"[Header]\r\n2009-05-29 18:14:03,303 [10] INFO  Witty.Logging - Witty is 
starting.
2009-05-29 18:14:03,746 [10] ERROR Witty.Logging - Unhandled Exception
System.Windows.Markup.XamlParseException: Cannot create instance of 
'MainWindow' defined in assembly 'Witty, Version=2.2.0.31001, 
Culture=neutral, PublicKeyToken=null'. Exception has been thrown by the 
target of an invocation.  Error in markup file 
'Witty;component/MainWindow.xaml' Line 2 Position 3. ---> 
System.Reflection.TargetInvocationException: Exception has been thrown by 
the target of an invocation. ---> System.BadImageFormatException: Could not 
load file or assembly 'Growl.Connector, Version=2.0.0.0, Culture=neutral, 
PublicKeyToken=980c2339411be384' or one of its dependencies. An attempt was 
made to load a program with an incorrect format." 

What is the expected output? What do you see instead?
normal launch :)

What version of the product are you using? On what operating system?
nightly build and experimental / Windows 7 RC 64bit

I was able to run witty after modifying the target CPU in VS (properties > 
build > platform target to x86 from any CPU)

Original issue reported on code.google.com by matthie...@gmail.com on 29 May 2009 at 10:32

GoogleCodeExporter commented 8 years ago 
Thanks! I've checked in this fix, will be included in next build.

Original comment by jongallo...@gmail.com on 4 Jun 2009 at 3:29

GoogleCodeExporter commented 8 years ago 
Same symptoms on XP64.  Nothing in the log file for me though.  Just "Witty is
starting" then windows "do you want to debug" message.

Original comment by mruh...@gmail.com on 8 Jul 2009 at 3:57

GoogleCodeExporter commented 8 years ago 
if the Growl libraries were the only thing causing you to have to compile in x86
mode, you will be glad to know they have been updated to be 64-bit compatible:

http://blog.growlforwindows.com/2009/08/growl-net-library-now-64-bit-compatible.
html

Original comment by briandun...@gmail.com on 3 Sep 2009 at 1:24