Register-DevartTools

Synopsis

Automates the activation of a Devart product.

Description

This activation method requires an active Internet connection and the activation key. Copy your activation key from the e-mail that was sent to you after your purchase and paste it into the Key parameter.

Syntax

Register-DevartTools -Key <string> -Product <DevartTool> [<CommonParameters>]

Parameters

-Product

Specifies dbForge Studio for SQL Server as part of the -Product key to activate it.

-Product <DevartTool>
Property Default value
Required True
Position Named
Default value Studio
Accept pipeline input False
Accept wildcard characters False

-Key

Specifies your activation key.

-Key <string>
Property Default value
Required True
Position Named
Default value -
Accept pipeline input False
Accept wildcard characters False

Common parameters

<CommonParameters>

This cmdlet supports these common parameters:

  • Verbose – Provides detailed output about the command operation.
  • Debug – Provides debugging information.
  • ErrorAction – Specifies how to respond to errors.
  • ErrorVariable – Stores error messages in a variable.
  • WarningAction – Specifies how to respond to warnings.
  • WarningVariable – Stores warning messages in a variable.
  • InformationAction – Specifies how informational messages are handled.
  • InformationVariable – Stores informational messages in a variable.
  • OutBuffer – Controls the number of objects buffered before output.
  • PipelineVariable – Stores the current pipeline object in a variable.
  • OutVariable – Stores output objects in a variable.

For more information, see About Common Parameters.

Output

System.Boolean (returns true on success and false otherwise)

System.Boolean returns:

  • true if the operation was successful.
  • false if the operation failed.

Example

Register-DevartTools -Product Studio -Key ThdUH+tysSaJa9DvDYitE2wt6aq9AXZdkPqpqwnTRg+

Note

To integrate dbForge Studio into an Azure DevOps pipeline, it is crucial to configure the Azure DevOps agent service to operate under the user that installed and activated it. Additionally, it is essential to grant this user the necessary access permissions to the SQL servers involved in the continuous integration (CI) process.