Page 1 of 1

I need some suggestions on opening Everything to VBA.

Posted: Sun Oct 07, 2018 1:31 pm
by everythingsvba
I need Help
I really want Everything to be able to use it on VBA. Especially in Office2016.
As a newcomer, I am puzzled about which program should be used to develop the easiest.

Using C# to develop DLL ? or Directly use the source code in SDK to compile and generate DLL?
Or Using C++ to develop DLL is better?
Who knows a better solution?

Looking forward to giving guidance.

I would appreciate any help from this forum, and after generating this DLL, I would like to take the time to compile a guide on VBA.

Now that I've generated an Everythinghelp. DLL with C++ and implemented only a few important functions. It seems that it is not stable enough through so many different language . I look forward to your suggestions and joining.

Re: I need some suggestions on opening Everything to VBA.

Posted: Mon Oct 08, 2018 6:35 pm
by NotNull
If you just want to kick off Everything.exe, hyou could use a simple call shell("everything.exe" "params").
Everything has *a lot* of command-line parameters to make it do whatever you want.

If you want to programmatically interact with (a running) Everything.exe, you would need one or more COM objects. Everything doesn't have those, sorry.

Alternative: use AutoIt/AutoHotKey.

(But I probably misinterpreted your question. What exactly do you want to accomplish?)

Re: I need some suggestions on opening Everything to VBA.

Posted: Wed Oct 10, 2018 7:13 am
by void
Using the Everything SDK with the provided DLLs would be my recommendation.

Please find an Everything SDK Visual Basic example here:
Everything.SDK.Visual.Basic.Example.zip

/support/everything/sdk/