VirtualizeOutOfProcessCom

[doofkopf]

Hello,

what ist this Paramter good for?

I have found the VirtualizeExternlaOutOfProcessCom in the Thinapp Help but nothing about the VirtualizeOutOfProcessCom?

THX

[pbjork]

Where did you see VirtualizeOutOfProcessCOM being mentioned?

[doofkopf]

I my Pakage.INI in the --General Purpose Parameters---

[pbjork]

That should be VirtualizeExternalOutOfProcessCOM=, to my knowledge is there no VirtualizeOutOfProcessCOM parameter..

[shrivastavaa]

>>to my knowledge is there no VirtualizeOutOfProcessCOM parameter.

That is correct, there is no VirtualizeOutOfProcessCOM. (Just verified)

[Cievo]

But line:

;VirtualizeExternalOutOfProcessCOM=0

is generated in every Package.ini file

IMHO it's misspelling and it was mentioned VirtualizeExternalOutOfProcessCOM. It's just another bug

I found in manual (page 78):

VirtualizeExternalOutOfProcessCOM

The VirtualizeExternalOutOfProcessCOM parameter controls whether out‐of‐process COM objects can
run in the virtual environment. COM objects that are external to the virtual environment always run in the
physical environment.
This parameter addressed out‐of‐process COM objects that are not part of a ThinApp package and are not
registered in the virtual registry. ThinApp sets an initial value of the VirtualizeExternalOutOfProcessCOM
parameter to run external out‐of‐process COM objects in the virtual environment to ensure that COM objects
cannot modify the host computer. If a compatibility problem exists with an external COM object running in
the virtual environment, you can create and run COM objects on the host system. To run only specific COM
objects outside of the virtual environment, you can use the ExternalCOMObjects parameter to list the CLSID
of each COM object.

Examples

You can modify the VirtualizeExternalOutOfProcessCOM parameter to run all external out‐of‐process
COM objects in the physical environment rather than the virtual environment. For example, you might use
virtual Microsoft Access 2003 to send email through a native IBM Lotus Notes session.

[BuildOptions]
VirtualizeExternalOutOfProcessCOM=0

[shrivastavaa]

I am not sure if I followed your post corerctly.

OP asked about VirtualizeOutOfProcessCom; which as Peter said does not exist.

OTOH, VirtualizeExternalOutOfProcessCOM; which you metioned in your post; is a valid package.ini option.

[Cievo]

I'm just saying that it's probably just a bug in engine which created default Package.ini file.

Have a nice day,

[shrivastavaa]

And I'll doubt that, because VirtualizeExternalOutOfProcessCOM=0, is hard coded.

Lets wait for OP to answer how he found this new noun.

[TobyFruthParson]

I realize this thread is slightly aged and possibly answered, but I have a question I think is relevant to the context.

Since VirtualizeExternalOutOfProcessCOM=0 is commented out by default in Package.ini, I assume that removing the semicolon puts the parameter in effect at the next build.

Is there a VirtualizeExternalOutOfProcessCOM=1 value, or is 0 the only value available?

[shrivastavaa]

By default it virtualize external com, so when the option is commented it is as same as VirtualizeExternalOutOfProcessCOM=1.

You can explicitly say to not virtualize external COM; when you put 0 there.

From manual,

VirtualizeExternalOutOfProcessCOM—Controls whether external out‐of‐process

COM objects are run in the virtual environment.

This option determines how to treat out‐of‐process COM objects that are not part of a

ThinApp package and not registered in the virtual registry.

By default, ThinApp executes external out‐of‐process COM objects in the virtual environment, so such COM

objects cannot modify the host PC. If you run into a compatibility issue with an external COM object running in the

virtual environment, this option can be used to allow such objects to be created by and run on the host system.

For example, this directs ThinApp to execute all external out‐of‐process COM objects

in the system context, not in the virtual environment.

[BuildOptions]

VirtualizeExternalOutOfProcessCOM=0

This instructs ThinApp to execute all external out‐of‐process COM objects in the virtual

environment (default).

[BuildOptions]

VirtualizeExternalOutOfProcessCOM=1

[TobyFruthParson]

Thanks for the shrivastavaa.

Your post is technically correct, if most of the ThinApp users out there are in the habit of quoting from page 114 of the "VMware Project North Star (Thinstall) Beta 1" PDF, and perhaps other ThinApp manuals prior to 4.6.1.

For those viewing the ThinApp 4.6.1 manual, here's what they'll see (page 78 of the PDF):

VirtualizeExternalOutOfProcessCOM

The VirtualizeExternalOutOfProcessCOM parameter controls whether out-of-process COM objects can run in the virtual environment. COM objects that are external to the virtual environment always run in the physical environment.

This parameter addressed out-of-process COM objects that are not part of a ThinApp package and are not registered in the virtual registry. ThinApp sets an initial value of the VirtualizeExternalOutOfProcessCOM parameter to run external out-of-process COM objects in the virtual environment to ensure that COM objects cannot modify the host computer. If a compatibility problem exists with an external COM object running in the virtual environment, you can create and run COM objects on the host system. To run only specific COM objects outside of the virtual environment, you can use the ExternalCOMObjects parameter to list the CLSID of each COM object.

Examples

You can modify the VirtualizeExternalOutOfProcessCOM parameter to run all external out-of-process COM objects in the physical environment rather than the virtual environment. For example, you might use virtual Microsoft Access 2003 to send email through a native IBM Lotus Notes session.

[BuildOptions]
VirtualizeExternalOutOfProcessCOM=0

For those using the ThinApp 4.7 documentation, you won't find mention of this switch in the main manual.  Instead, you'll have to go to the "ThinApp Package.INI Parameters Reference Guide - ThinApp 4.7."  Again, in that guide, you will not see the parameter listed with an "=1" in any example.

[shrivastavaa]

So sarcastic! are we?

I do not understand where you got confused between manuals  considering they both say same thing.

From my post:

"

From manual,

VirtualizeExternalOutOfProcessCOM—Controls whether external out‐of‐process

COM objects are run in the virtual environment.

This option determines how to treat out‐of‐process COM objects that are not part of a

ThinApp package and not registered in the virtual registry.

By default, ThinApp executes external out‐of‐process COM objects in the virtual environment, so such COM

objects cannot modify the host PC. If you run into a compatibility issue with an external COM object running in the

virtual environment, this option can be used to allow such objects to be created by and run on the host system

"

From your post

"

The VirtualizeExternalOutOfProcessCOM parameter controls whether out-of-process COM objects can run in the virtual environment. COM objects that are external to the virtual environment always run in the physical environment.

This parameter addressed out-of-process COM objects that are not part of a ThinApp package and are not registered in the virtual registry. ThinApp sets an initial value of the VirtualizeExternalOutOfProcessCOM parameter to run external out-of-process COM objects in the virtual environment to ensure that COM objects cannot modify the host computer. If a compatibility problem exists with an external COM object running in the virtual environment, you can create and run COM objects on the host system

"

They both say that ThinApp will execute external COM objects in virtual environment by default. Which can be changed using this option.

Regarding why 1 is not mentioned; well the code assumes its 1 if the option is commented; so specifying this as 1 is as same as commenting it. Which means you are are just suppose to uncomment it if you want to run external COM outside of bubble. Else you can specify 1 or beeter keep it commented.