Skip to content

Microsoft.SqlServer.Management.PowerShell.SqlPowerShellSqlExecutionException: Cannot access CLR. Assembly might be in an invalid state. Try running EXEC tSQLt.EnableExternalAccess @enable = 0; or reinstalling tSQLt.  #24

@muradkhateeb78

Description

@muradkhateeb78

Hi,

I am using this extension for the first time and I am facing a few issues.

  1. Should the TSQLt installation files be the part of the build artifact, I think the extension should be have the capability to get that installation done (Prepare environment) by itself.
  2. Where should the actual unit tests be residing. How would this extension know where to look for the .sql file carrying the actual unit tests, should that file be copied in the DefaultWorkingDirectory.
  3. I am getting Microsoft.SqlServer.Management.PowerShell.SqlPowerShellSqlExecutionException: Cannot access CLR. Assembly might be in an invalid state. Try running EXEC tSQLt.EnableExternalAccess @enable = 0; or reinstalling tSQLt. when trying to run the TSQLt tests.

Having said that I am using the extension for the first time, the documentation is not that clear for the beginners. I can contribute in writing proper documentation but I need to be clear myself first.

Any help in this regard is highly appreciated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions