Update Microsoft.SqlServer.Management.IntegrationServices.dll to recent version, current version is for SQL 2016

Tool name
Microsoft.SqlServer.Management.IntegrationServices.dll
Tool license
Microsoft
Add or update?

[X] Add
[X] Update

Desired version
14 / 15 / 16
Approximate size
No response
Brief description of tool
Microsoft.SqlServer.Management.IntegrationServices.dll is a DLL that allows to deploy Microsoft Integration Services Projects that are a part of Azure SSIS or onPrem SQL Server.
In automation this DLL is needed to deploy SSIS projects to Azure SSIS. The process is describeed at https://learn.microsoft.com/en-us/sql/integration-services/ssis-quickstart-deploy-powershell?view=sql-server-ver16 .
Actually there are others using build agents for the same purpose, see #3186
However, so far on the build agents just very old versions for SQL server 2012, 2014 and 2016 are installed in the GAC:
8/20/2023 11:36:48 PM 184000 C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.Management.IntegrationServices\<IP_ADDRESS>__89845dcd8080cc91\Microsoft.SqlServer.Management.IntegrationServices.dll
8/20/2023 11:37:12 PM 174784 C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.Management.IntegrationServices\<IP_ADDRESS>__89845dcd8080cc91\Microsoft.SqlServer.Management.IntegrationServices.dll
8/20/2023 11:37:37 PM 210624 C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.Management.IntegrationServices\<IP_ADDRESS>__89845dcd8080cc91\Microsoft.SqlServer.Management.IntegrationServices.dll

The newer versions (SQL Server 2017 / 2019 / 2022) are installed by Visual Studio on the agents:
8/20/2023 11:33:15 PM 247200 C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\CommonExtensions\Microsoft\SSIS\140\Binn\Microsoft.SqlServer.Management.IntegrationServices.dll
8/20/2023 11:33:20 PM 251792 C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\CommonExtensions\Microsoft\SSIS\150\Binn\Microsoft.SqlServer.Management.IntegrationServices.dll
8/20/2023 11:33:27 PM 251808 C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\CommonExtensions\Microsoft\SSIS\160\Binn\Microsoft.SqlServer.Management.IntegrationServices.dll

However, they are not registered in the GAC and thus not usable from PowerShell.
URL for tool's homepage
No response
Provide a basic test case to validate the tool's functionality.
# Load the IntegrationServices assembly
$loadStatus = [System.Reflection.Assembly]::Load("Microsoft.SQLServer.Management.IntegrationServices, "+
    "Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=MSIL")

Platforms where you need the tool

[X] Azure DevOps
[ ] GitHub Actions

Runner images where you need the tool

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[X] Windows Server 2019
[X] Windows Server 2022

Can this tool be installed during the build?
I believe this is not reasonable unfortunately to my knowledge there is no installer of reasonable size to install this .
SQL Server Developer Edition seems to be the tool that installs them in the GAC.
How have those old versions arrived on the build agents?
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response

I'll take a look

@fmms ,  if I understood your request, you ask to put some DLL into GAC. Are you able to pub them into GAC on your local machine, can you please provide repro steps ?

@fmms , I've found similar report: https://michielvanwelsenaere.github.io/posts/Deploying-SSIS-packages-from-Azure-DevOps-with-a-Microsoft-hosted-agent/
After discussing this issue with the Microsoft Data Factory & SSIS product group we received the following feedback:

Hosted Agent 2017 installs SSDT for VS2017, which installs the SSIS binaries into GAC for SQL version 2016 (<IP_ADDRESS>) and before. Binaries for SQL version 2017 and above are not installed to GAC. They are installed to app-local folder in VS. If your script references to the <IP_ADDRESS> version, it should work.

I think there are reasons for Microsoft Data Factory & SSIS to put dll to app-local folder in vs.
I was able to load dll using
 Add-Type -Path 'C:\\Program Files\\Microsoft Visual Studio\\2022\\Enterprise\\Common7\\IDE\\CommonExtensions\\Microsoft\\SSIS\\160\\Binn\\Microsoft.SqlServer.Management.IntegrationServices.dll'

@ilia-shipitsin thanks for your prompt reply.
I have tried using version 13 as well -- however that is SSIS of SQL Server 2016 Which is pretty much out of standard support https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2016 .
As SSIS allows to embed script tasks I have seen nasty issues because of a mismatch of SSIS deployment and target server versions, I'd be happy not to go that route. Azure SSIS is SQL 2017 and thus they are correctly using version 14 in their code examples.
To be able to discuss this, I have created a minimal example to show the issue:
pool:
  vmImage: windows-2019

steps:
  - task: PowerShell@2
    inputs:
      targetType: 'inline'
      script: |
        $ssisVersion = 160
        $ssisdll = $(Get-ChildItem -Path "C:\Program Files (x86)\Microsoft Visual Studio\*\*\Common7\IDE\CommonExtensions\Microsoft\SSIS\$ssisVersion" `
          -Recurse -Filter 'Microsoft.SqlServer.Management.IntegrationServices.dll' `
          -ErrorAction SilentlyContinue | Select-Object -First 1 | ForEach-Object { $_.FullName })
        try {
          Write-Host "Loading $ssisdll"
          Add-Type -Path $ssisdll
        }
        catch {
            Write-Host $error[0].Exception.GetBaseException().LoaderExceptions
            Write-Host $error
            exit -1
        }
        $SSISNamespace = "Microsoft.SqlServer.Management.IntegrationServices"
        $null = New-Object $SSISNamespace".IntegrationServices" "connectionString"
        $folder = $catalog.Folders
        Write-Host $folder

