Greg I did use Reflector to get the policy XML file out of the resources - but I didn't see that notice! I will take another look in a few days. Does the restriction apply, when you and I are using it for internal use (and I have the Microsoft utility still installed)?
Of course the DLL itself could be used alone, once registered (with regsvr32), and that would not be fair perhaps. I did find that the Tag names used within the Policy file are a bit peculiar, so it does take some work to make this approach suitable for my photos. I will have a go at TagLib# again, sometime. _____ Ian Thomas Victoria Park, Western Australia From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Monday, December 31, 2012 8:34 AM To: ozDotNet Subject: Re: Image Exif updating TagLibCSharp is convenient* - and I think I did post here about that, in the past 1-2 months - Ah yes, I remember that, and I had a look at it and was impressed by the number of formats it supported. I was only looking at the audio formats and neglected those that must be implemented as EXIF data. I'll have a fresh look with a fresh mind. Ten years ago I nearly died of exhaustion writing an ID3 tag processor, and I'd be happy now to replace my code with a general purpose one. but something that I have used (and might appeal to you) is to extend Microsoft's free Photo Tools v2.2 in the way that this article <http://www.codeproject.com/Articles/43266/Reading-and-Writing-Photo-Metadat a-Programmaticall> shows (very simple use of its DLL). Nice! We can hijack the functionality of the app's libraries. Dexter did abmirable detective work. However I did notice this in reflector: [assembly: AssemblyTitle("PhotoToolboxFoundation Obfuscated with Dotfuscator Professional Pre-build license. Illegal to use on software for general release.")] Cheers, Greg
