How do I set the default install path with a windows installer?
How do I set the default install path when deploying a program using a windows installer.
c# installer windows-installer
edited Jan 18 '12 at 20:47
ThinkingStiff
57.4k27131228
asked Nov 15 '11 at 15:01
user589195user589195
1,777104075
add a comment |
How do I set the default install path when deploying a program using a windows installer.
c# installer windows-installer
edited Jan 18 '12 at 20:47
ThinkingStiff
57.4k27131228
asked Nov 15 '11 at 15:01
user589195user589195
1,777104075
How depends on what technology you're using to build the installer, but yes, it will be possible to set the default install path.
– Damien_The_Unbeliever
Nov 15 '11 at 15:05
aha think i may of found the property
– user589195
Nov 15 '11 at 15:06
windows installer is a technology, part of windows, that consumes msi databases and uses those to install applications. The important technology to know about is the one that you're using to construct an MSI database - WiX, InstallShield, Visual Studio Setup Project (ugh), to name a few.
– Damien_The_Unbeliever
Nov 15 '11 at 15:09
visual studio but I think i found the property
– user589195
Nov 15 '11 at 15:09
currently set to [ProgramFilesFolder][Manufacturer][ProductName] Where is it pulling those params from?
– user589195
Nov 15 '11 at 15:10
add a comment |
How do I set the default install path when deploying a program using a windows installer.
c# installer windows-installer
edited Jan 18 '12 at 20:47
ThinkingStiff
57.4k27131228
asked Nov 15 '11 at 15:01
user589195user589195
1,777104075
How do I set the default install path when deploying a program using a windows installer.
c# installer windows-installer
c# installer windows-installer
edited Jan 18 '12 at 20:47
ThinkingStiff
57.4k27131228
asked Nov 15 '11 at 15:01
user589195user589195
1,777104075
edited Jan 18 '12 at 20:47
ThinkingStiff
57.4k27131228
asked Nov 15 '11 at 15:01
user589195user589195
1,777104075
edited Jan 18 '12 at 20:47
ThinkingStiff
57.4k27131228
edited Jan 18 '12 at 20:47
ThinkingStiff
57.4k27131228
edited Jan 18 '12 at 20:47
ThinkingStiff
57.4k27131228
57.4k27131228
asked Nov 15 '11 at 15:01
user589195user589195
1,777104075
asked Nov 15 '11 at 15:01
user589195user589195
1,777104075
asked Nov 15 '11 at 15:01
user589195user589195
1,777104075
1,777104075
How depends on what technology you're using to build the installer, but yes, it will be possible to set the default install path.
– Damien_The_Unbeliever
Nov 15 '11 at 15:05
aha think i may of found the property
– user589195
Nov 15 '11 at 15:06
windows installer is a technology, part of windows, that consumes msi databases and uses those to install applications. The important technology to know about is the one that you're using to construct an MSI database - WiX, InstallShield, Visual Studio Setup Project (ugh), to name a few.
– Damien_The_Unbeliever
Nov 15 '11 at 15:09
visual studio but I think i found the property
– user589195
Nov 15 '11 at 15:09
currently set to [ProgramFilesFolder][Manufacturer][ProductName] Where is it pulling those params from?
– user589195
Nov 15 '11 at 15:10
add a comment |
How depends on what technology you're using to build the installer, but yes, it will be possible to set the default install path.
– Damien_The_Unbeliever
Nov 15 '11 at 15:05
aha think i may of found the property
– user589195
Nov 15 '11 at 15:06
windows installer is a technology, part of windows, that consumes msi databases and uses those to install applications. The important technology to know about is the one that you're using to construct an MSI database - WiX, InstallShield, Visual Studio Setup Project (ugh), to name a few.
– Damien_The_Unbeliever
Nov 15 '11 at 15:09
visual studio but I think i found the property
– user589195
Nov 15 '11 at 15:09
currently set to [ProgramFilesFolder][Manufacturer][ProductName] Where is it pulling those params from?
– user589195
Nov 15 '11 at 15:10
How depends on what technology you're using to build the installer, but yes, it will be possible to set the default install path.
– Damien_The_Unbeliever
Nov 15 '11 at 15:05
How depends on what technology you're using to build the installer, but yes, it will be possible to set the default install path.
– Damien_The_Unbeliever
Nov 15 '11 at 15:05
aha think i may of found the property
– user589195
Nov 15 '11 at 15:06
aha think i may of found the property
– user589195
Nov 15 '11 at 15:06
windows installer is a technology, part of windows, that consumes msi databases and uses those to install applications. The important technology to know about is the one that you're using to construct an MSI database - WiX, InstallShield, Visual Studio Setup Project (ugh), to name a few.
– Damien_The_Unbeliever
Nov 15 '11 at 15:09
windows installer is a technology, part of windows, that consumes msi databases and uses those to install applications. The important technology to know about is the one that you're using to construct an MSI database - WiX, InstallShield, Visual Studio Setup Project (ugh), to name a few.
– Damien_The_Unbeliever
Nov 15 '11 at 15:09
visual studio but I think i found the property
– user589195
Nov 15 '11 at 15:09
visual studio but I think i found the property
– user589195
Nov 15 '11 at 15:09
currently set to [ProgramFilesFolder][Manufacturer][ProductName] Where is it pulling those params from?
– user589195
Nov 15 '11 at 15:10
currently set to [ProgramFilesFolder][Manufacturer][ProductName] Where is it pulling those params from?
– user589195
Nov 15 '11 at 15:10
add a comment |
1 Answer
1
active
oldest
votes
In a Visual Studio Setup project, you control the default install path by setting the DefaultLocation property of the Application Folder folder, within the File System Editor.
This, in turn, as you've found, defaults to [ProgramFilesFolder][Manufacturer][ProductName]. You can either replace this property entirely (you should keep [ProgramFilesFolder], at the very least though), or you can modify these properties.
[ProgramFilesFolder] is built in, and correctly leads to the Program Files directory on the target machine, no matter how customized the setup of Window is. The other two properties are properties of the setup project (select the Setup project in Solution Explorer, and examine the properties grid to find them). These default to the company name you supplied when installing Visual Studio, and the name of the Setup project.
edited Dec 10 '13 at 19:02
lazyPower
227312
answered Nov 15 '11 at 15:19
Damien_The_UnbelieverDamien_The_Unbeliever
193k17246333
1
its the program files bit i want to get rid of. I want to install in the folder above the program files directory. ie C:Manufacturer
– user589195
Nov 15 '11 at 15:41
16
You can eliminate it, but it's strongly not recommended by Microsoft. How do you know whether the machine you're installing on even has a C drive? You might try[WindowsVolume][Manufacturer], but I'm not sure it will work. Here's the documentation for the standard installer properties.
– Damien_The_Unbeliever
Nov 15 '11 at 15:52
3
The [WindowsVolume][Manufacturer] is a good answare! :)
– huncyrus
Sep 19 '13 at 10:46
Do not install directly to theWindowsVolume. This is intentionally made hard to achieve because nothing should be installed there in the first place. This is not some fixed idea, these are Windows application design guidelines. Future OS upgrades could cause binaries here to refuse to launch - for example.
– Stein Åsmul
Nov 22 '18 at 19:31
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%2f8138363%2fhow-do-i-set-the-default-install-path-with-a-windows-installer%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
In a Visual Studio Setup project, you control the default install path by setting the DefaultLocation property of the Application Folder folder, within the File System Editor.
This, in turn, as you've found, defaults to [ProgramFilesFolder][Manufacturer][ProductName]. You can either replace this property entirely (you should keep [ProgramFilesFolder], at the very least though), or you can modify these properties.
[ProgramFilesFolder] is built in, and correctly leads to the Program Files directory on the target machine, no matter how customized the setup of Window is. The other two properties are properties of the setup project (select the Setup project in Solution Explorer, and examine the properties grid to find them). These default to the company name you supplied when installing Visual Studio, and the name of the Setup project.
edited Dec 10 '13 at 19:02
lazyPower
227312
answered Nov 15 '11 at 15:19
Damien_The_UnbelieverDamien_The_Unbeliever
193k17246333
1
its the program files bit i want to get rid of. I want to install in the folder above the program files directory. ie C:Manufacturer
– user589195
Nov 15 '11 at 15:41
16
You can eliminate it, but it's strongly not recommended by Microsoft. How do you know whether the machine you're installing on even has a C drive? You might try[WindowsVolume][Manufacturer], but I'm not sure it will work. Here's the documentation for the standard installer properties.
– Damien_The_Unbeliever
Nov 15 '11 at 15:52
3
The [WindowsVolume][Manufacturer] is a good answare! :)
– huncyrus
Sep 19 '13 at 10:46
Do not install directly to theWindowsVolume. This is intentionally made hard to achieve because nothing should be installed there in the first place. This is not some fixed idea, these are Windows application design guidelines. Future OS upgrades could cause binaries here to refuse to launch - for example.
– Stein Åsmul
Nov 22 '18 at 19:31
add a comment |
In a Visual Studio Setup project, you control the default install path by setting the DefaultLocation property of the Application Folder folder, within the File System Editor.
This, in turn, as you've found, defaults to [ProgramFilesFolder][Manufacturer][ProductName]. You can either replace this property entirely (you should keep [ProgramFilesFolder], at the very least though), or you can modify these properties.
[ProgramFilesFolder] is built in, and correctly leads to the Program Files directory on the target machine, no matter how customized the setup of Window is. The other two properties are properties of the setup project (select the Setup project in Solution Explorer, and examine the properties grid to find them). These default to the company name you supplied when installing Visual Studio, and the name of the Setup project.
edited Dec 10 '13 at 19:02
lazyPower
227312
answered Nov 15 '11 at 15:19
Damien_The_UnbelieverDamien_The_Unbeliever
193k17246333
1
its the program files bit i want to get rid of. I want to install in the folder above the program files directory. ie C:Manufacturer
– user589195
Nov 15 '11 at 15:41
16
You can eliminate it, but it's strongly not recommended by Microsoft. How do you know whether the machine you're installing on even has a C drive? You might try[WindowsVolume][Manufacturer], but I'm not sure it will work. Here's the documentation for the standard installer properties.
– Damien_The_Unbeliever
Nov 15 '11 at 15:52
3
The [WindowsVolume][Manufacturer] is a good answare! :)
– huncyrus
Sep 19 '13 at 10:46
Do not install directly to theWindowsVolume. This is intentionally made hard to achieve because nothing should be installed there in the first place. This is not some fixed idea, these are Windows application design guidelines. Future OS upgrades could cause binaries here to refuse to launch - for example.
– Stein Åsmul
Nov 22 '18 at 19:31
add a comment |
In a Visual Studio Setup project, you control the default install path by setting the DefaultLocation property of the Application Folder folder, within the File System Editor.
This, in turn, as you've found, defaults to [ProgramFilesFolder][Manufacturer][ProductName]. You can either replace this property entirely (you should keep [ProgramFilesFolder], at the very least though), or you can modify these properties.
[ProgramFilesFolder] is built in, and correctly leads to the Program Files directory on the target machine, no matter how customized the setup of Window is. The other two properties are properties of the setup project (select the Setup project in Solution Explorer, and examine the properties grid to find them). These default to the company name you supplied when installing Visual Studio, and the name of the Setup project.
edited Dec 10 '13 at 19:02
lazyPower
227312
answered Nov 15 '11 at 15:19
Damien_The_UnbelieverDamien_The_Unbeliever
193k17246333
In a Visual Studio Setup project, you control the default install path by setting the DefaultLocation property of the Application Folder folder, within the File System Editor.
This, in turn, as you've found, defaults to [ProgramFilesFolder][Manufacturer][ProductName]. You can either replace this property entirely (you should keep [ProgramFilesFolder], at the very least though), or you can modify these properties.
[ProgramFilesFolder] is built in, and correctly leads to the Program Files directory on the target machine, no matter how customized the setup of Window is. The other two properties are properties of the setup project (select the Setup project in Solution Explorer, and examine the properties grid to find them). These default to the company name you supplied when installing Visual Studio, and the name of the Setup project.
edited Dec 10 '13 at 19:02
lazyPower
227312
answered Nov 15 '11 at 15:19
Damien_The_UnbelieverDamien_The_Unbeliever
193k17246333
edited Dec 10 '13 at 19:02
lazyPower
227312
edited Dec 10 '13 at 19:02
lazyPower
227312
edited Dec 10 '13 at 19:02
lazyPower
227312
227312
answered Nov 15 '11 at 15:19
Damien_The_UnbelieverDamien_The_Unbeliever
193k17246333
answered Nov 15 '11 at 15:19
Damien_The_UnbelieverDamien_The_Unbeliever
193k17246333
answered Nov 15 '11 at 15:19
Damien_The_UnbelieverDamien_The_Unbeliever
193k17246333
193k17246333
1
its the program files bit i want to get rid of. I want to install in the folder above the program files directory. ie C:Manufacturer
– user589195
Nov 15 '11 at 15:41
16
You can eliminate it, but it's strongly not recommended by Microsoft. How do you know whether the machine you're installing on even has a C drive? You might try[WindowsVolume][Manufacturer], but I'm not sure it will work. Here's the documentation for the standard installer properties.
– Damien_The_Unbeliever
Nov 15 '11 at 15:52
3
The [WindowsVolume][Manufacturer] is a good answare! :)
– huncyrus
Sep 19 '13 at 10:46
Do not install directly to theWindowsVolume. This is intentionally made hard to achieve because nothing should be installed there in the first place. This is not some fixed idea, these are Windows application design guidelines. Future OS upgrades could cause binaries here to refuse to launch - for example.
– Stein Åsmul
Nov 22 '18 at 19:31
add a comment |
1
its the program files bit i want to get rid of. I want to install in the folder above the program files directory. ie C:Manufacturer
– user589195
Nov 15 '11 at 15:41
16
You can eliminate it, but it's strongly not recommended by Microsoft. How do you know whether the machine you're installing on even has a C drive? You might try[WindowsVolume][Manufacturer], but I'm not sure it will work. Here's the documentation for the standard installer properties.
– Damien_The_Unbeliever
Nov 15 '11 at 15:52
3
The [WindowsVolume][Manufacturer] is a good answare! :)
– huncyrus
Sep 19 '13 at 10:46
Do not install directly to theWindowsVolume. This is intentionally made hard to achieve because nothing should be installed there in the first place. This is not some fixed idea, these are Windows application design guidelines. Future OS upgrades could cause binaries here to refuse to launch - for example.
– Stein Åsmul
Nov 22 '18 at 19:31
1
1
its the program files bit i want to get rid of. I want to install in the folder above the program files directory. ie C:Manufacturer
– user589195
Nov 15 '11 at 15:41
its the program files bit i want to get rid of. I want to install in the folder above the program files directory. ie C:Manufacturer
– user589195
Nov 15 '11 at 15:41
16
16
You can eliminate it, but it's strongly not recommended by Microsoft. How do you know whether the machine you're installing on even has a C drive? You might try
[WindowsVolume][Manufacturer], but I'm not sure it will work. Here's the documentation for the standard installer properties.– Damien_The_Unbeliever
Nov 15 '11 at 15:52
You can eliminate it, but it's strongly not recommended by Microsoft. How do you know whether the machine you're installing on even has a C drive? You might try
[WindowsVolume][Manufacturer], but I'm not sure it will work. Here's the documentation for the standard installer properties.– Damien_The_Unbeliever
Nov 15 '11 at 15:52
3
3
The [WindowsVolume][Manufacturer] is a good answare! :)
– huncyrus
Sep 19 '13 at 10:46
The [WindowsVolume][Manufacturer] is a good answare! :)
– huncyrus
Sep 19 '13 at 10:46
Do not install directly to the
WindowsVolume. This is intentionally made hard to achieve because nothing should be installed there in the first place. This is not some fixed idea, these are Windows application design guidelines. Future OS upgrades could cause binaries here to refuse to launch - for example.– Stein Åsmul
Nov 22 '18 at 19:31
Do not install directly to the
WindowsVolume. This is intentionally made hard to achieve because nothing should be installed there in the first place. This is not some fixed idea, these are Windows application design guidelines. Future OS upgrades could cause binaries here to refuse to launch - for example.– Stein Åsmul
Nov 22 '18 at 19:31
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%2f8138363%2fhow-do-i-set-the-default-install-path-with-a-windows-installer%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
How depends on what technology you're using to build the installer, but yes, it will be possible to set the default install path.
– Damien_The_Unbeliever
Nov 15 '11 at 15:05
aha think i may of found the property
– user589195
Nov 15 '11 at 15:06
windows installer is a technology, part of windows, that consumes msi databases and uses those to install applications. The important technology to know about is the one that you're using to construct an MSI database - WiX, InstallShield, Visual Studio Setup Project (ugh), to name a few.
– Damien_The_Unbeliever
Nov 15 '11 at 15:09
visual studio but I think i found the property
– user589195
Nov 15 '11 at 15:09
currently set to [ProgramFilesFolder][Manufacturer][ProductName] Where is it pulling those params from?
– user589195
Nov 15 '11 at 15:10