For me this produces:
2023-08-28T16:48:24.3321382Z ##[section]Starting: PowerShell
2023-08-28T16:48:24.3449844Z ==============================================================================
2023-08-28T16:48:24.3450001Z Task         : PowerShell
2023-08-28T16:48:24.3450072Z Description  : Run a PowerShell script on Linux, macOS, or Windows
2023-08-28T16:48:24.3450183Z Version      : 2.226.2
2023-08-28T16:48:24.3450249Z Author       : Microsoft Corporation
2023-08-28T16:48:24.3450342Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
2023-08-28T16:48:24.3450474Z ==============================================================================
2023-08-28T16:48:25.7963557Z Generating script.
2023-08-28T16:48:25.9105523Z ========================== Starting Command Output ===========================
2023-08-28T16:48:25.9413992Z ##[command]"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a\_temp\43760467-2bca-420a-a88d-5ac14b909445.ps1'"
2023-08-28T16:48:28.8088285Z Loading C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\CommonExtensions\Microsoft\SSIS\160\Binn\Microsoft.SqlServer.Management.IntegrationServices.dll
2023-08-28T16:48:30.1997037Z System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2000943Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2001513Z
2023-08-28T16:48:30.2001850Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2002282Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2002633Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2002957Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2003442Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2003940Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2004108Z
2023-08-28T16:48:30.2004300Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2004592Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2004932Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2005238Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2005724Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2006217Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2006378Z
2023-08-28T16:48:30.2006574Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2006866Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2007203Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2007508Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2007980Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2010050Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2010213Z
2023-08-28T16:48:30.2010419Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2010710Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2011062Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2011373Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2011874Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2012383Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2012544Z
2023-08-28T16:48:30.2012736Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2013027Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2013350Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2014111Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2014585Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2015098Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2015258Z
2023-08-28T16:48:30.2015450Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2015738Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2016062Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2016382Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2016850Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2017352Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2017514Z
2023-08-28T16:48:30.2017694Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2018004Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2018330Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2018648Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2019116Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2019616Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2019776Z
2023-08-28T16:48:30.2020304Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2020613Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2020935Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2021256Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2021728Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2022234Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2022393Z
2023-08-28T16:48:30.2022572Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2023105Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2023440Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2023764Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2024234Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2024849Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2025011Z
2023-08-28T16:48:30.2025187Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2025495Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2026283Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2026767Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2027421Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2028043Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2028202Z
2023-08-28T16:48:30.2028381Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2028684Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2029006Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2029705Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2030202Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2030691Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2030871Z
2023-08-28T16:48:30.2031047Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2031334Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2031670Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2031972Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2032596Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2033082Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2033299Z
2023-08-28T16:48:30.2033480Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2034189Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2034596Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2034907Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2035394Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2035907Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2036083Z
2023-08-28T16:48:30.2036264Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2036554Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2037091Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2037394Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2037878Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2038876Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2039096Z
2023-08-28T16:48:30.2039276Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2039565Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2039912Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2040217Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2040691Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.ConnectionInfo, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2041170Z File name: 'Microsoft.SqlServer.ConnectionInfo, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2041325Z
2023-08-28T16:48:30.2041516Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2041806Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2042142Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2042446Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2042926Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2043410Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2043686Z
2023-08-28T16:48:30.2043879Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2044168Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2045580Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2045889Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2046365Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2046872Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2047037Z
2023-08-28T16:48:30.2047232Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2047800Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2048152Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2048455Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2048921Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2049592Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2049752Z
2023-08-28T16:48:30.2050079Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2050389Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2050710Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2051416Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2051961Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2053469Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2053658Z
2023-08-28T16:48:30.2055170Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2055520Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2055884Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2056358Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2056881Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2057384Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2057562Z
2023-08-28T16:48:30.2057741Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2058031Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2058369Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2059701Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2060237Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2060737Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2060924Z
2023-08-28T16:48:30.2061107Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2061399Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2061737Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2062051Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2062531Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2063016Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2063176Z
2023-08-28T16:48:30.2064483Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2065095Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2065496Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2065800Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2066294Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2066783Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2067051Z
2023-08-28T16:48:30.2067363Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2067660Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2068002Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2068307Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2069172Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2069669Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2069828Z
2023-08-28T16:48:30.2070023Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2070311Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2070763Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2071313Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2073878Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2074644Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2074805Z
2023-08-28T16:48:30.2075018Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2075314Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2075656Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2075968Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2076434Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2076944Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2077105Z
2023-08-28T16:48:30.2077300Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2077589Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2077911Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2078231Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2078768Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2079269Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2079432Z
2023-08-28T16:48:30.2079624Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2079958Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2080283Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2080601Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2081069Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2081569Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2081728Z
2023-08-28T16:48:30.2081908Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2082213Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2082535Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2082852Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2083315Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2083817Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2083975Z
2023-08-28T16:48:30.2084150Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2084458Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2084837Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2085154Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2085618Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2086122Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2086280Z
2023-08-28T16:48:30.2086454Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2086757Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2087082Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2087398Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2087863Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2089598Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2089879Z
2023-08-28T16:48:30.2090071Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2090381Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2090702Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2091028Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2091494Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2091996Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2092158Z
2023-08-28T16:48:30.2092336Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2092638Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2092960Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2093261Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2093746Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2094229Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2094404Z
2023-08-28T16:48:30.2094580Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2094869Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2095209Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2095510Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2095992Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2096538Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2096711Z
2023-08-28T16:48:30.2096885Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2097174Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2097512Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2097816Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2098294Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2098780Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2098953Z
2023-08-28T16:48:30.2099128Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2099416Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2099805Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2100105Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2100582Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2101068Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2101241Z
2023-08-28T16:48:30.2101416Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2102116Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2102465Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2102773Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2103260Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2103746Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2103909Z
2023-08-28T16:48:30.2104101Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2104390Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2104725Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2105027Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2105508Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2105992Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2106779Z
2023-08-28T16:48:30.2106982Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2107272Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2107612Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2107913Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2108377Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2108883Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2109042Z
2023-08-28T16:48:30.2109232Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2109524Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2109859Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2110161Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2110624Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2111191Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2111349Z
2023-08-28T16:48:30.2111541Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2111830Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2112155Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2112470Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2112933Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2113436Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2113595Z
2023-08-28T16:48:30.2113784Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2114072Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2114394Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2114714Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2115177Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2115674Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2115836Z
2023-08-28T16:48:30.2116011Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2116314Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2116635Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2116950Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2117472Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2117967Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2118126Z
2023-08-28T16:48:30.2118305Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2118609Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2118930Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2119248Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2119713Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2120211Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2120369Z
2023-08-28T16:48:30.2120543Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2120847Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2121221Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2121538Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2122002Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2122502Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2122661Z
2023-08-28T16:48:30.2122836Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2123139Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2123464Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2123780Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2124245Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2124745Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2124904Z
2023-08-28T16:48:30.2125079Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2125427Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2125752Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2126056Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2126536Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2127078Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2127251Z
2023-08-28T16:48:30.2127428Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2127729Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2128050Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2128350Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2128837Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2129322Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2129499Z
2023-08-28T16:48:30.2129673Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2129985Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2130321Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2130621Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2131100Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2131639Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2131814Z
2023-08-28T16:48:30.2131991Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2132282Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2132620Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2132920Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2133400Z  System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
2023-08-28T16:48:30.2133887Z File name: 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
2023-08-28T16:48:30.2134061Z
2023-08-28T16:48:30.2134236Z WRN: Assembly binding logging is turned OFF.
2023-08-28T16:48:30.2134523Z To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
2023-08-28T16:48:30.2134864Z Note: There is some performance penalty associated with assembly bind failure logging.
2023-08-28T16:48:30.2135166Z To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2023-08-28T16:48:30.2135418Z
2023-08-28T16:48:30.2135679Z Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
2023-08-28T16:48:30.3224920Z ##[error]PowerShell exited with code '1'.
2023-08-28T16:48:30.3651079Z ##[section]Finishing: PowerShell

