Serwer terminali Winflector - alternatywa dla aplikacji Zdalny Pulpit, Citrix XenApp

Forum > Product technical support > Can I call/ShellExecute an executable in the (Windows) CLIENT machine from a published application?

Autor: prs_hope
Data: 2016-03-11 12:36:27

Experts,

Can an executable be called/ShellExecuted in the (Windows) CLIENT machine from a published application?  In other words, an application that resides in the Client machine.

Of course, calling other applications to be executed at the server within the published application is no problem and happens transparently.  My question is whether via the Winflector API one could this, and also, if there is a way of finding out if X application residing at the client machine is already running... perhaps a Windows-Title via the API?

 

 
Autor: prs_hope
Data: 2016-04-05 02:13:53

This functionality is sorely needed to further enhance the options while deploying WF-virtualized apps.
Autor: Jacek (staff)
Data: 2016-04-06 13:29:08

Currently, such functionality is not directly available in Winflector user API (TApi...) library. It can be implemented by adding user-defined client-side extention DLL with the mentioned functions.

Then, functions for starting new EXE and checking if a given application is running on the client could be called by TApiSyncRPC() extention API.

 

We have put your request on our Winflector API wish-list and will try to implement direct API.
Autor: prs_hope
Data: 2016-04-08 22:29:41

Thanks for the update Jacek..!

Very much looking forward to this...

The direct implementation of that feature as function(s) of the direct Winflector API (TApi...) will be an important event - a milestone of the software.  In our case, it's critical - and we are basically on hold with the large deployment of the project until this happens.

The TApiSyncRPC() extention API route is intriguing but we have technical questions as to how to develop it.  The great advantage of a 'direct API/TApi...' method is that it is 'already there in the PC' (if it is Windows);  otherwise, our guess is that we would need to develop a COM/DLL - distribute-copy it to the local machine (via TApi...) and then, register it so that it can be available to the TApiSyncRPC() interface for the Winflector-published app. to call it.

 
Autor: prs_hope
Data: 2016-05-13 06:22:37

I think a solid implementation of this feature equals Winflector version 4.0.0.0
1


Zaloguj się aby móc pisać na forum.