[Help] Linking C++ DLL and Visual Basic Executable Together - Page 3 - MPGH

Raydenman · 2015-08-31T08:36:10.000Z

[QUOTE=ლ(ಠ_ಠლ);10904792] Oh you got to be kidding me..[/QUOTE] Hey why should I "Kidding" you?

Originally Posted by user590177

Oh you got to be kidding me..

Hey why should I "Kidding" you?

I understand now on the logic but I don't know how should I write the code. Mind just adding a short of example to me? Im lost.

Most, if not all you guys really are just giving pieces of information or wrong information all-together.

1.) To do inter-process communication between applications, you can use either sockets or use a named pipe.
2.) To do the above, you will need to establish a protocol for doing that. ( Well not necessarily but I recommend it. )
3.) VB.NET requires PInvoke ( Platform invocations ) to use any native APIs. ( CreateNamedPipe, FindWindow, OpenProcess etc. )
4.) If you MUST use VB to inject your application ( Which is the worst idea since the creation of the internet ) and want to attempt to keep your application hidden, I'd recommend you stream it directly from a server using either SSL or directly using your own protocol. Following that, use a custom DLL that you can inject into the application that receives the streamed DLL and manually maps it into the process. ( Or just manually map it from the VB application but note that someone could just apply system call hooks ( NtWriteVirtualMemory etc. ) and dump your file that way. )

Originally Posted by Hitokiri~

1.) To do inter-process communication between applications, you can use either sockets or use a named pipe.
2.) To do the above, you will need to establish a protocol for doing that. ( Well not necessarily but I recommend it. )
3.) VB.NET requires PInvoke ( Platform invocations ) to use any native APIs. ( CreateNamedPipe, FindWindow, OpenProcess etc. )
4.) If you MUST use VB to inject your application ( Which is the worst idea since the creation of the internet ) and want to attempt to keep your application hidden, I'd recommend you stream it directly from a server using either SSL or directly using your own protocol. Following that, use a custom DLL that you can inject into the application that receives the streamed DLL and manually maps it into the process. ( Or just manually map it from the VB application but note that someone could just apply system call hooks ( NtWriteVirtualMemory etc. ) and dump your file that way. )

I love this girl and his skills

Originally Posted by Hitokiri~

1.) To do inter-process communication between applications, you can use either sockets or use a named pipe

There are many methods, this is one of them.
But, I said another ...
Use RegisterWindowsMessage using an unique ID string << it gives you an unique window message number.
Then, just broadcast on this number; don't forget to make all recipients send back their hWnds or make all recipients reply.
Then use SendMessage ...
Also, as you said you can still use a named pipe.
In .net managed classes there is only a solution to IPC is remoting.

Originally Posted by Hitokiri~

3.) VB.NET requires PInvoke ( Platform invocations ) to use any native APIs. ( CreateNamedPipe, FindWindow, OpenProcess etc. )

As already I said ...

Originally Posted by Raydenman

You must use DllImport actually to call a native function in vb.net.
Anyway, P/Invoke calls LoadLibrary on native dll.

Ok, if i wanted to stream it from a server / website how can I do this? I don't understand. Use a custom dll and stream the dll? Manual mapping? Can I have a source for manual mapping dlls? And I want to learn more about IPC. I don't mind if my app is not hidden and I want to learn to use native APIs like those you have mentioned. (Both on c++ and vb.net)

Originally Posted by Raydenman

Then use SendMessage ...

Was listing the fastest methods. SendMessage() has a higher IRQL than named pipes/socks

- - - Updated - - -