Relative Install-pack beginner here...
Visual Studio Installer seems to target the "System Folder" differently, in a VB project the msdxm.ocx is included and brought to the target system. Documentation suggest this ocx should reside in the System32-folder. When the VB-outputs are added to the installer-project, VSI automatically puts the ocx under "Windows System Folder".
Installing on Win2K puts the ocx in "System32"
Installing on Win98 puts dito in "System"
What is going on under the hood here? And how can I explicitly point to the "System32"-folder in the VSI-environment when I bild my MSI?
My first post - so here it is: A fab site, install-issues really deserves the kind of treatment you give it here!
Regards everybody, hansi.l
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
VSI and folder "system32"
Started by
hansi.l
, Jan 10 2003 21:41
1 reply to this topic
Posted 10 January 2003 - 21:41
_
hansi linderoth, mcp
http://www22.brinkster.com/hlinderoth/LNET/index.htm
hansi linderoth, mcp
http://www22.brinkster.com/hlinderoth/LNET/index.htm
Posted 12 January 2003 - 07:47
The "Windows System Folder" has different names on different operating systems:
C:\Windows\System on Win9X
C:\Winnt\System32 on NT4
C:\Windows\System32 on XP
etc.
But in any case this is the folder with shared system files where OCXs use to reside (unless you put them iin your own application directory or in a shared program files folder)
C:\Windows\System on Win9X
C:\Winnt\System32 on NT4
C:\Windows\System32 on XP
etc.
But in any case this is the folder with shared system files where OCXs use to reside (unless you put them iin your own application directory or in a shared program files folder)
Stefan Krüger
InstallSite.org twitter facebook