OCX on a shared network install.....

[NewsArchive]

I'm using OCX controls for the first time on a shared network
installation...

What do people typically do....?

Register the OCX as it resides on the shared drive?
Copy it to the workstation and register it there?

Suggestions?

Paul MarcFarlane

[NewsArchive]

In my experience, it must be registered on the workstations. Of course, if
you're running the program also on the server itself then it must be
registered there also.

Drew

[NewsArchive]

Hi Paul,

We have always created a separate installation that installs anything
our apps require on the local PC - including OCXs. User simply runs the
setup which is on server along with all the rest of our normal
installation. I have found it is much easier to do this than to explain
to our end users the regsvr32 functions etc...

Andy

[NewsArchive]

Sounds like a good use for RegFree (now supported in Clarion 9.1).

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Paul,

I would use RegFree and deploy everything in a single location on the
shared drive.

RegFree = Isolation and Protection

David Bratovich

[NewsArchive]

Thanks All......

I think my big question is WHERE the OCX lives. IF there is a problem
with it being located on the Share.....

I do have a workstation setup process that registers the OCX - but it
doesn't copy it to the workstations hard drive.

Can't use RegFree just yet - can't go 9.1 because of a 3rd party issue....
Hopefully soon....

Paul MacFarlane

[NewsArchive]

Paul,

I have experimented with interop assemblies and Reg Free, and should
say that Reg Free works in C8 and C9.0. Not sure about regular OCXs.

Mike

[NewsArchive]

The OCX should be local to the machine (just like EXEs and DLLs). You
can still use regfree if you have the external dependent assembly
manifest for it. That file must live with the EXE and the EXE manifest
references (linked in or not) it.

Just a heck of a lot easier with 9.1. Just out of curiosity, which 3rd
party product is causing the delay in updating? Perhaps the group here
could make some recommendations on a replacement if there is no 9.x edition.

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Hi Paul,

> The OCX should be local to the machine (just like EXEs and DLLs).
Just to clarify EXEs and DLLs can physically live on the network - but
run in local memory.
OCX needs to be registered locally (AFAIK it can't be 'networked'
unless you're running RDC or similar)

> .................................................. ...............You can
> still use regfree if you have the external dependent assembly manifest for
> it. That file must live with the EXE and the EXE manifest references (linked
> in or not) it.
At least in my experience that's not correct.
RegFree COM didn't work prior to Clarion 9.1 not because of the absence
of manifests (or the information within them) but because of the way
the OLE control worked.

It was the changes in the OLE control code in Clarion 9.1 that made
RegFree possible.

Graham

[NewsArchive]

> OCX needs to be registered locally (AFAIK it can't be 'networked' unless
> you're running RDC or similar)

Yes the OCX needs to be "registered" by each machine but the location of
the file itself can be anywhere.

db

[NewsArchive]

Hi David,

> .................. but the location of the file itself can be anywhere.

Didn't realise that, good to know - there's always an extra 'wrinkle'
lurking around isnt' there :-)

Graham

[NewsArchive]

yup!

Check your email.

db

[NewsArchive]

Hmm.. haven't seen anything - I'll check the spam filter.....

Paul MacFarlane

[NewsArchive]

> Hmm.. haven't seen anything - I'll check the spam filter.....
>
Sorry, that was for Graham

Heck, I just sent you a copy anyway!

db

[NewsArchive]

> can still use regfree if you have the external dependent assembly
> manifest for it.

CW 9.1 requires all dependentAssembly manifests to be external and
requires a dependentAssembly manifest for each OCX your app references.

Only the app manifest can be linked in.

db

[NewsArchive]

So heres what is happening:
I setup the application into a shared folder.
I ran the software and all seemed fine (Codejock stuff).

Went to workstation2. Run my workstation setup (registers the OCXs and
creates shortcuts).
Ran on the software of workstation2. Ran fine.

Played a bit and after closing and reopening the app a couple times,
both workstation display a blank screen (no OCX controls).
It's like they are getting loaded now.

Any clue as to why that would happen?

Maybe its Secwin causing this problem....

Paul MacFarlane

[NewsArchive]

> Hmm.. haven't seen anything - I'll check the spam filter.....
Hijacking that's what I call it <VBG>

Graham

[NewsArchive]

Hi David,

I know we've asked before but do you have plans to make your utility
available in some form?

As it ships Clarion's ability to _use_ RegFree COM is really hampered by the
difficulty of creating the necessary manifest files - particularly for older
OCXs where the original developers don't provide a suitable manifest
themselves.

I can see people being very interested in it particularly as it _seems_ to
include the ability to monitor the SxS trace logs during testing/debugging.

Graham

[NewsArchive]

Yup.

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

> Hi David,
>
> I know we've asked before but do you have plans to make your utility
> available in some form?

I'm working on the docs and adding "user registration" functionality.
Then a S/B installer and it should be ready to go.


db

[NewsArchive]

> I'm working on the docs and adding "user registration" functionality.
> Then a S/B installer and it should be ready to go.
Oooh - the anticipation :-)

Graham