How do I have to modify my pipeline to successfully load that library?
Thanks alot.

@fmms , I'm afraid you are knocking wrong door.
I understand your concern, however, it seems to be discussed with SQL team itself.
we just install a package to the way where it installs itself.
I'll have a look at provided output tomorrow, but I suggest you to discuss your concerns with SQL team first.

I took a look, DLL wants also Microsoft.SqlServer.Management.Sdk.Sfc.
I think we are doing something wrong by reinventing the wheel. In runner images we just install https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects by using its default installer.
No special way of loading it into Powershell should be required. The recommended way should work. If there's a documentation how to use it officially, let's have a look. If you can add DLL to Powershell on your local windows 2019, the same way should also work for runners.

that's good starting point: https://learn.microsoft.com/en-us/sql/integration-services/ssis-quickstart-deploy-powershell?view=sql-server-ver16#powershell-script
I beleive it is related to full SQL Server install. as far as I know, it is not installed on github runners (maybe we should, I'll try to find out). Most probably, full SQL Server install put those DLL to GAC and you can just load them.
Currently we install only https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects and DLLs are indeed not in GAC.

I played with those DLLs a while.... well, it is something beyond my intelligence.
PS C:\ssis\160> dir

    Directory: C:\ssis\160

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---           8/24/2023  3:56 AM         251808 Microsoft.SqlServer.Management.IntegrationServices.dll
-a---           8/24/2023  2:48 AM         523688 Microsoft.SqlServer.Management.Sdk.Sfc.dll

PS C:\ssis\160> asmspy C:\ssis\160\
Check assemblies in: C:\ssis\160\
Checking file Microsoft.SqlServer.Management.IntegrationServices.dll
Checking file Microsoft.SqlServer.Management.Sdk.Sfc.dll
Checking reference mscorlib
Checking reference Microsoft.SqlServer.Management.Sdk.Sfc
Checking reference System
Checking reference Microsoft.SqlServer.ConnectionInfo
Checking reference Microsoft.SqlServer.Diagnostics.STrace
Checking reference System.Data
Checking reference Microsoft.SqlServer.Smo
Checking reference System.Drawing
Checking reference System.Windows.Forms
Checking reference Microsoft.SqlServer.IntegrationServices.Common.ObjectModel
Checking reference System.Web
Checking reference Microsoft.SqlServer.ConnectionInfo
Checking reference System.Xml
Checking reference System.Core
Checking reference Microsoft.SqlServer.SqlClrProvider
Detailing only conflicting assembly references.
Reference: Microsoft.SqlServer.ConnectionInfo
  Microsoft.SqlServer.ConnectionInfo, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
Source: NotFound
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
  Microsoft.SqlServer.ConnectionInfo, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
Source: NotFound
    <IP_ADDRESS> by Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: Microsoft.SqlServer.Diagnostics.STrace
  Microsoft.SqlServer.Diagnostics.STrace, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
Source: NotFound
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: Microsoft.SqlServer.IntegrationServices.Common.ObjectModel
  Microsoft.SqlServer.IntegrationServices.Common.ObjectModel, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
Source: NotFound
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: Microsoft.SqlServer.Management.Sdk.Sfc
  Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
Source: NotFound
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
  Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
Source: Local, Location: C:\ssis\160\Microsoft.SqlServer.Management.Sdk.Sfc.dll

Reference: Microsoft.SqlServer.Smo
  Microsoft.SqlServer.Smo, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
Source: NotFound
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: Microsoft.SqlServer.SqlClrProvider
  Microsoft.SqlServer.SqlClrProvider, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
Source: NotFound
    <IP_ADDRESS> by Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: mscorlib
  mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089
Source: GlobalAssemblyCache, Location: C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib.dll
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
    <IP_ADDRESS> by Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: System
  System, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089
Source: GlobalAssemblyCache, Location: C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.dll
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
    <IP_ADDRESS> by Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: System.Core
  System.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089
Source: GlobalAssemblyCache, Location: C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Core.dll
    <IP_ADDRESS> by Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: System.Data
  System.Data, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089
Source: GlobalAssemblyCache, Location: C:\Windows\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Data.dll
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91
    <IP_ADDRESS> by Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: System.Drawing
  System.Drawing, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Source: GlobalAssemblyCache, Location: C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_<IP_ADDRESS>__b03f5f7f11d50a3a\System.Drawing.dll
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: System.Web
  System.Web, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Source: GlobalAssemblyCache, Location: C:\Windows\Microsoft.Net\assembly\GAC_32\System.Web\v4.0_<IP_ADDRESS>__b03f5f7f11d50a3a\System.Web.dll
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: System.Windows.Forms
  System.Windows.Forms, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089
Source: GlobalAssemblyCache, Location: C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Windows.Forms.dll
    <IP_ADDRESS> by Microsoft.SqlServer.Management.IntegrationServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

Reference: System.Xml
  System.Xml, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089
Source: GlobalAssemblyCache, Location: C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Xml.dll
    <IP_ADDRESS> by Microsoft.SqlServer.Management.Sdk.Sfc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91

PS C:\ssis\160>

there are a lot of dependencies, which I could not copy to single folder.
I'm not sure how that package that we install on runner is supposed to run with Powershell, truth is that https://learn.microsoft.com/en-us/sql/integration-services/ssis-quickstart-deploy-powershell?view=sql-server-ver16#powershell-script does not work, because it is related to full SQL installation.
we are open to any usage, if https://marketplace.visualstudio.com/items?itemName=SSIS.MicrosoftDataToolsIntegrationServices is supposed to work with Powershell, it should work from runner as well. But we do not know whether package owners support such usage or not.
what can be options

try to find some good nuget package. I've found https://www.nuget.org/packages/SQLServer.SMO.2016 , but it looks old. maybe there's no such package
installation of full SQL server (I can discuss it, no idea whether it will be approved or not)
you can try to ship all DLLs directly with your application and load it from folder

is it possible to install just SQL client part from command line ?

@ilia-shipitsin thanks. I have looked now indepth at asmspy -- thanks for that reference.
However, I am not able to find a combination of DLLs that fit together. Some are <IP_ADDRESS> though <IP_ADDRESS> is required.
I hopeed to just combine the IntegrationServices DLL with the official SMO package from https://www.nuget.org/packages/Microsoft.SqlServer.SqlManagementObjects.
However, those are <IP_ADDRESS> while Integration Services requires <IP_ADDRESS>. I even tried to go with older versions e.g. https://www.nuget.org/packages/Microsoft.SqlServer.SqlManagementObjects/150.18208.0 however, this does not fit either.
So it does not seem to be easy to execute the script form the Microsoft documentation on the Microsoft hosted build agents.
Installing SQL Server can be automated. However, I have played with that this evening as well. However, it seems the required DLLs are not added to the GAC Installing all components of SSIS from the SQL Server 2022 setup.

@ilia-shipitsin I have opned a ticket for the documentation as well. See https://github.com/MicrosoftDocs/sql-docs/issues/9286 . In case you have any chance to bring some attention to that. This would be highly appreciated.

@ilia-shipitsin thanks. I have looked now indepth at asmspy -- thanks for that reference.
However, I am not able to find a combination of DLLs that fit together. Some are <IP_ADDRESS> though <IP_ADDRESS> is required. I hopeed to just combine the IntegrationServices DLL with the official SMO package from

<IP_ADDRESS> will work, I gave up on Microsoft.SqlServer.Diagnostics.STrace.dll, some of part want <IP_ADDRESS>, while other want <IP_ADDRESS>
it is possible to achive with GAC, but I'm not sure how it supposed to work otherwise.
https://www.nuget.org/packages/Microsoft.SqlServer.SqlManagementObjects.

However, those are <IP_ADDRESS> while Integration Services requires <IP_ADDRESS>. I even tried to go with older versions e.g. https://www.nuget.org/packages/Microsoft.SqlServer.SqlManagementObjects/150.18208.0 however, this does not fit either.
So it does not seem to be easy to execute the script form the Microsoft documentation on the Microsoft hosted build agents.
Installing SQL Server can be automated. However, I have played with that this evening as well. However, it seems the required DLLs are not added to the GAC Installing all components of SSIS from the SQL Server 2022 setup.

well, I had a hope that installing SQL Server would place all stuff to GAC.
some guidance from SQL folks would be nice.

@ilia-shipitsin I have opned a ticket for the documentation as well. See MicrosoftDocs/sql-docs#9286 . In case you have any chance to bring some attention to that. This would be highly appreciated.

docs are not clear.
it is not clear what is supposed to be installed to run those commands.
if software package would have been specified there, it might be added to microsoft hosted agents

not clear what can be done on image generation side, I'll close the issue (to keep the backlog clean)
if some updates in https://github.com/MicrosoftDocs/sql-docs/issues/9286 will allow us to step further, we'll reopen it


change on readme file

I just made a change on the README file

Hello from 2024! :grinning:
I somehow didn't see this PR when you opened it, sorry. I just reworked the README file including some changes along these lines. I'll close this PR, but feel free to holler if you think the README still needs changes. Thanks!
Note: In case it's hard to follow my branch changes, I removed the "master" branch and forked it to "py2" (old files w/o a lot of changes) and "main" (updated version taking advantage of py3 features).


[MINOR][SPARKR][PYSPARK] Copy PySpark, SparkR archives to latest/

This change copies the pip / CRAN compatible source archives to latest/ during release build

cc @felixcheung @holdenk @rxin

Closing in favor of #16227


Migrate component_reads_and_writes

Migrate component_reads_and_writes for the 0.16 release. bevy uses it internally and it is deprecated.
It is being made pub(crate) in #16338. didn't work because it is used in an example. That fact makes this a 0.15 issue :)

@chescock @pcwalton @SkiFire13, I'm not immediately sure on the migration strategy here. Bevy uses this internally in a few places, and the dynamic example uses it at https://github.com/bevyengine/bevy/blob/e155fe1d86e3a21dd32832f2f1f6253593a4688f/examples/ecs/dynamic.rs#L156

Short term I think the enum approach is the best one, but long term I agree with @pcwalton that this is an abuse of Access and shouldn't be exposed like this.

How is it an abuse?  I see Access as a kind of set, and iterating the elements of a set doesn't seem any worse than asking whether it contains a given element.
I do agree that fn component_reads_and_writes(&self) -> (impl Iterator<Item = T> + '_, bool) is bad!  But I think it's bad because it leaks the implementation details of how unbounded sets are represented, and returning an enum would clean that up.

How is it an abuse? I see Access as a kind of set, and iterating the elements of a set doesn't seem any worse than asking whether it contains a given element.

I'm ok with just exposing iteration over all components included in this set. But exposing how the set is defined (i.e. by inclusion or exclusion of some element) exposes implementation details.

I do agree that fn component_reads_and_writes(&self) -> (impl Iterator<Item = T> + '_, bool) is bad! But I think it's bad because it leaks the implementation details of how unbounded sets are represented, and returning an enum would clean that up.

I don't see the difference between that function and an enum, both leak the implementation details in the same way. An enum would just be a bit more ergonomic.

#16348 provides one possible way forward. The general idea is to provide a higher level abstraction with fallibility in mind. That extra height allows the implementation details of Access to change while still providing a method that should be flexible enough to adapt.

But exposing how the set is defined (i.e. by inclusion or exclusion of some element) exposes implementation details.

Ah, is your worry that we'll introduce new kinds of infinite sets that can't be expressed that way?  Like, I can imagine a future "this reads any component that implements a specific trait" access.  (I'd consider adding those to be an API change rather than an implementation detail change, but it's a compatibility hazard either way.)
Does @bushrat011899's approach in #16348 alleviate that concern?  All infinite sets are collapsed in a single Err(UnboundedAccess) variant, which should allow any possible set to be expressed.

Ah, is your worry that we'll introduce new kinds of infinite sets that can't be expressed that way? Like, I can imagine a future "this reads any component that implements a specific trait" access. (I'd consider adding those to be an API change rather than an implementation detail change, but it's a compatibility hazard either way.)

Yes, I think there are possibilities for changes like that to Access. Backward compatibility is of course always an issue, but there are differences in how to handle a simple breaking change in the API and a fundamental change in what it exposes.

Does @bushrat011899's approach in https://github.com/bevyengine/bevy/pull/16348 alleviate that concern?

Yes, it does solve that concern, however it feels a bit limited as an API. I worry that people will always assume it won't error, or they will replace an error with empty sets etc etc.

Unfortunately the only other way I think we could resolve the unbounded-set issue would be to require the user to provide access to a reference (bounded) set (e.g., Components). Which doesn't work well with the current usage of this method.

I think it might be possible to remove the call to component_reads_and_writes() in QueryBuilder::is_dense(), which might make this easier to resolve.  See #16396 for my attempt to do so.


Importing from Modules Gallery in Automation fails with message :While importing the module, an error occurred while processing the module content.

Error importing the module MSAL.PS. Import failed with the following error: Orchestrator.Shared.AsyncModuleImport.ModuleImportException: While importing the module, an error occurred while processing the module content. Internal error message: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.. at Orchestrator.Activities.SetModuleVersion.ExecuteInternal(CodeActivityContext context, String moduleName, ModuleLanguage moduleLanguage, String pythonModuleVersion, String modulePath, Guid accountId, Guid moduleVersionId, Int64 moduleContentByteSize, String storageUri, Int32 moduleVersion) at Orchestrator.Activities.SetModuleVersion.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

Same issues here, tested in two tenants. The older version of MSAL.PS module import works, but the newest version doesn't

Can confirm this. Manually importing it did not work either.

I needed the module in my Azure Automation, so I ran this to save the older MSAL.PS module, then zip it, and import this older version to Azure Automation. The new version doesn't work.
Save-Module -Name MSAL.PS -MaximumVersion <IP_ADDRESS> C:\Temp

Thanks @sandytsang, that worked for me.

Same issue here. There are other modules having dependencies on MSAL.PS as well that fails because of the this same issue. Importing from Azure Automation or clicking "Deploy to Azure Automation" in PSGallery gives the same error inside Azure Automation on the latest version.

This is the output from the deployment direct from PSGallery:

Thanks for reporting this. I will take a look. You can also download preview releases here: https://github.com/AzureAD/MSAL.PS/releases

The bug should be fixed in the latest release. Thanks!
https://github.com/AzureAD/MSAL.PS/releases/tag/v<IP_ADDRESS>


Background Music (BGM) Fails to Resume After Closing Advertisements

Description
There is an issue with background music (BGM) not resuming correctly after closing advertisements in a Phaser 3 game embedded in a webview. When the app goes to the background, the BGM pauses as expected. However, when the app returns to the foreground and an advertisement (with sound) has been shown, the BGM does not resume after closing the advertisement.
Steps to Reproduce

Start the Phaser 3 game with looping background music (BGM).
Switch the app to the background, which pauses the BGM.
Return to the app, triggering an advertisement with sound to play.
Close the advertisement.
Observe that the BGM does not resume.

Expected Behavior
The BGM should resume playing after the advertisement is closed and the app returns to the foreground.
Actual Behavior
The BGM remains paused and does not resume after the advertisement is closed and the app is back in the foreground.
Additional Information

Phaser Version: [e.g., 3.55.2]
Browser: [e.g., Chrome 91, WebView]
Operating System: [e.g., Android 11, iOS 14]
Audio Context Status: The audio context is resumed correctly when the app returns to the foreground, but the BGM does not play.
Related Code Snippet:

document.addEventListener('visibilitychange', () => handleVisibilityChange(this), false);

function handleVisibilityChange(context) {
    if (document.hidden) {
        context.bgm.pause();
    } else {
        if (!isAdPlaying()) {
            context.bgm.resume();
        } else {
            onAdEnded(() => {
                context.bgm.resume();
            });
        }
    }
}

function isAdPlaying() {
    const adAudio = document.getElementById('adAudio');
    return adAudio && !adAudio.paused;
}

function onAdEnded(callback) {
    const adAudio = document.getElementById('adAudio');
    if (adAudio) {
        adAudio.addEventListener('ended', callback, { once: true });
    }
}

This issue seems to be related to the interaction between the audio contexts of the advertisement and the Phaser game. Any guidance or fixes would be greatly appreciated.
Thank you!

I suspect that Phaser failed to correctly restore the audio context, So what should we do in this situation?

Hi @cy920820, did you come to a conclusion on this?


add ontology mapping notebook to tutorials preview

Description of feature
Doesn't show up yet

Because RTD failed


Date is converted to some unknown number

This is the first time I am using this module.I am having a excel file which contains date format column as this (DD/MM/YYYY) but after conversion to json,this date changed to some number - 42912.
26/6/2017   changed to 42912.
What could be the issue ?

This is excel's internal storage format for dates. From cpearson:

Excel stores dates and times as a number representing the number of days since 1900-Jan-0, plus a fractional portion of a 24 hour day: ddddd.tttttt . This is called a serial date, or serial date-time. The integer portion of the number, ddddd, represents the number of days since 1900-Jan-0.

http://www.cpearson.com/excel/datetime.htm

Excuse me, how to solve this?


Default "Up to major version" dependency rule in Xcode incompatible with Pow's 0.X versioning

Xcode's "up to major version" dependency by default is 1.0.0 < 2.0.0 which seems to conflict with Pow's 0.3.0 versioning.

Hey @warpling, it seems like this problem is on Xcode’s side. Semantically there's nothing wrong with versioning a library in the 0.x.x range, the number is generally reserved for pre-release versions. I can understand from Xcode's side why they choose to assume that libraries are 1.0.0 and higher, but it still seems like they should handle pre-release libraries more gracefully.
The good news is that we just released version 1.0.0, so this won't be a problem going forward regardless and I feel safe closing this issue out. 🙂


Renames exits to withdraw requests all over the code

Depends on https://github.com/lightclient/7002asm/pull/7, decided to put this change aside as renaming is quite big in terms of the diff.
EIP-7002 is extended to support not only full exits but also partial withdrawals, thus, exit should be replaced with a more general term. Withdraw requests is the term used by the EIP-7251 CL spec.

given that we are multiplexing multiple operations on top of the one EL message, it may be better to use an even more general term like OperationRequest
esp if we end up with 7251 EL-init'd consolidation messages, this may end up a bit overloaded so a more general name is better

given that we are multiplexing multiple operations on top of the one EL message, it may be better to use an even more general term like OperationRequest
esp if we end up with 7251 EL-init'd consolidation messages, this may end up a bit overloaded so a more general name is better

I don’t think we will have any other EL activated operation as a part of 7002. If we end up introducing EL triggered consolidations or anything else after 7002 this will rather be another EIP with its own terms and data structs.


Consider storing fully qualified parse trees instead of queries

In pipeline_query.
This should allow us to re-create objects during binary upgrades without preserving OIDs, which would probably be a good simplification.
Currently it seems like things like UDFs within a CQ's target list could reference nonexistent functions after a binary upgrade, as functions don't get consistent OIDs across binary upgrades...

I think you may need both. When renaming objects, the OIDs are what help the query planner look up the correct objects (since they remain the same). If you don't store the OIDs, then renaming objects becomes a lot more tricky--may potentially involve rewriting all queries in pipeline_query.


No navigator key in latest prerelease of auto_route

In the latest prerelease of auto_route there is no way to pass in a navigator key which I believe is essential to be able to use the navigation service. What should I do in order to be able to navigate without context?

@Reprevise I haven't worked on the pre-release, that sounds worrying. I'll check this out today and see if I can find a workaround for you.

@Reprevise I haven't worked on the pre-release, that sounds worrying. I'll check this out today and see if I can find a workaround for you.

yeah that's a pretty drastic change. I'll have to spend some more time figuring out how use it together with Get.

yeah that's a pretty drastic change. I'll have to spend some more time figuring out how use it together with Get.

yeah that's a pretty drastic change. I'll have to spend some more time figuring out how use it together with Get.

Any updates?

yeah that's a pretty drastic change. I'll have to spend some more time figuring out how use it together with Get.

Any updates?

No @Reprevise I spoke to the author of Auto_route. I'll publish a new package using the old version under stacked_routing. I'm not going to switch the implementation of the current navigation just yet. At the moment I would not use the latest pre-release. I'll be keeping the api consistent with the version at 0.6.6 and add navigator 2.0 features if required into the generator as well. We use it mostly as a generator, he's trying to make it its own navigation service that requires the context.

No @Reprevise I spoke to the author of Auto_route. I'll publish a new package using the old version under stacked_routing. I'm not going to switch the implementation of the current navigation just yet. At the moment I would not use the latest pre-release. I'll be keeping the api consistent with the version at 0.6.6 and add navigator 2.0 features if required into the generator as well. We use it mostly as a generator, he's trying to make it its own navigation service that requires the context.

After talking to the author of the package we will fork the version at 0.6.6 and publishing our own stacked router_package which provides the same functionality. We're still determining a date of when we can start working on that package.

This functionality has been merged into stacked through the new StackedApp annotation and generation functionality


Nuget package

Hello,
READ.ME looks broken.
1.)
There is no image on the top.

2.)
Which nuget is the right one?

Stats are linked to: https://www.nuget.org/packages/Tatum/1.2.0?_src=template
Link is for the nuget: https://www.nuget.org/packages/TatumCS/

C# SDK v2 is out - closing all the issues for v1 cause they are not relevant any more.


A way to bypass the cache and pull in updated data from Reddit?

I may have overlooked something, but is there a straightforward way to re-query Reddit and pull in new data?
Consider:
> submission.comments
Out[197]: []

> submission.add_comment('test')
Out[198]: <reddit.objects.Comment at 0x4823730>

> submission.comments
Out[199]: []

Note that the data in submission.comments is outdated.

Has this been removed? I always get this error AttributeError: 'Subreddit' object has no attribute 'refresh', i have the latest praw version.


Use kvstore in LSP to optimize startup performance.

Use kvstore in LSP to optimize startup performance. When LSP starts up, it has to parse and hash every file in the project. This cost currently dominates startup time on large projects.
With this change, when --cache-dir and --lsp are supplied to Sorbet, Sorbet will store the following on disk in the kvstore immediately after initialization:

The same contents as the CLI version (parsed ASTs and GlobalState).
Hashes for files

Sorbet does not touch the cache-dir for the rest of execution.
LSP is compatible with the CLI's kvstore, so the same --cache-dir can be supplied to both LSP and CLI modes. The extra hashes are stored in keys that are uniquely used only in LSP mode.
The implementation involved changing KeyValueStore so that it's possible to transfer ownership between threads, which is necessary to support kvstore interactions in realmain and LSPIndexer. Specifically:

All access to KeyValueStore must be mediated via an OwnedKeyValueStore.
OwnedKeyValueStore can be downgraded (via disown) to a KeyValueStore.
Downgrading will either commit pending changes to disk or discard them, depending on the parameters passed to disown. The act of downgrading consumes the OwnedKeyValueStore which prevents footguns.

The end result of this optimization: A huge decrease in startup latency for Sorbet LSP (an order of magnitude decrease) when the project is cached on disk.
Motivation

Mainly, to speed up LSP initialization!
Sorbet's CLI supports caching ASTs on disk with --cache-dir, and earlier today I landed logic for also serializing hashes for files. It made sense to connect this logic with LSP when --cache-dir is supplied.
Test plan

One thing that worries me: kvstore doesn't seem to be tested! I manually tested these changes, but they should be carefully reviewed. Perhaps it's time to write a simple test suite?

I guess kvstore is tested in some CLI tests that use --cache-dir?

I guess kvstore is tested in some CLI tests that use --cache-dir?

yes, but better tests are welcome

There is now a unit test suite for KeyValueStore, and end-to-end tests for LSP's usage of KeyValueStore.


why does "capturing" an image of a VM in Azure prevent the VM from being used anymore?

Capturing an image in Azure Portal, whether sharing to a gallery or as a managed image, should warn customers regarding the VM going to deallocated and later to useless status.
This is neither documented on Azure docs:
https://learn.microsoft.com/en-us/azure/virtual-machines/capture-image-resource
https://learn.microsoft.com/en-us/azure/virtual-machines/capture-image-portal
It would make sense to keep the VM as is, in case further modifications such as installing new patches are required, to capture a new image instead of having to create another VM to update the image.
But the minimum is to warn customer when capturing the image in Azure Portal.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 3dfa7214-78bc-d8d9-bd29-8d465465e106
Version Independent ID: 349d0c58-4fd9-5009-9f2b-f81761f733e9
Content: Capture an image of a VM using the portal - Azure Virtual Machines
Content Source: articles/virtual-machines/capture-image-portal.md
Service: virtual-machines
Sub-service: imaging
GitHub Login: @cynthn
Microsoft Alias: cynthn

In fact, there is misleading information in Azure Portal when creating a manage image (legacy)
On the "Automatically delete this virtual machine after creating the image" informational link it states the following:
"If you generalize the virtual machine, no further actions on it are allowed. For example, a generalized virtual machine can't be started or modified. You can select this checkbox to have the virtual machine deleted automatically once the image is created. If you do not generalize the virtual machine, you can continue to use it as normal."
The VM is generalized as part of capturing the image without any option to not to do it.

@cynthn
Can you look into above issue and add your feedback.

Thank you for your feedback! First, I want to address this: "The VM is generalized as part of capturing the image without any option to not to do it." This isn't really the case because the platform doesn't generalize anything. Generalizing a VM can be done before creating an image, but it is always done by the user. If the user created a generalized image, the VM is marked as generalized on the platform, which makes it so it can't be restarted. I'm not clear why the platform won't let the VM be restarted, my assumption is that it might cause collisions between the VMs, even if the VM was properly generalized.
The message for "Automatically delete this VM...." option is there for both gallery and legacy images. You can create gallery images of VMs that haven't been generalized (which we tend to call "specialized") which is why it talks about being able to boot a VM that wasn't generalized.
You are correct that both of the articles you mention need to have a warning about not being able to restart a generalized VM. I've added that and filed PRs for the changes.
Please let me know if I didn't answer your question! And, thank you for taking the time to give feedback in the documentation :)


Backend- Program/Tasks Report-Screen-Admin-App- Sprint

https://github.com/ALCOpenSource/Mentor-Management-System-Team-6/issues/21
Generate Program Report
Generate Tasks Report

Kindly provide more context on the Program report


Ask you a question about Watchface

In your watchface file, I see a lot of property definitions. What exactly do the definitions of these properties mean? I didn't find any relevant documentation from Apple developer website, where have you seen how to define watchface files?

There is no official information from Apple. That is the reason I analyze the format and then I published as WatchFaceDumper, an OSS project. Moreover, watchfaces have different data structures although they share a common structures roughly. Photos, kaleidoscope, whistler-analog and Portrait (#3) are the only face types I already analyzed. Other face types needs to be analyzed.


fix(Types): make Body.json() method generic

What is the purpose of this pull request?

[ ] Documentation update
[ ] Bug fix
[ ] New feature
[x] Other, please explain:

Makes the json method generic. This will allow users to tell tsc the return type of the method. It's opt-in, which means if no type is provided, the return type will remain unknown
What changes did you make?
Turned BodyMixin#json into a generic method.
const a = await res.json(); // 'a' is unknown

interface User {
 name: string;
}
const b = await res.json<User>(); // 'b' is of type User

Which issue (if any) does this pull request address?
Lack of IntelliSense due to return type of json being unknown. It still defaults to unknown but the user can opt-in by providing a return type for the method.

Closing this because using generics this way isn't preferred. See Common Mistakes


Use a 5.10 kernel version that supports live patching

Adds scripts/kernel.sh which sets the kernel to 5.10 with packer.
NOTE: needs rebasing, should be adding 1 commit to #2

Not needed in EKS 1.24+


fix(forkJoin): test for object literal

Description:
This PR fixes a problem with forkJoin's inspection of its first argument to determine whether or not it should be joining the properties of an object literal.
The current code checks to see if the argument is not an Observable and if it isn't, it proceeds as if it has been called with an object literal. However. the argument could be another ObservableInput - like a Promise.
This PR adds a failing test and changes the check to compare the argument's prototype to Object.prototype.
Related issue (if exists): #4737

Pull Request Test Coverage Report for Build 8421

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.2%) to 96.658%

Files with Coverage Reduction
New Missed Lines
%

src/internal/Subscriber.ts
1
81.48%

src/internal/OuterSubscriber.ts
1
50.0%

Totals

Change from base Build 8414:
-0.2%

Covered Lines:
5206

Relevant Lines:
5386

💛  - Coveralls


Allow Selection of Shapes from Drawing Layer(s)

It has been requested that users be able to choose a shape they have previously drawn from the selection layer.
This involves, drawing the shape on a 'sketch' layer and then using it inside of tools like the 'Select Features' service.

@klassenjs - This is part one, part two is to enable it in the mapbook...
<config>...
<param name="services.tools.select_feature">true</param>
...</config>

Doc'd.


Incorrect Warning Banner

As of November 22nd the Microsoft Graph CLI is no longer in preview and is now generally available. I recommend removing the warning on this page stating that it is still in preview.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 3be63768-c95c-f1f5-8d77-f40688637448
Version Independent ID: 3be63768-c95c-f1f5-8d77-f40688637448
Content: Install the Microsoft Graph command-line interface (CLI) - Microsoft Graph
Content Source: concepts/cli/installation.md
Product: non-product-specific
Technology: microsoft-graph
GitHub Login: @jasonjoh
Microsoft Alias: MSGraphDocsVteam

Thanks for reporting! A fix for this will be published today.


this.camera.capture() returning file name / uri not image binary

Steps to reproduce

Include code from example.
Press the capture button - firing this.camera.capture()
The data when logged is not an image binary, instead it appears to be a uri of the form: assets-library://asset/asset.JPG?id=0126412B-2B92-4F90-BB7B-CB00000A0000&ext=JPG
From here there are two options:

A) Send the 'data' to the server as an image binary - this fails because it's not an image binary
B) Include the photo uri in an object and send that as form data to the server - this also fails
render function includes:

            <Camera
              ref={(cam) => {
                this.camera = cam;
              }}
              style={localStyles.preview}
              aspect={Camera.constants.Aspect.fill}
              flashMode={Camera.constants.FlashMode.auto}
              captureAudio={false}>
              <View style = {localStyles.captureBtnContainer}>
                <Text
                  style={localStyles.captureBtn}
                  onPress={this.takePicture.bind(this)}>
                  Capture
                </Text>
              </View>
            </Camera>

