Partager via

  • Article

Classe TaskUILifetimeHintAttribute

Defines a task lifetime attribute that specifies how expensive a user interface is to re-create.

Espace de noms :  Microsoft.SqlServer.Dts.Runtime.Design
Assembly :  Microsoft.SqlServer.Dts.Design (dans Microsoft.SqlServer.Dts.Design.dll)

Syntaxe

'Déclaration
<AttributeUsageAttribute(AttributeTargets.Class, AllowMultiple := False)> _
Public NotInheritable Class TaskUILifetimeHintAttribute _
    Inherits Attribute
'Utilisation
Dim instance As TaskUILifetimeHintAttribute

[AttributeUsageAttribute(AttributeTargets.Class, AllowMultiple = false)]
public sealed class TaskUILifetimeHintAttribute : Attribute

[AttributeUsageAttribute(AttributeTargets::Class, AllowMultiple = false)]
public ref class TaskUILifetimeHintAttribute sealed : public Attribute

[<SealedAttribute>]
[<AttributeUsageAttribute(AttributeTargets.Class, AllowMultiple = false)>]
type TaskUILifetimeHintAttribute =  
    class
        inherit Attribute
    end

public final class TaskUILifetimeHintAttribute extends Attribute

Notes

In Integration Services, this attribute allows you to specify how expensive it is to recreate a specific user interface. For example, if a user interface displays a drop-down list with only five fields, all obtained from the local computer, the user interface may be fairly fast and inexpensive to process. However, if a drop-down list in a user interface contains information that was gathered from a remote server, or from across a network that was slow, the user interface may be expensive and time-consuming to re-create. To keep the user interface in memory until the package designer is closed, set the TaskUILifetimeHint property to RecreationExpensive. To dispose of the user interface as soon as the user closes the dialog, set the TaskUILifetimeHint property to RecreationInexpensive.

Hiérarchie d'héritage

System. . :: . .Object
  System. . :: . .Attribute
    Microsoft.SqlServer.Dts.Runtime.Design..::..TaskUILifetimeHintAttribute

Sécurité des threads

Tous les membres publics static (Shared dans Visual Basic) de ce type sont thread-safe. Il n'est pas garanti que les membres d'instance soient thread-safe.