You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for some reason we are unable to add the *.vsix Extension to our Azure DevOps Server. If we try to open http://our-server/_gallery/manage we get an error:
TF53001: The database operation was canceled by an administrator
So is there any other option to use MagicChunks inside a PowerShell@2 task?
I downloaded the binaries to our build agent and I do the following:
This gives me an exception in my pipeline:
File or assembly "file:///C:\MagicChunks-1.3.1\MagicChunks.dll" or a dependency of it not found ...
If I execute it on build agents powershell directly, I get even more information:
Transforming file C:\buildagent_work\16\s\docker-compose.yml
Format-MagicChunks : File transformation error: Type[MagicChunks.Core.TransformationCollection] not found ... check if assembly has been loaded ...
From my understanding Import-Module should load everything?
The text was updated successfully, but these errors were encountered:
Hi,
for some reason we are unable to add the *.vsix Extension to our Azure DevOps Server. If we try to open http://our-server/_gallery/manage we get an error:
TF53001: The database operation was canceled by an administrator
So is there any other option to use MagicChunks inside a PowerShell@2 task?
I downloaded the binaries to our build agent and I do the following:
This gives me an exception in my pipeline:
File or assembly "file:///C:\MagicChunks-1.3.1\MagicChunks.dll" or a dependency of it not found ...
If I execute it on build agents powershell directly, I get even more information:
Transforming file C:\buildagent_work\16\s\docker-compose.yml
Format-MagicChunks : File transformation error: Type[MagicChunks.Core.TransformationCollection] not found ... check if assembly has been loaded ...
From my understanding Import-Module should load everything?
The text was updated successfully, but these errors were encountered: