Comments
8 comments
-
Try a -Force here. I think that will help, but not in a place to test, and everyone in the UK is gone for the weekend. Can you check the version of SCA on your build server?
-
The TFS extension is set to use the latest version in its build.
-
Update-Module with the -Force flag gave me the same issue. Trying a -Force on the Install-Module gave me:
WARNING: The specified module 'SqlChangeAutomation' with PowerShellGetFormatVersion '2.0' isnot supported by the current version of PowerShellGet. Get the latest version of the PowerShellGet module to install this module, 'SqlChangeAutomation'.
And of course I checked PowerShellGet and I have the latest (1.6.7) -
hmm, I've asked a few people for help here. I'm not sure what's broken.
-
Unfortunately PowerShell has a tendency of loading the old version of PowerShellGet by default, even if you've got a newer version installed. To be absolutely certain, you'll need to run the following:
Import-Module PowerShellGet -MinimumVersion 1.6 -Force<br>Import-PackageProvider PowerShellGet -MinimumVersion 1.6 -Force<br><br>Install-Module SQLChangeAutomation
I'm assuming you're doing this all on a development machine to test things out by the way. The various SQL Change Automation build/release extensions have their own auto-updating mechanism to download the latest version of SQL Change Automation from PowerShellGet, which does some more complicated things to make sure that it can work without admin permissions (if you're interested in the gory details, you can look in the extension directory for the file PowerShellGallery.ps1 to see what we do).
-
Yes, I am working in the Dev environment.
I had to add the -Force and -AcceptLicense flags before I got it to work, but now I have the latest version (3.0.3.2525) installed side by side with the 3.0.2.2482 version.
-
A couple things I heard back. First, did you have a new Posh session between the provider install and the get install?
This page (https://documentation.red-gate.com/sca3/getting-started/installation/installing-powershell-components) asks for that. Also, is the new session elevated? -
Not the first attempt, no, but on subsequent attempts, I did have separate powershell sessions with elevated permissions.
Add comment
Please sign in to leave a comment.
I'm getting the following error working with the nuget package from our build server (TFS 2015):
Looking at my list of installed modules, I've got 3.0.2.2482, and it looks like there's a new version out there for 3.0.2.2525 (or something similar). I'm working my way through the steps, ensuring I have the latest version of nuget (2.8.5.208) and the latest version of PowerShellGet (1.6.7). When I get to SqlChangeAutomation, I'm getting the following:
PS C:\temp> Update-Module -Name SqlChangeAutomation
I'm assuming this is because I've got SCA installed with my Visual Studio 2017, but there's no published update in visual studio that I can see. How do I resolve this issue?