Hi Tamas,<br><br>Just got the latest GDAL from SVN and built the C# wrappers. They appear to be strongly named now. Thanks for the quick turnaround!<br><br>Jason<br><br><div class="gmail_quote">On Jan 31, 2008 6:43 PM, Tamas Szekeres <<a href="mailto:szekerest@gmail.com">szekerest@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Added the strong name support in SVN trunk r13646<br>We are using a fixed keyfile that won't change among the releases.<br>
gdal.snk have also been added to the repository.<br>The keyfile is referenced by AssemblyInfo.cs that might be deprecated<br>by the further Visual Studio releases. However this is the only way to<br>support the strongnames for all of the platforms right now.<br>
<div><div></div><div class="Wj3C7c"><br>Best regards,<br><br>Tamas<br><br>2008/1/31, Jason Beverage <<a href="mailto:jasonbeverage@gmail.com">jasonbeverage@gmail.com</a>>:<br>> Thanks Tamas. It's so much nicer to just be able to download a working<br>
> binary than having to compile and configure everything yourself.<br>><br>> Thanks!<br>><br>> Jason<br>><br>><br>> On Jan 31, 2008 3:03 PM, Tamas Szekeres <<a href="mailto:szekerest@gmail.com">szekerest@gmail.com</a>> wrote:<br>
><br>> > Jason,<br>> ><br>> > Please file a ticket for this issue, I'll take care of this.<br>> > The /keyfile compiler option is quite VS2005 specific, however I think<br>> > we have alternative options to achieve the same results which is<br>
> > compiler neutral.<br>> ><br>> > Best regards,<br>> ><br>> > Tamas<br>> ><br>> ><br>> ><br>> ><br>> > 2008/1/31, Jason Beverage <<a href="mailto:jasonbeverage@gmail.com">jasonbeverage@gmail.com</a>>:<br>
> ><br>> ><br>> ><br>> > > Hi all,<br>> > ><br>> > > I've been using the C# wrappers that come with FWTools, and I noticed<br>> that<br>> > > they are not strongly named. This is causing a problem for my project<br>
> as we<br>> > > require everything to be strongly named.<br>> > ><br>> > > I noticed that the <a href="http://makefile.vc" target="_blank">makefile.vc</a> has a "sign" step that generates the<br>
> gdal.snk<br>> > > file, but it is not used after that.<br>> > ><br>> > > If you change the gdal_csharp target to include the /keyfile argument,<br>> it<br>> > > should produce strongly named assemblies:<br>
> > > $(CSC) /debug:full /keyfile:gdal.snk /target:library /out:ogr_csharp.dll<br>> > > ogr\*.cs<br>> > > $(CSC) /debug:full /keyfile:gdal.snk /target:library<br>> /out:gdal_csharp.dll<br>> > > gdal\*.cs<br>
> > > $(CSC) /debug:full /keyfile:gdal.snk /target:library<br>> > > /out:gdalconst_csharp.dll const\*.cs<br>> > > $(CSC) /debug:full /keyfile:gdal.snk /target:library /out:osr_csharp.dll<br>> > > osr\*.cs<br>
> > ><br>> > > It would be great if the bindings that come from the FWTools distro<br>> become<br>> > > the "official" way to download the binaries and they are signed when we<br>> get<br>
> > > them.<br>> > ><br>> > > Thanks!<br>> > ><br>> > > Jason<br>> > ><br>> > > _______________________________________________<br>> > > gdal-dev mailing list<br>
> > > <a href="mailto:gdal-dev@lists.osgeo.org">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>
> > ><br>> ><br>><br>><br></div></div></blockquote></div><br>