• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 148
  • Last Modified:

Question Regarding Creation of a Windows Installer Package

I have a setup project in my solution. Everything 'works' okay, but I would like to get rid of a kink.

Apparently something in our company's policy defaults the installation folder to:
  C:\Program Files\CompanyName - For Internal Use Only\ProjectName\

Can I set the default location in the setup project to a specific name. 99.999% of the time, C:\Program Files\ProjectName\ will be a valid installation path, so can that be somehow hardcoded?
0
dbbishop
Asked:
dbbishop
  • 4
  • 3
1 Solution
 
Jorge PaulinoIT Pro/DeveloperCommented:
You can choose the default location when you create the distribution package.

C:\Program Files\ProjectName\ Is the path that you like ?
0
 
dbbishopAuthor Commented:
How? I don't see any property that lets you specify a default installation path.
0
 
Jorge PaulinoIT Pro/DeveloperCommented:
Are you using the VS Setup Project ?
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
dbbishopAuthor Commented:
Yes. VS 2005
0
 
Jorge PaulinoIT Pro/DeveloperCommented:
If you select the Application Folder on the File system on Target Machine you will see on the properties the DefaultLocation. You just have to change there.
0
 
dbbishopAuthor Commented:
I'm home. I will check tomorrow. Thanks.

Doug
0
 
dbbishopAuthor Commented:
That worked. Thanks.
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now