Yes, it works great, thanks a lot! Regards, Andre Loker

ProcessExited only works for the main AppDomain (and even then, I find strange bevahvior to occur). Regards, Andre

While it may be annoying, it certainly isn't strange. When crossing application boundaries (including distinct AppDomains), .NET Remoting marshals the call to another context, similar in concept (regarding this discussion) to your code calling another class's code. Depending on derivation and location, the method must be public in order to call it. If you absolutely don't want to make it public, there is a way although it is difficult. You can extend RealProxy and the ProxyAttribute (with which you attribute your class that defines the handler). The RealProxy derivative can catch method calls (as well as other types), which you can use to override the default behavior so that the delegate is serialized. It's tricky, and if you're not too familiar with .NET Remoting I suggest you pick up a book like "Microsoft .NET Remoting" from MS Press[^] or "Advanced .NET Remoting" from Ingo Rammer[^]. Microsoft MVP, Visual C# My Articles

Just test 21 nested structs on VS.NET 2003 Final Beta. It compiles without any problem. Frankly, working with MC++ is sometimes frustrating. The compiler seems to be a work in progress. Consider the ff, for instance: System::String __gc* strTmp1 = String::Format(S"{0}, {1}, {2}", S"0", S"1", S"2"); System::String __gc* strTmp2 = String::Format(S"{0}, {1}, {2}, {3}", S"0", S"1", S"2", S"3"); The second strTmp2 will not compile simply because the MC++ does not have support for variable parameters, while C# and even VB.NET supports it. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.

Huh? Which version are you using? I have two c# module that I compile from the command line using /target:module, lets say part1.module and part2.module. Then I use al.exe to create a manifest for these two modules (foo.dll). If I add foo.dll to the references list (only the file foo.dll, no projects), I don't see any of the types of the modules. However, I can use the types and compile the program. I got a post in microsoft.public.dotnet.languages.csharp that this is a known limitation (or bug if you want so). It would have been *sooo* nice :( - Andre

Thats nice to kow, o well there goes my plans for a native/managed C++ assembly... ;P I rated this article 2 by mistake. It deserves more. I wanted to get to the second page... - vjedlicka 3:33 25 Nov '02

Paul Selormey wrote: I do not think it is an issue of time since it took four years of development from VC++ 6.0 release. With very little improvement in MFC, and some web-stuff updates for ATL four years was enough to do effective work. Or maybe they could only start their work after most parts of .NET framework were done. It's not the fall that kills you: it's the sudden stop - Down by Law, Jim Jamursch (1986)

Hi Paul! I solved my problems and (as you said) use the command line tools. 1. I add the resource files (resx and txt for strings) and the localized versions to the project. 2. For the neutral resource, I set resgen $(InputFileName) $(InputName).resources as the commandline and "$(InputName).resources" as the output file 3. For all localized resources I set the command line to e.g. resgen $(InputFileName) $(InputName).resources al /v:1.0.* /target:lib /embed:$(InputName).resources /culture:de /out:$(OutDir)/de/$(TargetName).resources.dll and $(OutDir)/de/$(TargetName).resources.dll as the output file to create the satelite assemblies. 4. In the project settings Linker->Input->Embed managed resource file I add strings.resource That's it, works sweetly for me, although it is not as easy as it could be. Why does MS stick to .rc/.res in VC++.net 2002? - Andre

Whoops, it seems I did not get an e-mail notification. Something's going on in here, I see. I'm short on time right now, so I cannot post the test code (maybe it was a test way too naiv at all). I'll post it when I have a little more time. Thanks already for the interesting research, Jeff! - Andre

Hi VizOne, Sorry for the late reply. VizOne wrote: But what about __value object? They are stored on stack, aren't they? Will stack object be move during collection, too? Although __value objects are typically stored on the stack, they can also be put on the heap. Stack objects are the same in .Net as they are in regular C/C++, so they won't move. How heavy would you say is pinning a pointer? Is it a real performance issue if I keep the pointer pinned only for some native calculations that won't last more then a view microseconds? I did some preliminary tests too, and I could barely measure any performance differences. I forced GC collections during them. The GC does not collect very often under normal circumstances, so I don't see pinning as costly either. Your tests jibe with mine. Of course reinterpret_cast is an evil monster, but I have to use it here, haven't I? I always do, and MC++ code that ships with .Net uses it too. I really think MS is just playing it "safe". As I recall, reinterpret_cast was just discouraged. The software world would grind to a halt if such casts were never used ;) The reinterpret_cast is safe and ok, or not? I usually call native functions from MC++ much like you do. As long as managed objects are pinned and the cast is appropriate, safety should not be of concern. Cheers

Nothing new, just re-implementing IDisposable to create the impression of a virtual method (in which case you do not have to use the "Internal" attachment) - have fun. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.

I see what you mean. Having said that, it may well be feasible to use XSLT to transform the Doxygen style XML to a more useful format. :cool: It might be worth reading up on XSLT transformations. There's a bunch of articles on MSDN - just do a search. Good luck. Anna :rose: www.annasplace.me.uk "Be yourself - not what others think you should be" - Marcia Graesch Trouble with resource IDs? Try the Resource ID Organiser Add-In for Visual C++

Someone already gave me the clue. MSDN says: "String Class. Represents an immutable series of characters." Stupid me! RTFM... - Andre