When the capture button is pressed, the takePicture method is fired - and on success the image should be sent to my server.
 takePicture() {
    this.camera.capture()
      .then((data) => {
        this.setState({'photoUri' : data})
        var uploadUrl = this.state.uploadUrl;

        var photo = {
          uri: data,
          type: 'image/jpeg',
          name: 'photo.jpg',
        };

        var uploadForm = new FormData()
        uploadForm.userKey = this.state.userKey;
        uploadForm.append('image', photo);
        fetch(uploadUrl, {
          method: 'POST',
          headers: {
            'Accept': 'application/json',
            'Content-Type': 'multipart/related',
          },
          body: uploadForm
        })
      .then((response) => response.text())
      .then((responseText) => {
        alert(responseText);
      })
      .catch((error) => { alert('takePicture upload: ' + error) });
      })
      .catch(err => alert('takePicture: ' + err));
  }

Expected behaviour
I expect the 'data' returned to be an image binary - but it doesn't seem to be
Actual behaviour
Instead the 'data' returned appears to be a uri for the image. This uri, however fails with a "No suitable request handler found for assets-library..."
Environment

Node.js version:5.10.0
React Native version:0.23.1
React Native platform + platform version: iOS 9.3.1 (on phone) and latest simulator (iphone 5s)

react-native-camera
Version: "master"

FYI - I used the "Mostly automatic install" as opposed to the "manual install" approach.

For anyone experiencing a similar issue I've found that setting:
captureTarget={Camera.constants.CaptureTarget.disk}
Within the  tag returns a uri usable in the way set out above.

But where the image is saved then? On iOS it's not showing in Camera roll

For anyone experiencing a similar issue I've found that setting:
captureTarget={Camera.constants.CaptureTarget.disk}
Within the tag returns a uri usable in the way set out above.
this solution doesnt work


WebUI PNG metadata import does not include LoRA (maybe not written to metadata at all?)

No it isn't written as metadata yet. Same with Vae.