Diego, I will update the C# readme with this manifest embedding stuff, thanks for the feedback.
I guess that some of the dependent libraries have been compiled with previous versions of Visual Sudio. You might want to select the libraries really needed to run your application and compile them using VS2005. Howard Butler's buildkit is the best option to have all of the sources to compile. By editing mapserver/nmake.opt you should enable only those libraries that are really used. It must be noted that using different compilers may cause that the modules have different CRT heaps and may result in heap corruption if the memory allocation and deallocation of the same segment occurs in different modules. I hope this situation may occur rarely by now. Compilation of some of the libraries with VS2005 may be a big fun ;) As far as I know the buildkit was originally compiled with VS2003 and the ms4w installation was released based on theese binaries. Tamas Diego Riofrio <[EMAIL PROTECTED]> írta: > Tamas, > > I did what you say about the dlls of mapscript in C#, I added the manifest > with mt /manifest mapscript.dll.manifest /outputresource:mapscript.dll;#2, > and it worked very well. I realized that some things are fixed, like draw > line witch didn't work with the other version. > > I only have a problem while working on development ambient the dlls don't > work in a computer with only Visual .Net 2005 installed, they also need > Visual .Net 2003 installed. I don't know why but if Visual .Net 2005 is only > installed an exception of mapscriptPINVOKE is thrown: "Unable to load dll ' > mapscript.dll'". I haven't tested the application on a deployment ambient > yet, but I will do it in a few days. > > I'm very grateful with your help. > > Best Regards, > Diego Riofrío > _______________________________________________________________________________ A legjobb akciós utazások oldala, ahol most rengeteg nyeremény vár Rád: http://ad.adverticum.net/b/cl,1,6022,99401,161631/click.prm
