Closed GoogleCodeExporter closed 9 years ago
i definitely want to ship connector libraries that are 64-bit compatible very
soon -
the libraries should already be 64-bit compatible other than the compiler flags
(as
you found out), but i havent personally been able to test and verify this since
i
dont have a 64-bit machine.
if anyone is willing to run the tests described in this post
(http://groups.google.com/group/growl-for-windows/browse_thread/thread/82e608959
9e90584/3045a6126cd801dc?lnk=gst&q=64-bit#3045a6126cd801dc)
and confirm that everything is working, i will release the connector libraries
compiled as AnyCPU so they work in 32-bit and 64-bit environments.
Original comment by briandun...@gmail.com
on 10 Aug 2009 at 11:08
We are using the Growl SDK in CruiseControl.NET to enable Growl notifications
from
CCTray. With your assemblies the following exception occured (sorry for the
german)
on a Win2k8/64bit machine that is running our CI build. Same on a 64bit client.
System.BadImageFormatException : Die Datei oder Assembly "Growl.Connector,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=980c2339411be384" oder eine
Abhängigkeit davon wurde nicht gefunden. Es wurde versucht, eine Datei mit
einem
falschen Format zu laden.
After i rebuilt the connector without the optimization for 32bit it works. I
don't
have a 64bit box myself, otherwise i would run your test app and report the
results,
but they should be the same...
Original comment by dhom...@gmail.com
on 11 Aug 2009 at 12:27
i have updated the .NET library to be compiled for AnyCPU instead of x86 based
on
your feedback. please try out the updated assemblies and let me know if it
resolves
the issue -
http://www.growlforwindows.com/gfw/d.ashx?f=connectors/Growl_NET_Connector_SDK.z
ip
Original comment by briandun...@gmail.com
on 13 Aug 2009 at 12:09
I committed your updated libraries and our 64 bit CI box doesn't complain
anymore. I
think this issue can be resolved. Thanks for your quick fix!
Original comment by dhom...@gmail.com
on 13 Aug 2009 at 5:56
resolved.
Original comment by briandun...@gmail.com
on 13 Aug 2009 at 6:15
Original issue reported on code.google.com by
dhom...@gmail.com
on 10 Aug 2009 at 7:41