Microsoft KB Archive/246625: Difference between revisions

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 44: Line 44:
== SUMMARY ==
== SUMMARY ==


When attempting to configure an interface as Queued in the COM+ Component Services snap-in in Windows 2000, you might find that the option to do so is disabled. This can be because the interface has [out] or "ByRef" parameters, Property Get methods, or has functions that have return values.
When attempting to configure an interface as Queued in the COM+ Component Services snap-in in Windows 2000, you might find that the option to do so is disabled. This can be because the interface has [out] or "ByRef" parameters, Property Get methods, or has functions that have return values.


</div>
</div>
Line 51: Line 51:
== MORE INFORMATION ==
== MORE INFORMATION ==


Queued Components allow for method calls to be stored, queued, and executed later when the object is available. Since the information flow is one-way, interfaces which have either Functions , Property Get, or &quot;ByRef&quot; parameters cannot be marked as Queued.<br />
Queued Components allow for method calls to be stored, queued, and executed later when the object is available. Since the information flow is one-way, interfaces which have either Functions , Property Get, or "ByRef" parameters cannot be marked as Queued.<br />
<br />
<br />
Please note that Visual Basic marks function parameters as &quot;ByRef&quot; by default that is, if neither &quot;ByRef&quot; or &quot;ByVal&quot; is specified. The parameter will be &quot;ByRef&quot;; thus invalidating queuing for the interface.
Please note that Visual Basic marks function parameters as "ByRef" by default that is, if neither "ByRef" or "ByVal" is specified. The parameter will be "ByRef"; thus invalidating queuing for the interface.


</div>
</div>

Latest revision as of 13:50, 21 July 2020

Knowledge Base


INFO: Only Write-Only interfaces Can be Marked as Queued in COM+

Article ID: 246625

Article Last Modified on 1/26/2006



APPLIES TO

  • Microsoft COM+ 1.0



This article was previously published under Q246625

SUMMARY

When attempting to configure an interface as Queued in the COM+ Component Services snap-in in Windows 2000, you might find that the option to do so is disabled. This can be because the interface has [out] or "ByRef" parameters, Property Get methods, or has functions that have return values.

MORE INFORMATION

Queued Components allow for method calls to be stored, queued, and executed later when the object is available. Since the information flow is one-way, interfaces which have either Functions , Property Get, or "ByRef" parameters cannot be marked as Queued.

Please note that Visual Basic marks function parameters as "ByRef" by default that is, if neither "ByRef" or "ByVal" is specified. The parameter will be "ByRef"; thus invalidating queuing for the interface.


Additional query words: Queued Component Services COM+ Queue QC

Keywords: kbinfo kbcomplusqc KB246625