AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2004.09.16 17:04 "[Tiff] libtiff and .net", by Kabongo, Kalonji
2004.09.16 17:09 "Re: [Tiff] libtiff and .net", by Bob Friesenhahn
2004.09.16 17:23 "RE: [Tiff] libtiff and .net", by Kabongo, Kalonji
2004.09.16 17:35 "RE: [Tiff] libtiff and .net", by Bob Friesenhahn
2004.09.16 17:44 "RE: [Tiff] libtiff and .net", by Kabongo, Kalonji
2004.09.16 18:16 "RE: [Tiff] libtiff and .net", by Bob Friesenhahn
2004.09.16 17:59 "RE: [Tiff] libtiff and .net", by Bill Bither
2004.09.20 19:48 "RE: [Tiff] libtiff and .net", by Bob Friesenhahn
2004.09.22 03:52 "RE: [Tiff] libtiff and .net", by Bill Bither
2004.09.22 04:13 "RE: [Tiff] libtiff and .net", by Bob Friesenhahn

2004.09.16 17:59 "RE: [Tiff] libtiff and .net", by Bill Bither

I don't think it really makes sense to port LibTIFF to 100% managed .NET code. The better approach would be to use PInvoke from .NET to call the compiled LibTIFF library functions and create your own objects based on that, or use an existing 3rd party .NET component that's based on LibTIFF (check my signature for more info there).

Also, MS Visual Studio 2005, currently in beta, allows for compiling unmanaged code into managed assemblies using C++. This would be the ultimate solution as it takes advantage of both managed usability and the .NET Framework with unmanaged performance and memory management.

Best Regards,
Bill Bither
http://www.atalasoft.com/

-----Original Message-----

From: tiff-bounces@remotesensing.org [mailto:tiff-bounces@remotesensing.org] On Behalf Of Bob Friesenhahn

Sent: Thursday, September 16, 2004 1:10 PM

To: Kabongo, Kalonji (DET)
Cc: 'tiff@remotesensing.org'
Subject: Re: [Tiff] libtiff and .net

On Thu, 16 Sep 2004, Kabongo, Kalonji (DET) wrote:

Are there plans to port the libtiff library to the .net platform?

What do you mean by porting to the .net platform?

It should already be possible to compile libtiff as .net "managed" MSIL code using Visual Studio .net. That doesn't mean that it will become platform independent though since libtiff uses native APIs.