eYoung I am able to resolve my problem because of windows security issues it
is not inserting in syswow folder so that's the reason it is not registering
in regedit with syswow folder.
I just added
SetDirectory Id=dirE83E2903B913C888AB303B0FEE2CB6DB
Value=[SystemFolder] /
it worked.
I have
1. It's my understanding that WiX preferred method is not to save to
GAC, but dont quote me on that.
2. That is outside my area of expertise, although I know others will
answer. If your interested please buy
http://www.amazon.com/WiX-3-6-Developers-Windows-Installer/dp/1782160426
It has
Is not inserting in the syswow folder doesn't really help much. If
you can't copy it there, then you can't register in in HKLM either,
---
Phil Wilson
On Fri, Jun 13, 2014 at 10:33 AM, Carter Young ecyo...@grandecom.net wrote:
1. It's my understanding that WiX preferred method is
MSINET.OCX: either install it to the System32 folder and register it, or
use RegFree COM. RegFree COM is a great technology that makes VB6 programs
really portable: you have to add the entries for the DLL and OCX files to
the manifest for the executable, and then they work magically without any
This doesn't work on 64 bit systems as the ocx file id 32 bit only,
therefore you need SysWow, which as stated previously, is not
inserting...
Quoting Alasdair King alasdairk...@gmail.com:
MSINET.OCX: either install it to the System32 folder and register it, or
use RegFree COM. RegFree COM
Young I am able to resolve all the issues by adding ensuretable but couldn't
resolve only one issue
Error 1 ICE02: Component
'Global_System_OAREG.900AE6ED_B3C8_4C1C_B3A7_EBA22F9EE105' references
ODBCDataSource 'Global_System_OAREG_r0.900AE6ED_B3C8_4C1C_B3A7_EBA22F9EE105'
as KeyPath, but
No, but comment out all the merge modules and references, then add
them in one at a time then recompile then add 1 then recompile etc
until you find the one causing the issue. Once you find it, we will
have to find a fix, which may not exist, which leads us back to the
point I tried to
My guess on this is that your development machine has no OBDC32 driver
installed. If the OS is 64-bit, my assumption is correct. See:
http://msdn.microsoft.com/en-us/library/aa368797(v=vs.85).aspx
Quoting sandyGSS sandhya@gmail.com:
Young I am able to resolve all the issues by adding
But I tried to check in my machine when I got the error. But there aren't any
odbc drivers and also for our product we try to use oledb drivers .
Let me try to add one by one module in to the msi and test it out.
Thanks
Sandhya
--
View this message in context:
Your having this issue because Windows 7 doesn't use the old format
OBDC drivers. It uses the new ACE format.
Carter
Quoting sandyGSS sandhya@gmail.com:
But I tried to check in my machine when I got the error. But there aren't any
odbc drivers and also for our product we try to use
Hey phil If i am trying to download through the link
http://www.everythingdesign.net/zero/installanywhere-net-merge-modules.html
I am getting below error.
ERROR
The requested URL could not be retrieved
The following error was encountered while trying to retrieve the URL:
That whole structure is down. Every file Reports:
Oops! Google Chrome could not connect to goldengate.zerog.com
Did you mean: zerog.com
Carter
Quoting sandyGSS sandhya@gmail.com:
Hey phil If i am trying to download through the link
yes zerog.com is working but the merge modules for .net I couldn't find in
that site.
On Thu, Jun 5, 2014 at 8:47 AM, Carter Young ecyo...@grandecom.net wrote:
That whole structure is down. Every file Reports:
Oops! Google Chrome could not connect to goldengate.zerog.com
Did you mean:
Exactly, like the error message states, the goldengate subdomain has
been removed, therefore you beed to find the merge modules elsewhere...
Quoting Sandhya Ch sandhya@gmail.com:
yes zerog.com is working but the merge modules for .net I couldn't find in
that site.
On Thu, Jun 5, 2014
Young I downloaded .msm files from below location
http://www.microsoft.com/en-us/download/confirmation.aspx?id=5883
Trying to patch up to existing .msi but not successful . can we do it
through melt.exe create .wxs file and merge in to existing product.wxs file
like using heat?
Can you please
Start Here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-use-a-Merge-Module-msm-file-in-a-WiX-project-td6533730.html
Then Here: -- Step 2
http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/install_vcredist.html
and Lastly:
Young If I did in that way I am facing issues
Error 1 ICE02: Component
'Global_System_OAREG.900AE6ED_B3C8_4C1C_B3A7_EBA22F9EE105' references
ODBCDataSource 'Global_System_OAREG_r0.900AE6ED_B3C8_4C1C_B3A7_EBA22F9EE105'
as KeyPath, but the ODBCDataSource table does not exist.
Because Your using the wrong Version, ie you cant use a .NET
Compatible Version for a VB6 Component... You'll need to keep testing
til you find the right version of the merge module.
Quoting sandyGSS sandhya@gmail.com:
Young If I did in that way I am facing issues
Error 1 ICE02:
IIRC, OCX Controls were only supported from Windows 95 up to XP,
during the Lifespan of VB4 - VB6. They are no longer supported in
Windows Versions past XP. You'll need to upgrade the components to
their .NET equivalent. If your app is written in VB6, it's time to
upgrade the app.
Yes our app is built in vb6 and we are trying to install the msi in windows
8. Actually windows 7 is working fine. Can you please specify what to
upgrade??
--
View this message in context:
All the items and controls that you are using that require OCX files
will have to be rewritten(custom) or replaced by the .NET replacement.
You can't use the .NET replacements until you recode the app in at
least .NET Framework 2.0 SP1
Carter
Quoting sandyGSS sandhya@gmail.com:
Yes
Hey young without upgrading with the existing ocx files can't we use wix
installer to generate an msi?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ocx-file-is-not-registered-in-windows-8-tp7595015p7595021.html
Sent from the wix-users mailing
There's still a dependency on the vb6 runtime, so the target machine
will need that installing.
That error decodes to The operating system cannot run %1. but it's
not clear to me what is running at install time if you've extracted
all the registration data. You may need to look at a verbose log
Do you have any reference / documentation link about this?
--
Nicolás
2014-06-04 11:53 GMT-03:00 Carter Young ecyo...@grandecom.net:
IIRC, OCX Controls were only supported from Windows 95 up to XP,
during the Lifespan of VB4 - VB6. They are no longer supported in
Windows Versions past XP.
ok if there is a solution of merge module. Can you please suggest me how to
use merge module for all the ocx's.
The problem is it is not registering the msinet.ocx in the regedit properly
in windows 8. We are not facing any issues in windows 7
example_Windows_7.log
No ones stopping you from doing that, as that's what youve done, but
if you want to use the installer, you can only use it on the OS'es
that are all EoL, as depending on the settings in Windows 7, users can
choose to support ocx files or not, and if they choose to support
them, you must
Before you go down that path, read my other email... I apologize as a
one handed disabled typist/programmer some of the answers take awhile :)
Carter
Quoting sandyGSS sandhya@gmail.com:
ok if there is a solution of merge module. Can you please suggest me how to
use merge module for all
Oh ok young I got it.
But how can we do by using the merge module? what is the merge module? can
you give me the references?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ocx-file-is-not-registered-in-windows-8-tp7595015p7595027.html
Sent from
This link that Phil Posted Earlier should start you on the right path:'
http://msdn.microsoft.com/en-US/vstudio/ms788708.aspx
Carter
Quoting sandyGSS sandhya@gmail.com:
Oh ok young I got it.
But how can we do by using the merge module? what is the merge module? can
you give me the
From said Link: (Quote)
Supporting and/or shipping Visual Basic 6.0 runtime binaries on
Windows Vista/Windows Server 2008/Windows 7/Windows 8 does not change
the support policy for the Visual Basic 6.0 IDE or Visual Studio 6.0
IDE as a whole. Those products will move out of extended
Thats ok thanks young through our posts I came to know there are two
solutions
1) Either manually go ahead and register .ocx files in windows 8 or
2) In this link it just says it couldn't support but support agreements are
available
No, but Custom Support Agreements may be available.
But here
Merge Modules:
http://msdn.microsoft.com/en-us/library/aa369820(v=vs.85).aspx
Using Merge Modules:
http://msdn.microsoft.com/en-us/library/aa372427(v=vs.85).aspx
Carter
Quoting sandyGSS sandhya@gmail.com:
Thats ok thanks young through our posts I came to know there are two
solutions
1)
...@grandecom.net]
Sent: 04 June 2014 15:53
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] .ocx file is not registered in windows 8
IIRC, OCX Controls were only supported from Windows 95 up to XP, during the
Lifespan of VB4 - VB6. They are no longer supported in Windows Versions past
The official merge modules should be somewhere in the VB6 setup, or
included with the Visual Studio Installer that was available at that
time. These guys seem to have accumulated the latest ones, including
msinet.msm.
http://www.everythingdesign.net/zero/installanywhere-net-merge-modules.html
Yes that's what my concern is neil all the other ocx files are working fine
except this msinet.ocx. After googling for 4 to 5 days I couldn't find the
answer.
How can we check whether it might have dependencies or not? Can you suggest
me.
Young thanks for sending the merge modules will try to
it.
Neil
-Original Message-
From: sandyGSS [mailto:sandhya@gmail.com]
Sent: 04 June 2014 17:08
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] .ocx file is not registered in windows 8
Yes that's what my concern is neil all the other ocx files are working fine
except
Thanks neil I will try to test that once I get permision from my manager.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ocx-file-is-not-registered-in-windows-8-tp7595015p7595039.html
Sent from the wix-users mailing list archive at Nabble.com.
37 matches
Mail list logo
