Azure Devops Build SSIS task
I have created an SSIS package using VS 2017 and added the project to Azure Devops. I am trying to setup a build task in Azure Devops using the SQL Integration Service add in. Everything I am doing is setup on my machine which includes the Agent Pool etc. When trying to setup parameters for the SSIS build the Devenv Version selection only gives me 12 and 14. VS2017 doesn't appear. As a result it appears that when I do a build the incorrect version on devenv is used and the build (even though it doesn't say its failed) fails.
The version the build is using is C:Program Files (x86)Microsoft Visual Studio 14.0Common7IDEDevenv.com but should be using C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDE>Devenv.com
How do I get to DEVENV config parameter to include the Hosted VS2017 version?
The following web page gives an idea of what I am trying to achieve: -
http://chamindac.blogspot.com/2018/09/build-and-deploy-ssis-with-azure-devops.html
ssis
azure-devops azure-pipelines edited Nov 11 at 23:46
lucascaro
3,44611530
asked Nov 11 at 23:18
user1790316
11
|
show 2 more comments
I have created an SSIS package using VS 2017 and added the project to Azure Devops. I am trying to setup a build task in Azure Devops using the SQL Integration Service add in. Everything I am doing is setup on my machine which includes the Agent Pool etc. When trying to setup parameters for the SSIS build the Devenv Version selection only gives me 12 and 14. VS2017 doesn't appear. As a result it appears that when I do a build the incorrect version on devenv is used and the build (even though it doesn't say its failed) fails.
The version the build is using is C:Program Files (x86)Microsoft Visual Studio 14.0Common7IDEDevenv.com but should be using C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDE>Devenv.com
How do I get to DEVENV config parameter to include the Hosted VS2017 version?
The following web page gives an idea of what I am trying to achieve: -
http://chamindac.blogspot.com/2018/09/build-and-deploy-ssis-with-azure-devops.html
ssis
azure-devops azure-pipelines edited Nov 11 at 23:46
lucascaro
3,44611530
asked Nov 11 at 23:18
user1790316
11
Looking at our DevOps, we have a Powershell script that looks like this :&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.com" "$(Build.SourcesDirectory)SSISMySSISProject.dtproj" /rebuild $(BuildConfiguration). Not posting as an answer because I don't know if it even works.
– Nick.McDermaid
Nov 11 at 23:33
Thanks Nike. The code does run VS 2017 however, I would need to tell the build to use V2017 in the first place which I am unable to as it doesn't appear in the DEVENV Config dropdown build parameter setting. So if there is code that determines which versions of VS are available that would possibly tell me why its not finding VS2017 to populate the selection parameter for DEVENV.
– user1790316
Nov 12 at 0:09
Maybe I'm missing something but there There is no devenv config dropdown in a powershell step. It just runs a command line.
– Nick.McDermaid
Nov 12 at 0:21
The powershell step doesn't have one but the SSIS build deploy one does. I have changed it now use powershell and it builds. Unfortunately when I try to deploy now using powershell scripts I have another issue. $integrationServices = New-Object "Microsoft.SqlServer.Management.IntegrationServices.IntegrationServices" $sqlConnection New-Object : Could not load file or assembly 'Microsoft.SqlServer.Dmf.Common, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The file is in the C:Windowsassembly for that version
– user1790316
Nov 12 at 5:48
I believe we are using ISDeploymentWizard.exe to deploy rather than the SSIS API, again through powershell.
– Nick.McDermaid
Nov 12 at 6:22
|
show 2 more comments
I have created an SSIS package using VS 2017 and added the project to Azure Devops. I am trying to setup a build task in Azure Devops using the SQL Integration Service add in. Everything I am doing is setup on my machine which includes the Agent Pool etc. When trying to setup parameters for the SSIS build the Devenv Version selection only gives me 12 and 14. VS2017 doesn't appear. As a result it appears that when I do a build the incorrect version on devenv is used and the build (even though it doesn't say its failed) fails.
The version the build is using is C:Program Files (x86)Microsoft Visual Studio 14.0Common7IDEDevenv.com but should be using C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDE>Devenv.com
How do I get to DEVENV config parameter to include the Hosted VS2017 version?
The following web page gives an idea of what I am trying to achieve: -
http://chamindac.blogspot.com/2018/09/build-and-deploy-ssis-with-azure-devops.html
ssis
azure-devops azure-pipelines edited Nov 11 at 23:46
lucascaro
3,44611530
asked Nov 11 at 23:18
user1790316
11
I have created an SSIS package using VS 2017 and added the project to Azure Devops. I am trying to setup a build task in Azure Devops using the SQL Integration Service add in. Everything I am doing is setup on my machine which includes the Agent Pool etc. When trying to setup parameters for the SSIS build the Devenv Version selection only gives me 12 and 14. VS2017 doesn't appear. As a result it appears that when I do a build the incorrect version on devenv is used and the build (even though it doesn't say its failed) fails.
The version the build is using is C:Program Files (x86)Microsoft Visual Studio 14.0Common7IDEDevenv.com but should be using C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDE>Devenv.com
How do I get to DEVENV config parameter to include the Hosted VS2017 version?
The following web page gives an idea of what I am trying to achieve: -
http://chamindac.blogspot.com/2018/09/build-and-deploy-ssis-with-azure-devops.html
ssis
azure-devops azure-pipelines ssis
azure-devops azure-pipelines edited Nov 11 at 23:46
lucascaro
3,44611530
asked Nov 11 at 23:18
user1790316
11
edited Nov 11 at 23:46
lucascaro
3,44611530
asked Nov 11 at 23:18
user1790316
11
edited Nov 11 at 23:46
lucascaro
3,44611530
edited Nov 11 at 23:46
lucascaro
3,44611530
edited Nov 11 at 23:46
lucascaro
3,44611530
3,44611530
asked Nov 11 at 23:18
user1790316
11
asked Nov 11 at 23:18
user1790316
11
asked Nov 11 at 23:18
user1790316
11
11
Looking at our DevOps, we have a Powershell script that looks like this :&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.com" "$(Build.SourcesDirectory)SSISMySSISProject.dtproj" /rebuild $(BuildConfiguration). Not posting as an answer because I don't know if it even works.
– Nick.McDermaid
Nov 11 at 23:33
Thanks Nike. The code does run VS 2017 however, I would need to tell the build to use V2017 in the first place which I am unable to as it doesn't appear in the DEVENV Config dropdown build parameter setting. So if there is code that determines which versions of VS are available that would possibly tell me why its not finding VS2017 to populate the selection parameter for DEVENV.
– user1790316
Nov 12 at 0:09
Maybe I'm missing something but there There is no devenv config dropdown in a powershell step. It just runs a command line.
– Nick.McDermaid
Nov 12 at 0:21
The powershell step doesn't have one but the SSIS build deploy one does. I have changed it now use powershell and it builds. Unfortunately when I try to deploy now using powershell scripts I have another issue. $integrationServices = New-Object "Microsoft.SqlServer.Management.IntegrationServices.IntegrationServices" $sqlConnection New-Object : Could not load file or assembly 'Microsoft.SqlServer.Dmf.Common, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The file is in the C:Windowsassembly for that version
– user1790316
Nov 12 at 5:48
I believe we are using ISDeploymentWizard.exe to deploy rather than the SSIS API, again through powershell.
– Nick.McDermaid
Nov 12 at 6:22
|
show 2 more comments
Looking at our DevOps, we have a Powershell script that looks like this :&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.com" "$(Build.SourcesDirectory)SSISMySSISProject.dtproj" /rebuild $(BuildConfiguration). Not posting as an answer because I don't know if it even works.
– Nick.McDermaid
Nov 11 at 23:33
Thanks Nike. The code does run VS 2017 however, I would need to tell the build to use V2017 in the first place which I am unable to as it doesn't appear in the DEVENV Config dropdown build parameter setting. So if there is code that determines which versions of VS are available that would possibly tell me why its not finding VS2017 to populate the selection parameter for DEVENV.
– user1790316
Nov 12 at 0:09
Maybe I'm missing something but there There is no devenv config dropdown in a powershell step. It just runs a command line.
– Nick.McDermaid
Nov 12 at 0:21
The powershell step doesn't have one but the SSIS build deploy one does. I have changed it now use powershell and it builds. Unfortunately when I try to deploy now using powershell scripts I have another issue. $integrationServices = New-Object "Microsoft.SqlServer.Management.IntegrationServices.IntegrationServices" $sqlConnection New-Object : Could not load file or assembly 'Microsoft.SqlServer.Dmf.Common, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The file is in the C:Windowsassembly for that version
– user1790316
Nov 12 at 5:48
I believe we are using ISDeploymentWizard.exe to deploy rather than the SSIS API, again through powershell.
– Nick.McDermaid
Nov 12 at 6:22
Looking at our DevOps, we have a Powershell script that looks like this :
&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.com" "$(Build.SourcesDirectory)SSISMySSISProject.dtproj" /rebuild $(BuildConfiguration). Not posting as an answer because I don't know if it even works.– Nick.McDermaid
Nov 11 at 23:33
Looking at our DevOps, we have a Powershell script that looks like this :
&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.com" "$(Build.SourcesDirectory)SSISMySSISProject.dtproj" /rebuild $(BuildConfiguration). Not posting as an answer because I don't know if it even works.– Nick.McDermaid
Nov 11 at 23:33
Thanks Nike. The code does run VS 2017 however, I would need to tell the build to use V2017 in the first place which I am unable to as it doesn't appear in the DEVENV Config dropdown build parameter setting. So if there is code that determines which versions of VS are available that would possibly tell me why its not finding VS2017 to populate the selection parameter for DEVENV.
– user1790316
Nov 12 at 0:09
Thanks Nike. The code does run VS 2017 however, I would need to tell the build to use V2017 in the first place which I am unable to as it doesn't appear in the DEVENV Config dropdown build parameter setting. So if there is code that determines which versions of VS are available that would possibly tell me why its not finding VS2017 to populate the selection parameter for DEVENV.
– user1790316
Nov 12 at 0:09
Maybe I'm missing something but there There is no devenv config dropdown in a powershell step. It just runs a command line.
– Nick.McDermaid
Nov 12 at 0:21
Maybe I'm missing something but there There is no devenv config dropdown in a powershell step. It just runs a command line.
– Nick.McDermaid
Nov 12 at 0:21
The powershell step doesn't have one but the SSIS build deploy one does. I have changed it now use powershell and it builds. Unfortunately when I try to deploy now using powershell scripts I have another issue. $integrationServices = New-Object "Microsoft.SqlServer.Management.IntegrationServices.IntegrationServices" $sqlConnection New-Object : Could not load file or assembly 'Microsoft.SqlServer.Dmf.Common, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The file is in the C:Windowsassembly for that version
– user1790316
Nov 12 at 5:48
The powershell step doesn't have one but the SSIS build deploy one does. I have changed it now use powershell and it builds. Unfortunately when I try to deploy now using powershell scripts I have another issue. $integrationServices = New-Object "Microsoft.SqlServer.Management.IntegrationServices.IntegrationServices" $sqlConnection New-Object : Could not load file or assembly 'Microsoft.SqlServer.Dmf.Common, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The file is in the C:Windowsassembly for that version
– user1790316
Nov 12 at 5:48
I believe we are using ISDeploymentWizard.exe to deploy rather than the SSIS API, again through powershell.
– Nick.McDermaid
Nov 12 at 6:22
I believe we are using ISDeploymentWizard.exe to deploy rather than the SSIS API, again through powershell.
– Nick.McDermaid
Nov 12 at 6:22
|
show 2 more comments
1 Answer
1
active
oldest
votes
I ended up using a powershell script instead.
The script has one line to run the build.
&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017ProfessionalCommon7IDEdevenv.com" "C:UsersmeDownloadsvsts-agent-win-x64-2.140.0_work2sPOC_SSIS.sln" /rebuild
I place the code in a .ps1 file and put it into the root of my repo. I then used the Powershell config to reference the file and it worked.
I did a similar thing for the deployment where I used : -
ISDeploymentWizard /S /SP:C:UsersmeDownloadsvsts-agent-win-x64-2.140.0_work2sPOC_SSISbinDevelopmentPOC_SSIS.ispac /DS:serverName /DP:/SSISDB/POC_SSIS/POC_SSIS
answered Nov 16 at 3:40
user1790316
11
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254225%2fazure-devops-build-ssis-task%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I ended up using a powershell script instead.
The script has one line to run the build.
&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017ProfessionalCommon7IDEdevenv.com" "C:UsersmeDownloadsvsts-agent-win-x64-2.140.0_work2sPOC_SSIS.sln" /rebuild
I place the code in a .ps1 file and put it into the root of my repo. I then used the Powershell config to reference the file and it worked.
I did a similar thing for the deployment where I used : -
ISDeploymentWizard /S /SP:C:UsersmeDownloadsvsts-agent-win-x64-2.140.0_work2sPOC_SSISbinDevelopmentPOC_SSIS.ispac /DS:serverName /DP:/SSISDB/POC_SSIS/POC_SSIS
answered Nov 16 at 3:40
user1790316
11
add a comment |
I ended up using a powershell script instead.
The script has one line to run the build.
&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017ProfessionalCommon7IDEdevenv.com" "C:UsersmeDownloadsvsts-agent-win-x64-2.140.0_work2sPOC_SSIS.sln" /rebuild
I place the code in a .ps1 file and put it into the root of my repo. I then used the Powershell config to reference the file and it worked.
I did a similar thing for the deployment where I used : -
ISDeploymentWizard /S /SP:C:UsersmeDownloadsvsts-agent-win-x64-2.140.0_work2sPOC_SSISbinDevelopmentPOC_SSIS.ispac /DS:serverName /DP:/SSISDB/POC_SSIS/POC_SSIS
answered Nov 16 at 3:40
user1790316
11
add a comment |
I ended up using a powershell script instead.
The script has one line to run the build.
&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017ProfessionalCommon7IDEdevenv.com" "C:UsersmeDownloadsvsts-agent-win-x64-2.140.0_work2sPOC_SSIS.sln" /rebuild
I place the code in a .ps1 file and put it into the root of my repo. I then used the Powershell config to reference the file and it worked.
I did a similar thing for the deployment where I used : -
ISDeploymentWizard /S /SP:C:UsersmeDownloadsvsts-agent-win-x64-2.140.0_work2sPOC_SSISbinDevelopmentPOC_SSIS.ispac /DS:serverName /DP:/SSISDB/POC_SSIS/POC_SSIS
answered Nov 16 at 3:40
user1790316
11
I ended up using a powershell script instead.
The script has one line to run the build.
&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017ProfessionalCommon7IDEdevenv.com" "C:UsersmeDownloadsvsts-agent-win-x64-2.140.0_work2sPOC_SSIS.sln" /rebuild
I place the code in a .ps1 file and put it into the root of my repo. I then used the Powershell config to reference the file and it worked.
I did a similar thing for the deployment where I used : -
ISDeploymentWizard /S /SP:C:UsersmeDownloadsvsts-agent-win-x64-2.140.0_work2sPOC_SSISbinDevelopmentPOC_SSIS.ispac /DS:serverName /DP:/SSISDB/POC_SSIS/POC_SSIS
answered Nov 16 at 3:40
user1790316
11
answered Nov 16 at 3:40
user1790316
11
answered Nov 16 at 3:40
user1790316
11
answered Nov 16 at 3:40
user1790316
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254225%2fazure-devops-build-ssis-task%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Looking at our DevOps, we have a Powershell script that looks like this :
&"${env:ProgramFiles(x86)}Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.com" "$(Build.SourcesDirectory)SSISMySSISProject.dtproj" /rebuild $(BuildConfiguration). Not posting as an answer because I don't know if it even works.– Nick.McDermaid
Nov 11 at 23:33
Thanks Nike. The code does run VS 2017 however, I would need to tell the build to use V2017 in the first place which I am unable to as it doesn't appear in the DEVENV Config dropdown build parameter setting. So if there is code that determines which versions of VS are available that would possibly tell me why its not finding VS2017 to populate the selection parameter for DEVENV.
– user1790316
Nov 12 at 0:09
Maybe I'm missing something but there There is no devenv config dropdown in a powershell step. It just runs a command line.
– Nick.McDermaid
Nov 12 at 0:21
The powershell step doesn't have one but the SSIS build deploy one does. I have changed it now use powershell and it builds. Unfortunately when I try to deploy now using powershell scripts I have another issue. $integrationServices = New-Object "Microsoft.SqlServer.Management.IntegrationServices.IntegrationServices" $sqlConnection New-Object : Could not load file or assembly 'Microsoft.SqlServer.Dmf.Common, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The file is in the C:Windowsassembly for that version
– user1790316
Nov 12 at 5:48
I believe we are using ISDeploymentWizard.exe to deploy rather than the SSIS API, again through powershell.
– Nick.McDermaid
Nov 12 at 6:22