CI/CD WFP setup file using Azure Pipelines
I have successfully created a Repo on Azure Devops and a Pipeline which triggers a release every time I push to the master branch. The result of the release is an .exe file that I can download from the Artifacts explorer. If I download the release and open it, the WPF app simply runs (no install required). I'm trying to wrap my head around how this whole CI/CD process would work but I just cannot find any good examples that could help me understand the deployment process(at least for WPF apps).
What I would usually do is build a WPF App, once I'm done, I add a new project to the solution (Visual Studio Installer - Setup Project) and deliver the .msi installer to the end user (for updates I send them the latest version to install).
How can I make this process a lot more smoother using CI/CD in Azure Devops? How do I generate an actual installer? Do I use some logic in the app itself to check for the latest build in Azure? Can someone please lay out some simple steps or some good resources?
wpf continuous-integration
azure-devops continuous-deployment asked Nov 20 '18 at 22:49
iCosminiCosmin
146116
add a comment |
I have successfully created a Repo on Azure Devops and a Pipeline which triggers a release every time I push to the master branch. The result of the release is an .exe file that I can download from the Artifacts explorer. If I download the release and open it, the WPF app simply runs (no install required). I'm trying to wrap my head around how this whole CI/CD process would work but I just cannot find any good examples that could help me understand the deployment process(at least for WPF apps).
What I would usually do is build a WPF App, once I'm done, I add a new project to the solution (Visual Studio Installer - Setup Project) and deliver the .msi installer to the end user (for updates I send them the latest version to install).
How can I make this process a lot more smoother using CI/CD in Azure Devops? How do I generate an actual installer? Do I use some logic in the app itself to check for the latest build in Azure? Can someone please lay out some simple steps or some good resources?
wpf continuous-integration
azure-devops continuous-deployment asked Nov 20 '18 at 22:49
iCosminiCosmin
146116
add a comment |
I have successfully created a Repo on Azure Devops and a Pipeline which triggers a release every time I push to the master branch. The result of the release is an .exe file that I can download from the Artifacts explorer. If I download the release and open it, the WPF app simply runs (no install required). I'm trying to wrap my head around how this whole CI/CD process would work but I just cannot find any good examples that could help me understand the deployment process(at least for WPF apps).
What I would usually do is build a WPF App, once I'm done, I add a new project to the solution (Visual Studio Installer - Setup Project) and deliver the .msi installer to the end user (for updates I send them the latest version to install).
How can I make this process a lot more smoother using CI/CD in Azure Devops? How do I generate an actual installer? Do I use some logic in the app itself to check for the latest build in Azure? Can someone please lay out some simple steps or some good resources?
wpf continuous-integration
azure-devops continuous-deployment asked Nov 20 '18 at 22:49
iCosminiCosmin
146116
I have successfully created a Repo on Azure Devops and a Pipeline which triggers a release every time I push to the master branch. The result of the release is an .exe file that I can download from the Artifacts explorer. If I download the release and open it, the WPF app simply runs (no install required). I'm trying to wrap my head around how this whole CI/CD process would work but I just cannot find any good examples that could help me understand the deployment process(at least for WPF apps).
What I would usually do is build a WPF App, once I'm done, I add a new project to the solution (Visual Studio Installer - Setup Project) and deliver the .msi installer to the end user (for updates I send them the latest version to install).
How can I make this process a lot more smoother using CI/CD in Azure Devops? How do I generate an actual installer? Do I use some logic in the app itself to check for the latest build in Azure? Can someone please lay out some simple steps or some good resources?
wpf continuous-integration
azure-devops continuous-deployment wpf continuous-integration
azure-devops continuous-deployment asked Nov 20 '18 at 22:49
iCosminiCosmin
146116
asked Nov 20 '18 at 22:49
iCosminiCosmin
146116
asked Nov 20 '18 at 22:49
iCosminiCosmin
146116
asked Nov 20 '18 at 22:49
iCosminiCosmin
146116
asked Nov 20 '18 at 22:49
iCosminiCosmin
146116
146116
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You should be able to use a task like this: https://marketplace.visualstudio.com/items?itemName=dutchworkz.BuildInstaller to use the VS Installer project you have traditionally used.
This task wraps the calls to devenv that are needed to drive VS Installer to create its MSI package as it doesn't use the usual MSBuild engine to do this.
Other tools do a similar job, for example you could drive WIX or a similar tool to create the MSI package however if you are familiar with VS Installer Projects you may want to stick to this.
answered Nov 21 '18 at 0:26
Colin BColin B
2166
Sorry for the slow reply. It's a step in the right direction but I am struggling to get it to work. Do I need to configure my on build agent(on premise)? I tried it that way and I get this error:2018-11-27T17:41:13.0687513Z DEBUG: Aggregated: System.Objectdevenv.com 2018-11-27T17:41:13.4277529Z ##[error]Cannot retrieve the dynamic parameters for the cmdlet. The specified wildcard character pattern is not valid: System.Object.If I try it with the Hosted2017 Agent Pool, this is the result:##[error]Cannot find path 'D:a1sSetuprelease' because it does not exist.
– iCosmin
Nov 27 '18 at 18:16
1
Did the build create the MSI OK? i.e. does the task report success? I can't work out from this snippet what stage is failing.
– Colin B
Nov 28 '18 at 14:27
Building the solution is successful but Creating .msi file from VS Installer project fails with the above message. I tried putting the step before or after the publishing of the Artifact step and still cannot get it to work. Thank you for your support.
– iCosmin
Nov 28 '18 at 16:56
1
So this is the output from the VS Build Installer task that is failing? What inputs did you give to the task?
– Colin B
Nov 28 '18 at 18:31
Yes. that is right. Please see below:- task: dutchworkz.BuildInstaller.BuildInstaller.BuildInstaller@1 displayName: 'Create .msi file(s) from VS Installer project(s).' inputs: installTaskMode: vdproj SlnPath: 'MyProject.sln' VdprojPath: MySetupProject/MySetupProject.vdproj
– iCosmin
Nov 28 '18 at 18:43
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%2f53402766%2fci-cd-wfp-setup-file-using-azure-pipelines%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
You should be able to use a task like this: https://marketplace.visualstudio.com/items?itemName=dutchworkz.BuildInstaller to use the VS Installer project you have traditionally used.
This task wraps the calls to devenv that are needed to drive VS Installer to create its MSI package as it doesn't use the usual MSBuild engine to do this.
Other tools do a similar job, for example you could drive WIX or a similar tool to create the MSI package however if you are familiar with VS Installer Projects you may want to stick to this.
answered Nov 21 '18 at 0:26
Colin BColin B
2166
Sorry for the slow reply. It's a step in the right direction but I am struggling to get it to work. Do I need to configure my on build agent(on premise)? I tried it that way and I get this error:2018-11-27T17:41:13.0687513Z DEBUG: Aggregated: System.Objectdevenv.com 2018-11-27T17:41:13.4277529Z ##[error]Cannot retrieve the dynamic parameters for the cmdlet. The specified wildcard character pattern is not valid: System.Object.If I try it with the Hosted2017 Agent Pool, this is the result:##[error]Cannot find path 'D:a1sSetuprelease' because it does not exist.
– iCosmin
Nov 27 '18 at 18:16
1
Did the build create the MSI OK? i.e. does the task report success? I can't work out from this snippet what stage is failing.
– Colin B
Nov 28 '18 at 14:27
Building the solution is successful but Creating .msi file from VS Installer project fails with the above message. I tried putting the step before or after the publishing of the Artifact step and still cannot get it to work. Thank you for your support.
– iCosmin
Nov 28 '18 at 16:56
1
So this is the output from the VS Build Installer task that is failing? What inputs did you give to the task?
– Colin B
Nov 28 '18 at 18:31
Yes. that is right. Please see below:- task: dutchworkz.BuildInstaller.BuildInstaller.BuildInstaller@1 displayName: 'Create .msi file(s) from VS Installer project(s).' inputs: installTaskMode: vdproj SlnPath: 'MyProject.sln' VdprojPath: MySetupProject/MySetupProject.vdproj
– iCosmin
Nov 28 '18 at 18:43
add a comment |
You should be able to use a task like this: https://marketplace.visualstudio.com/items?itemName=dutchworkz.BuildInstaller to use the VS Installer project you have traditionally used.
This task wraps the calls to devenv that are needed to drive VS Installer to create its MSI package as it doesn't use the usual MSBuild engine to do this.
Other tools do a similar job, for example you could drive WIX or a similar tool to create the MSI package however if you are familiar with VS Installer Projects you may want to stick to this.
answered Nov 21 '18 at 0:26
Colin BColin B
2166
Sorry for the slow reply. It's a step in the right direction but I am struggling to get it to work. Do I need to configure my on build agent(on premise)? I tried it that way and I get this error:2018-11-27T17:41:13.0687513Z DEBUG: Aggregated: System.Objectdevenv.com 2018-11-27T17:41:13.4277529Z ##[error]Cannot retrieve the dynamic parameters for the cmdlet. The specified wildcard character pattern is not valid: System.Object.If I try it with the Hosted2017 Agent Pool, this is the result:##[error]Cannot find path 'D:a1sSetuprelease' because it does not exist.
– iCosmin
Nov 27 '18 at 18:16
1
Did the build create the MSI OK? i.e. does the task report success? I can't work out from this snippet what stage is failing.
– Colin B
Nov 28 '18 at 14:27
Building the solution is successful but Creating .msi file from VS Installer project fails with the above message. I tried putting the step before or after the publishing of the Artifact step and still cannot get it to work. Thank you for your support.
– iCosmin
Nov 28 '18 at 16:56
1
So this is the output from the VS Build Installer task that is failing? What inputs did you give to the task?
– Colin B
Nov 28 '18 at 18:31
Yes. that is right. Please see below:- task: dutchworkz.BuildInstaller.BuildInstaller.BuildInstaller@1 displayName: 'Create .msi file(s) from VS Installer project(s).' inputs: installTaskMode: vdproj SlnPath: 'MyProject.sln' VdprojPath: MySetupProject/MySetupProject.vdproj
– iCosmin
Nov 28 '18 at 18:43
add a comment |
You should be able to use a task like this: https://marketplace.visualstudio.com/items?itemName=dutchworkz.BuildInstaller to use the VS Installer project you have traditionally used.
This task wraps the calls to devenv that are needed to drive VS Installer to create its MSI package as it doesn't use the usual MSBuild engine to do this.
Other tools do a similar job, for example you could drive WIX or a similar tool to create the MSI package however if you are familiar with VS Installer Projects you may want to stick to this.
answered Nov 21 '18 at 0:26
Colin BColin B
2166
You should be able to use a task like this: https://marketplace.visualstudio.com/items?itemName=dutchworkz.BuildInstaller to use the VS Installer project you have traditionally used.
This task wraps the calls to devenv that are needed to drive VS Installer to create its MSI package as it doesn't use the usual MSBuild engine to do this.
Other tools do a similar job, for example you could drive WIX or a similar tool to create the MSI package however if you are familiar with VS Installer Projects you may want to stick to this.
answered Nov 21 '18 at 0:26
Colin BColin B
2166
answered Nov 21 '18 at 0:26
Colin BColin B
2166
answered Nov 21 '18 at 0:26
Colin BColin B
2166
answered Nov 21 '18 at 0:26
Colin BColin B
2166
2166
Sorry for the slow reply. It's a step in the right direction but I am struggling to get it to work. Do I need to configure my on build agent(on premise)? I tried it that way and I get this error:2018-11-27T17:41:13.0687513Z DEBUG: Aggregated: System.Objectdevenv.com 2018-11-27T17:41:13.4277529Z ##[error]Cannot retrieve the dynamic parameters for the cmdlet. The specified wildcard character pattern is not valid: System.Object.If I try it with the Hosted2017 Agent Pool, this is the result:##[error]Cannot find path 'D:a1sSetuprelease' because it does not exist.
– iCosmin
Nov 27 '18 at 18:16
1
Did the build create the MSI OK? i.e. does the task report success? I can't work out from this snippet what stage is failing.
– Colin B
Nov 28 '18 at 14:27
Building the solution is successful but Creating .msi file from VS Installer project fails with the above message. I tried putting the step before or after the publishing of the Artifact step and still cannot get it to work. Thank you for your support.
– iCosmin
Nov 28 '18 at 16:56
1
So this is the output from the VS Build Installer task that is failing? What inputs did you give to the task?
– Colin B
Nov 28 '18 at 18:31
Yes. that is right. Please see below:- task: dutchworkz.BuildInstaller.BuildInstaller.BuildInstaller@1 displayName: 'Create .msi file(s) from VS Installer project(s).' inputs: installTaskMode: vdproj SlnPath: 'MyProject.sln' VdprojPath: MySetupProject/MySetupProject.vdproj
– iCosmin
Nov 28 '18 at 18:43
add a comment |
Sorry for the slow reply. It's a step in the right direction but I am struggling to get it to work. Do I need to configure my on build agent(on premise)? I tried it that way and I get this error:2018-11-27T17:41:13.0687513Z DEBUG: Aggregated: System.Objectdevenv.com 2018-11-27T17:41:13.4277529Z ##[error]Cannot retrieve the dynamic parameters for the cmdlet. The specified wildcard character pattern is not valid: System.Object.If I try it with the Hosted2017 Agent Pool, this is the result:##[error]Cannot find path 'D:a1sSetuprelease' because it does not exist.
– iCosmin
Nov 27 '18 at 18:16
1
Did the build create the MSI OK? i.e. does the task report success? I can't work out from this snippet what stage is failing.
– Colin B
Nov 28 '18 at 14:27
Building the solution is successful but Creating .msi file from VS Installer project fails with the above message. I tried putting the step before or after the publishing of the Artifact step and still cannot get it to work. Thank you for your support.
– iCosmin
Nov 28 '18 at 16:56
1
So this is the output from the VS Build Installer task that is failing? What inputs did you give to the task?
– Colin B
Nov 28 '18 at 18:31
Yes. that is right. Please see below:- task: dutchworkz.BuildInstaller.BuildInstaller.BuildInstaller@1 displayName: 'Create .msi file(s) from VS Installer project(s).' inputs: installTaskMode: vdproj SlnPath: 'MyProject.sln' VdprojPath: MySetupProject/MySetupProject.vdproj
– iCosmin
Nov 28 '18 at 18:43
Sorry for the slow reply. It's a step in the right direction but I am struggling to get it to work. Do I need to configure my on build agent(on premise)? I tried it that way and I get this error:
2018-11-27T17:41:13.0687513Z DEBUG: Aggregated: System.Objectdevenv.com 2018-11-27T17:41:13.4277529Z ##[error]Cannot retrieve the dynamic parameters for the cmdlet. The specified wildcard character pattern is not valid: System.Object. If I try it with the Hosted2017 Agent Pool, this is the result: ##[error]Cannot find path 'D:a1sSetuprelease' because it does not exist.– iCosmin
Nov 27 '18 at 18:16
Sorry for the slow reply. It's a step in the right direction but I am struggling to get it to work. Do I need to configure my on build agent(on premise)? I tried it that way and I get this error:
2018-11-27T17:41:13.0687513Z DEBUG: Aggregated: System.Objectdevenv.com 2018-11-27T17:41:13.4277529Z ##[error]Cannot retrieve the dynamic parameters for the cmdlet. The specified wildcard character pattern is not valid: System.Object. If I try it with the Hosted2017 Agent Pool, this is the result: ##[error]Cannot find path 'D:a1sSetuprelease' because it does not exist.– iCosmin
Nov 27 '18 at 18:16
1
1
Did the build create the MSI OK? i.e. does the task report success? I can't work out from this snippet what stage is failing.
– Colin B
Nov 28 '18 at 14:27
Did the build create the MSI OK? i.e. does the task report success? I can't work out from this snippet what stage is failing.
– Colin B
Nov 28 '18 at 14:27
Building the solution is successful but Creating .msi file from VS Installer project fails with the above message. I tried putting the step before or after the publishing of the Artifact step and still cannot get it to work. Thank you for your support.
– iCosmin
Nov 28 '18 at 16:56
Building the solution is successful but Creating .msi file from VS Installer project fails with the above message. I tried putting the step before or after the publishing of the Artifact step and still cannot get it to work. Thank you for your support.
– iCosmin
Nov 28 '18 at 16:56
1
1
So this is the output from the VS Build Installer task that is failing? What inputs did you give to the task?
– Colin B
Nov 28 '18 at 18:31
So this is the output from the VS Build Installer task that is failing? What inputs did you give to the task?
– Colin B
Nov 28 '18 at 18:31
Yes. that is right. Please see below:
- task: dutchworkz.BuildInstaller.BuildInstaller.BuildInstaller@1 displayName: 'Create .msi file(s) from VS Installer project(s).' inputs: installTaskMode: vdproj SlnPath: 'MyProject.sln' VdprojPath: MySetupProject/MySetupProject.vdproj– iCosmin
Nov 28 '18 at 18:43
Yes. that is right. Please see below:
- task: dutchworkz.BuildInstaller.BuildInstaller.BuildInstaller@1 displayName: 'Create .msi file(s) from VS Installer project(s).' inputs: installTaskMode: vdproj SlnPath: 'MyProject.sln' VdprojPath: MySetupProject/MySetupProject.vdproj– iCosmin
Nov 28 '18 at 18:43
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.
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%2f53402766%2fci-cd-wfp-setup-file-using-azure-pipelines%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
