View previous topic :: View next topic |
Author |
Message |
Freakazoid
Joined: 13 Jan 2009 Posts: 4
|
Posted: Tue Jan 13, 2009 9:28 pm Post subject: Pdfsharp.dll and XP 64-bit |
|
|
how is pdfsharp.dll compiled? i'm running into problems with a program of mine crashing on a 64-bit machine. The problem seems to stem from my program being compiled as "any cpu" and it trying to load a 32-bit DLL from a program that's being ran as 64-bit, hence it going *crunch*
The problem is that I can't change my program to be compiled as 32-bit only because i'm using an express edition.
Basically: is it possible to get a version of PdfSharp.dll that'll work on 32-bit and 64-bit systems (compiled as "any cpu") or do .net compiled DLLs not work that way? |
|
Back to top |
|
 |
Thomas Hoevel

Joined: 16 Oct 2006 Posts: 387 Location: Cologne, Germany
|
Posted: Wed Jan 14, 2009 10:58 am Post subject: |
|
|
AFAIK PDFsharp is compiled as "any CPU", but it uses some PInvokes.
Flagging your app as x86 would solve the issue (but you can't do it in your GUI).
I dunno if it would help to flag PDFsharp as x86.
But I read that you can add
Quote: | <PlatformTarget>x86</PlatformTarget> |
to your project file directly.
The compiler is part of .NET and it's not crippled, they only crippled the GUI. Maybe that helps. _________________ Regards
Thomas Hoevel
PDFsharp Team |
|
Back to top |
|
 |
Freakazoid
Joined: 13 Jan 2009 Posts: 4
|
Posted: Wed Jan 14, 2009 7:55 pm Post subject: |
|
|
Thomas Hoevel wrote: | AFAIK PDFsharp is compiled as "any CPU", but it uses some PInvokes.
Flagging your app as x86 would solve the issue (but you can't do it in your GUI).
I dunno if it would help to flag PDFsharp as x86.
But I read that you can add
Quote: | <PlatformTarget>x86</PlatformTarget> |
to your project file directly.
The compiler is part of .NET and it's not crippled, they only crippled the GUI. Maybe that helps. |
ya, after much work and downloading the .net 2.0 SDK I managed to get my app compiled as x86 but things still went *crunch*.
going to try and recompile PdfSharp as x86 to match it and have to re-compile my program again with it as it's expecting v1.0.
unrelated but i'll ask it anyway: is there a way to make it so a .net (2.0) app doesn't need a recompile if there's been a new dll version dropped in place? |
|
Back to top |
|
 |
Freakazoid
Joined: 13 Jan 2009 Posts: 4
|
Posted: Wed Jan 14, 2009 8:44 pm Post subject: |
|
|
Freakazoid wrote: |
ya, after much work and downloading the .net 2.0 SDK I managed to get my app compiled as x86 but things still went *crunch*.
going to try and recompile PdfSharp as x86 to match it and have to re-compile my program again with it as it's expecting v1.0. |
ok, i'm confused. Compiled x86 specific versions of both the pdfsharp dll and my program. Program still goes *crunch* and the app is still showing up as a 64-bit app in task manager when it runs. (no *32 after it) |
|
Back to top |
|
 |
Freakazoid
Joined: 13 Jan 2009 Posts: 4
|
Posted: Wed Jan 14, 2009 9:42 pm Post subject: |
|
|
Freakazoid wrote: |
ok, i'm confused. Compiled x86 specific versions of both the pdfsharp dll and my program. Program still goes *crunch* and the app is still showing up as a 64-bit app in task manager when it runs. (no *32 after it) |
HAH! I win. found a way to absolutely force a .net 2.0 app to load as 32-bit, app works now. Used corflags to do such: http://msdn.microsoft.com/en-us/library/ms164699(VS.80).aspx |
|
Back to top |
|
 |
|