Comments
Sort by recent activity
That's surprising and disappointing. Are there plans to move this functionality into the SCA powershell scripts? A flag to indicate that the database doesn't exist yet and will be created by the scripts inside of the package? / comments
That's surprising and disappointing. Are there plans to move this functionality into the SCA powershell scripts? A flag to indicate that the database doesn't exist yet and will be created by t...
Right, so changing the authentication method doesn't make a difference. New-DatabaseReleaseArtifact always prompts me for a -Target value, and as the target database doesn't exist yet (as I'm trying to create it), it fails. So what am I doing wrong? / comments
Right, so changing the authentication method doesn't make a difference. New-DatabaseReleaseArtifact always prompts me for a -Target value, and as the target database doesn't exist yet (as I'm tryi...
I use integrated security for all connections to my local sql server. / comments
I use integrated security for all connections to my local sql server.
So....I can connect to my local SQL server on my own machine with Windows Auth just fine. The database doesn't exist as I'm trying to create it via the Nuget Package. I can try creating a sql user and setting up the $production variable that way, but I'd expect the same results. / comments
So....I can connect to my local SQL server on my own machine with Windows Auth just fine. The database doesn't exist as I'm trying to create it via the Nuget Package. I can try creating a sql use...
Not the first attempt, no, but on subsequent attempts, I did have separate powershell sessions with elevated permissions. / comments
Not the first attempt, no, but on subsequent attempts, I did have separate powershell sessions with elevated permissions.
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. / comments
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...
The TFS extension is set to use the latest version in its build. / comments
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' is not supported by the current version of PowerShellGet. Get the latest version of the PowerS hellGet module to install this module, 'SqlChangeAutomation'.
And of course I checked PowerShellGet and I have the latest (1.6.7) / comments
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' ...