Killing Vault on OnStartup - When Needed

[Tiffany_Hayden_]

Hi, 

This is probably something simple that I can't seem to find. I'm looking to kill Vault in the sub for 

Public Sub OnStartup(Application AS IApplication) Implements IExplorerExtension.OnStartup

End Sub

I have some logic that checks to see if a file is up to date and runs an exe external but if it's out of date I need to kill Vault. Is this possible? 

Thank you in advance! 

Tiffany

[olegd.prod]

"Kill Vault"? Do you mean that you want to kill the process your code is running in ? AFAIK, we don't provide any suicidal APIs 😉

[Tiffany_Hayden_]

@olegd.prod haha! 😂 What I would like it to do is close down the vault that is opening up. 

Thanks for the Tuesday Morning giggles! 

[olegd.prod]

Giggle Tuesday is a thing!

Sorry for being slow, but I am still not clear about what you are trying to achieve.
The host (Vault Client) is calling your extension's OnStartup - this is where you'd typically add commands you want to show up in the Vault Client. What does "kill" mean in this context? Can you describe the desired workflow end-to-end, starting with "User logs into Vault Client"?

[Tiffany_Hayden_]

So what happens is 

User clicks on Vault icon

My extension runs and checks an exe for file updates (Onstartup Sub)

If the exe runs and the files are out of date then Vault Client closes down. 

If it everything is up to date then the Vault Client continues down the open and log in process. 

What I want is if the onstartup runs and the file is out of date that Vault Client closes and doesn't continue the startup process or login process. I'm trying to force users to run the exe by not allowing the client to actually startup. Is this possible? 

[olegd.prod]

So you do want the VC process to commit suicide. There is no Vault API for that. You can certainly choose to kill the VC process using Process.Kill, but that seems ... extreme. With that said I certainly don't fully understand your scenario, so will leave the "should I ?" to your judgement