Hi Tomas,<br><br>I don't remember what the exact problem was, however the situation remains the same, namely:<br><br>1. We can compile gdal either for x86 or x64. The x86 version could work natively with the x86 version on the .NET framework and the x64 compilation would work with the x64 version of the framework.<br>
2. If the host process is developed by you, then you should use the /platform:x86 compiler optionand use the gdal x86 compilation. This setting will provide to force your application to run on x86 mode regardless of the environment which will work pretty well on each platform then.<br>
3. <a href="http://ASP.NET">ASP.NET</a> application running on a Win64 OS use the x64 framework by default, therfore you'll have to use the Win64 compiled gdal binaries. However this is not the case when running the same application in the VS debugger since the debugger host process is running in x86 mode by default.<br>
<br>Best regards,<br><br>Tamas<br><br><br><br><br><br><div class="gmail_quote">2009/3/6 Tomas R <span dir="ltr"><<a href="mailto:monshi@home.se">monshi@home.se</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tamas, remember the detective work done last year.<br>
<br>
32 bit C# interface won't mix at all with 64 bit runtime environment. or have you found a way around that? have not followed the list for some time, just now trying to create a 64-bit version of gdal.<br>
<br>
Yes, I have a problem too, and yes a q has been posted on this list.<br>
<br>
/Tomas<br>
<br>
Tamas Szekeres skrev:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
You should provide further info about your environment:<br>
<br>
1. Did you test your app by running from an IDE like VS2005 for example?<br>
2. What version of OS/IIS you intend to use when deploying the application.<br>
<br>
You appdir and platform configuration (32/64) may be different depending on your environment.<br>
For example by using the VS IDE you'd probably use WebDev.WebServer.exe as the host process which is running against the 32 bit version of the .NET framework on a 64 bit machine.<br>
<br>
You might want to use SysInternals ProcMon.exe to make sure about the expected locations of the dll files.<br>
<br>
Best regards,<br>
<br>
Tamas<br>
<br>
<br>
<br>
<br></div>
2009/2/12 Tri <<a href="mailto:rsosnowski@cableone.net" target="_blank">rsosnowski@cableone.net</a> <mailto:<a href="mailto:rsosnowski@cableone.net" target="_blank">rsosnowski@cableone.net</a>>><div class="im">
<br>
<br>
<br>
Tamas,<br>
<br>
I'm creating web services. This is first go on 64 bit machine -<br>
plenty of<br>
32 bit web services to fall back on. The problem is I was using<br>
FDO which<br>
as far as I know has only 32 bit compiled code. So I set the<br>
'Enable 32 Bit<br>
Application' to true, published the application, then tried to run<br>
from<br>
localhost. There were no problems with 64 bit, 32 bit conflicts<br>
this way.<br>
However, I then started getting an error that says:<br>
<br>
System.IO file not found. I'm not using System.IO file in the<br>
web service.<br>
<br>
So, I thought I would use your compiled 64 bit GDAL / OGR code to<br>
create a<br>
new web service, but running into previously mentioned problem<br>
taking this<br>
approach.<br>
<br>
Thanks again.....<br>
<br>
<br>
<br>
<br>
<br>
<br>
Tamas Szekeres wrote:<br>
><br>
> What kind of application you develop Console/WinForms/<a href="http://ASP.NET" target="_blank">ASP.NET</a><br></div>
<<a href="http://ASP.NET" target="_blank">http://ASP.NET</a>> ?<div class="im"><br>
> Wouldn't it be sufficient to use 32 bit binaries and compile<br>
your app with<br>
> the /platform:x86 option?<br>
><br>
> Best regards,<br>
><br>
> Tamas<br>
><br>
><br>
><br>
><br>
> 2009/2/12 Tri <<a href="mailto:rsosnowski@cableone.net" target="_blank">rsosnowski@cableone.net</a><br></div>
<mailto:<a href="mailto:rsosnowski@cableone.net" target="_blank">rsosnowski@cableone.net</a>>><div><div></div><div class="h5"><br>
><br>
>><br>
>> Hi Tamas and others - thanks for the help.<br>
>><br>
>> By application executing directory - I've copied the files to<br>
both the<br>
>> bin<br>
>> directory under the project and the obj, Debug directory under the<br>
>> project.<br>
>> When I run the application in debug mode, the same problem occurs:<br>
>><br>
>> System.TypeInitializationException: The type initializer for<br>
>> OSGeo.OGR.Ogr<br>
>> threw an exception<br>
>><br>
>> InnerException: The type initializer for OSGeo.OGR.OgrPINVOKE<br>
threw an<br>
>> excpetion<br>
>><br>
>> I am using the 64 bit compiled code from you on Vista 64 bit<br>
machine.<br>
>><br>
>> Any more ideas? Thanks.....<br>
>><br>
>><br>
>><br>
>> Tamas Szekeres wrote:<br>
>> ><br>
>> > Hi,<br>
>> ><br>
>> > You might have to copy all of the dll-s (*_csharp.dll,<br>
*_wrap.dll,<br>
>> > gdal16.dll, proj.dll etc.) to the application executing<br>
directory.<br>
>> ><br>
>> > Best regards,<br>
>> ><br>
>> > Tamas<br>
>> ><br>
>> ><br>
>> ><br>
>> > 2009/2/11 Tri <<a href="mailto:rsosnowski@cableone.net" target="_blank">rsosnowski@cableone.net</a><br></div></div>
<mailto:<a href="mailto:rsosnowski@cableone.net" target="_blank">rsosnowski@cableone.net</a>>><div class="im"><br>
>> ><br>
>> >><br>
>> >> Can't get GDAL / OGR to work with CSharp. Using the CSharp<br>
dlls, I<br>
>> keep<br>
>> >> getting exceptions like:<br>
>> >><br>
>> >> OgrPINVOKE, threw an exception.<br>
>> >><br>
>> >><br>
>> >> TO TRY TO GET TO WORK I DID:<br>
>> >> - Copied the csharp dlls into project,<br>
>> >> - Created a reference to the dlls.<br>
>> >><br>
>> >> What am I doing wrong?<br>
>> >><br>
>> >><br>
>> >> --<br>
>> >> View this message in context:<br>
>> >> <a href="http://n2.nabble.com/GDAL---CSharp-tp2308674p2308674.html" target="_blank">http://n2.nabble.com/GDAL---CSharp-tp2308674p2308674.html</a><br>
>> >> Sent from the GDAL - Dev mailing list archive at Nabble.com.<br>
>> >><br>
>> >> _______________________________________________<br>
>> >> gdal-dev mailing list<br></div>
>> >> <a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a> <mailto:<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a>><div class="im">
<br>
>> >> <a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
>> >><br>
>> ><br>
>> > _______________________________________________<br>
>> > gdal-dev mailing list<br></div>
>> > <a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a> <mailto:<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a>><div class="im">
<br>
>> > <a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
>> ><br>
>><br>
>> --<br>
>> View this message in context:<br>
>> <a href="http://n2.nabble.com/GDAL---CSharp-tp2308674p2312047.html" target="_blank">http://n2.nabble.com/GDAL---CSharp-tp2308674p2312047.html</a><br>
>> Sent from the GDAL - Dev mailing list archive at Nabble.com.<br>
>><br>
>> _______________________________________________<br>
>> gdal-dev mailing list<br></div>
>> <a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a> <mailto:<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a>><div class="im"><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
>><br>
><br>
> _______________________________________________<br>
> gdal-dev mailing list<br></div>
> <a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a> <mailto:<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a>><div class="im"><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
><br>
<br>
--<br>
View this message in context:<br>
<a href="http://n2.nabble.com/GDAL---CSharp-tp2308674p2312090.html" target="_blank">http://n2.nabble.com/GDAL---CSharp-tp2308674p2312090.html</a><br>
Sent from the GDAL - Dev mailing list archive at Nabble.com.<br>
<br>
_______________________________________________<br>
gdal-dev mailing list<br></div>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a> <mailto:<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a>><div class="im"><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
<br>
<br>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
</div></blockquote><div><div></div><div class="h5">
<br>
_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
</div></div></blockquote></div><br>