Your best bet is to use GDI+ in your application, then you can save as jpg, etc. I have a number of articles on GDI+ here on CP. Christian Graus - Microsoft MVP - C++

I think passing one of the two will solve the problem. very good Sincerely, Max Pastchenko

Try Google groups there's some dicussions. http://groups.google.co.za/groups?q=%22Virtual%20Dispatching%22%20C%23[^] xacc-ide 0.0.15 now with C#, MSIL, C, XML, ASP.NET, Nemerle, MyXaml and HLSL coloring - Screenshots

This is quite helpful. Thank you Sincerely, Max Pastchenko

Better validation check to simply validate values on text cahnged event Sincerely, Max Pastchenko

I found out that it is not pissible. I guess a solution would be simple storing that region and diplaying it long with paths on a bitmap. Sincerely, Max Pastchenko

That method looks very good. Our Instant C# VB to C# converter converts VB redim preserve statements to C# in-line equivalents, via something like the following example: VB: Dim YourArray() As Integer ... ReDim Preserve YourArray(i) C#: int[] YourArray; ... int[] temp = new int[i + 1]; if (YourArray != null) Array.Copy(YourArray, temp, Math.Min(YourArray.Length, temp.Length)); YourArray = temp; (we have to add 1 since VB arrays sizes are specified in terms of their upper bound, not the number of elements) David Anton www.tangiblesoftwaresolutions.com Home of: Clear VB: Cleans up outdated VB.NET code Instant C#: Converts from VB.NET to C# Instant VB: Converts from C# to VB.NET Instant J#: Converts from VB.NET to J#

I am guessing no then.:sigh: Sincerely, Max Pastchenko

In instead of having next programmer, work with GDI+ and put that constraint on him (this is a only a part of the project that will be used by someone else), I would rather contain all GDI+ in .NET thats why I am using paths (strings). So its easier for someone else, especially if not familiar with GDI+ directly to just say: LoadANDCompareMaps(bstingpath1, bstringpath2, etc) The solution to my priblem is quite simple: I was declaring my binary strings incorrectly correct syntax: BSTR bla = SysAllocString(L"C:\\temp\\TestDLL3.bmp_BGL.bmp"); Thank you Sincerely, Max Pastchenko P.S. I debugged on VB side with C++ executable and thats how I found that they were empty. And as far as i see C++ is talking to a .NET DLL which is created by VB.NET

problem solved. Every time VB builds a project, a .tlb is created (privided COM Interop option is chosen) This tlb is linked with a C++ project that uses .DLL. So when I already have a .tlb and decide to rebuild my VB DLL project a tlb is basically recreated. The solution i found for myself is to rebuild my DLL project after closing C++ project and then opening C++ project again. Of course initializing COM is another thing that needs to be done to properly use DLL Sincerely, Max Pastchenko

mpastchenko wrote: An example you would useful. See here. "One must learn from the bite of the fire to leave it alone." - Native American Proverb