Codejock Developer Community : Vista and RegistryFree COM\OCX

Vista and RegistryFree COM\OCX : If CodeJock provided a XML manifest...

Tue, 27 May 2008 13:04:56 +0000

Author: NeilH
Subject: 8245
Posted: 27 May 2008 at 1:04pm

If CodeJock provided a XML manifest then it would save us a lot of grief. I for example don't use VS, therefore mine is more grudge work.

The above manifest did work for me however, the only changes I did where to define the folder for the filename and clear the "helpdir" values.

Otherwise this worked like a dream!

I compiled my manifest into my executable, the code inside the execuatble managed the license.

We now have different versions of our product different versions of codejock running on the same machine (Vista, XP, 2008, 2003) and nothing registered.

Depending on your application you could external manifest data, but remember XP and Vista don't work the same way (typical of Microsoft).

Regards

Neil

Vista and RegistryFree COM\OCX : Hello, I find this issue quite...

Tue, 27 May 2008 12:51:42 +0000

Author: Felipe
Subject: 8245
Posted: 27 May 2008 at 12:51pm

Hello,

I find this issue quite important. We have a big institutional customer who wants to install in Vista and XP without requiring Admin privileges. This is because their internal PC policy makes it a pain to install software in their office computers.

So far we succeeded with Side-by-Side assemblies and manifests. This works well, even with our own ActiveX components that we can install Reg-Free.

Now we need to deploy 2 new applications that integrate the Codejock Suite. And it seems there is no way that I can avoid COM registration.

We need a Manifest for the Codejock Suite, but I see no trace of a manifest inside the .ocx resources.

We generateda Manifest with Installshield 2008 and get a similar output as NeilH. But the application complains and it does not run. It only runs when we register the Codejock Suite.

We had a similar experience before with our in house ActiveX: the InstallShield generated manifest did not work. We solved it by compiling our ActiveX in VS2005 and defining the Isolated COM parameters (in VS2005 C++ select the project properties of your Activex, then Manifest/Isolated COM, and define the Type Library File (.tlb) and Component File Name (.ocx or .dll) from which extracting the manifest info.) doing this our .ocx has an RT_MANIFEST well defined that works very well in isolation Reg-Free.

I assume the Codejock Suite is compiled with a pre-VS2005 compiler for a good reason of compatibility. Would it be possible that Codejock delivers a suitable Manifest that allows for Side-BySide installations?

Thank You

Vista and RegistryFree COM\OCX : I don't have .NET!

Mon, 01 Oct 2007 10:06:34 +0000

Author: NeilH
Subject: 8245
Posted: 01 October 2007 at 10:06am

I don't have .NET!

Vista and RegistryFree COM\OCX : HI, If you use .NET, just select...

Mon, 01 Oct 2007 09:14:02 +0000

Author: Oleg
Subject: 8245
Posted: 01 October 2007 at 9:14am

HI,

If you use .NET, just select properties for interops and set Isolated property to True.

Vista and RegistryFree COM\OCX : I need a bright spark to tell...

Mon, 01 Oct 2007 07:58:25 +0000

Author: NeilH
Subject: 8245
Posted: 01 October 2007 at 7:58am

I need a bright spark to tell me where I went wrong....

The introduction of Vista enforces new rules regarding deploying applications, and often the need for "Administrator" rights. In the real world (and not on a developers machine) access to the registry is required for the registering codejocks.

If this was an installation program then perhaps I would have a different view, but I actually only update a main application server and the rest of the files are deployed out to each client machine as they connect. The clients don't have 'Administrator' rights, the files are therefore copied to the user 'virtual store'. Regsvr32 cannot be called because they don't have permissions.

The ideal solution would be to use a manifest as in RegistryFree COM therefore not requiring writing to the registry.

Would someone in the know....like to tell me where I went from in this manifest construct!......Please! :)

Any constructive help is welcomed!

Regards

Neil

MY APPLICATION


                  type="win32"
     name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="X86" publicKeyToken="6595b64144ccf1df" language="*" />




                      level="asInvoker"
            uiAccess="false"/>








      http://www.w3.org/2000/09/xmldsig#sha1" />
      CZ24nqrsDZxLa1z9s7+hM2QZkZ0=









      http://www.w3.org/2000/09/xmldsig#sha1" />
      jKT1PnCkPjzDISMN3bIxYIuMNlo=









      http://www.w3.org/2000/09/xmldsig#sha1" />
      qe+1JwTlAiUfdDEAZKsNrweDkvk=










      http://www.w3.org/2000/09/xmldsig#sha1" />
      v4HZZQUkoTfeUVs8u6x7VzK9Zyg=




















      http://www.w3.org/2000/09/xmldsig#sha1" />
      Va8Ez1OowpZisIqq/1IDywxTSVI=










      http://www.w3.org/2000/09/xmldsig#sha1" />
      dZtVM0SnXvWBlPwYrvzSR1X8EzE=









      http://www.w3.org/2000/09/xmldsig#sha1" />
      l0uM1xnO28bdruDNSYhhszz81Yk=










      http://www.w3.org/2000/09/xmldsig#sha1" />
      9Lc2q3ueiohrY49kr2XZfogIqPw=









      http://www.w3.org/2000/09/xmldsig#sha1" />
      wMMD9kihaW4jcwZk/hV3c/vRxRo=











      http://www.w3.org/2000/09/xmldsig#sha1" />
      L1FYKQYP54rKawNP19j3/MnH0CE=