Softgrid - SystemGuard
Hi,
Found this on the MS Softgrid page, well it look look like the Softgrid can communicate with COM. is there any limits for a SG app to communicat with OS components...??
COM/IPC: SystemGuard enables programs to redirect communication requests through services such as COM/ DCOM or IPC methods such as Named Pipes. This alleviates versioning problems and other conflicts at these interfaces.
/Tjabocom
Found this on the MS Softgrid page, well it look look like the Softgrid can communicate with COM. is there any limits for a SG app to communicat with OS components...??
COM/IPC: SystemGuard enables programs to redirect communication requests through services such as COM/ DCOM or IPC methods such as Named Pipes. This alleviates versioning problems and other conflicts at these interfaces.
/Tjabocom
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
kkaminsk
17 years ago
Posted by:
bkelly
17 years ago
Posted by:
kkaminsk
17 years ago
Posted by:
bkelly
17 years ago
Posted by:
SaiTech
17 years ago
I am confused how much the SG app can communicate between two SG bubbles
From MS
Side-by-Side Virtualization:
Each SoftGrid-enabled application brings down its own set of configurations and can run side-by-side without the settings conflicting with each other — or the host operating system. Despite this separation, inter-application communication with other SoftGrid applications and those installed locally is preserved, allowing for cut and paste, OLE, and all other standard operations.
Is there any one with live experionce here...
/Tjabocom
From MS
Side-by-Side Virtualization:
Each SoftGrid-enabled application brings down its own set of configurations and can run side-by-side without the settings conflicting with each other — or the host operating system. Despite this separation, inter-application communication with other SoftGrid applications and those installed locally is preserved, allowing for cut and paste, OLE, and all other standard operations.
Is there any one with live experionce here...
/Tjabocom
Posted by:
bkelly
17 years ago
One bubble cannot talk to another-- only within the bubble or with locally installed applications. If you wanted two virtualized applications to communicate via COM/DCOM/Named pipes, you would need to bundle them in the same "virtual package" (bubble).
So if you virtualize Word and you virtualize Excel separately, you could not drag excel objects into Word.
If you virtualize word and Excel together, you can drag Excel objects into Word.
On that note-- you would not want to virtualize office if you have any plug-ins. In this case, you would install office physically and then you could virtualize the plug-ins individually to sit on top. Otherwise say if you had a two plug-ins for excel, and excel was virtualized-- you would either need to include the two plug-ins in your virtual package for Excel, or make two Excel packages (one for each plug in).
Hopefully the examples help; t is understandably confusing.
So if you virtualize Word and you virtualize Excel separately, you could not drag excel objects into Word.
If you virtualize word and Excel together, you can drag Excel objects into Word.
On that note-- you would not want to virtualize office if you have any plug-ins. In this case, you would install office physically and then you could virtualize the plug-ins individually to sit on top. Otherwise say if you had a two plug-ins for excel, and excel was virtualized-- you would either need to include the two plug-ins in your virtual package for Excel, or make two Excel packages (one for each plug in).
Hopefully the examples help; t is understandably confusing.
Posted by:
turbokitty
17 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.