This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- .NET ProgramFilesFolder on 64-bit
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 22, 2012
09:41 AM
.NET ProgramFilesFolder on 64-bit
Hello!
My target:
One MSI for my .NET application
for 64-bit and 32-bit
Installationfolder allways: c:\program files
--- not c:\program files(x86) on a 64-bit system!
Many thanks in advance!
Johannes
My target:
One MSI for my .NET application
for 64-bit and 32-bit
Installationfolder allways: c:\program files
--- not c:\program files(x86) on a 64-bit system!
Many thanks in advance!
Johannes
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 22, 2012
01:38 PM
I don't fully understand your question. Realize that the ProgramFilesFolder property will always resolve to the 32bit program files directory. The ProgramFiles64Folder property will resolve to the 64bit directory but can only be used in an MSI package that has been marked as 64bit.
Also generally the Any CPU concept in .NET was a failure. Newer versions of .NET now default to x86 and it's generally best to to think of your application as 32bit ( especially if you are doing COM Interop or P/Invoke ). If you really need to be Any CPU then a lot of thought has to go into making sure you have all your right dependencies for 32bit and 64bit.
You might be interested in this:
http://blog.iswix.com/2011/01/comments-on-setting-installdir-during.html
Also generally the Any CPU concept in .NET was a failure. Newer versions of .NET now default to x86 and it's generally best to to think of your application as 32bit ( especially if you are doing COM Interop or P/Invoke ). If you really need to be Any CPU then a lot of thought has to go into making sure you have all your right dependencies for 32bit and 64bit.
You might be interested in this:
http://blog.iswix.com/2011/01/comments-on-setting-installdir-during.html
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 23, 2012
03:05 AM
Thank you Christopher,
your first chapter hits the bull's eye.
Does the assessment with the failture come from MS?
Regards
Johannes
your first chapter hits the bull's eye.
Does the assessment with the failture come from MS?
Regards
Johannes
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 23, 2012
05:47 AM
Well, I'm sure MS wouldn't call it a "failure" but here's the rational that I recall reading from them:
http://blogs.msdn.com/b/rmbyers/archive/2009/06/09/anycpu-exes-are-usually-more-trouble-then-they-re-worth.aspx
http://blogs.msdn.com/b/rmbyers/archive/2009/06/09/anycpu-exes-are-usually-more-trouble-then-they-re-worth.aspx