Hi, I managed to build root with .NET without any problems; I didn't come around testing whether linking VC6 libs within .NET works. So I have not had this problem because I've never tried it. Either way: The standard c++ lib for .NET and VC6 differ, so my assumption would be (now, it wasn't a few weeks ago) that cross linking will only work when using the backward compatible .NET std lib - which doesn't sound like a good idea, because that gives you the same buggy lib people were fighting with under VC6. As Rene might not like a public discussion on this (it's not a bug report as .NET is not supported, and .NET is so buggy that supporting it and adding 100 work-arounds won't really pay off), we should maybe migrate it to a closed forum. Valeri: Have you seen this? Did you test it? Either way, building root from sources with .NET instead of using the binary distribution for VC6 should get rid of this problem. Cheers, Axel. Heather Kelly wrote: > Hi, > > I have seen plenty of discussion concerning ROOT & Visual .Net - we are > using ROOT 3.04.02 on Windows. > It was my understanding from previous posts that one could link against > the ROOT binaries compiled with VC6. > However, we have run into trouble when compiling/linking (using Visual > .Net) our ROOT I/O classes against ROOT 3.04.02 (compiled with VC6), > specifically related to TObject::SavePrimitive: > > mcRootData.arc(McPositionHit.obj) : error LNK2001: unresolved external > symbol "public: virtual void __thiscall TObject::SavePrimitive(class > std::basic_ofstream<char,struct std::char_traits<char> > &,char const > *)" > (?SavePrimitive@TObject@@UAEXAAV?$basic_ofstream@DU?$char_traits@D@std@@@std > @@PBD@Z) > > > Clearly, others have not had this problem...is there a known cause for > this? and is there an easy fix? > > Thanks, > Heather
This archive was generated by hypermail 2b29 : Thu Jan 01 2004 - 17:50:09 MET