wupdate.exe question

[NewsArchive]

Friedrich,

Any possibility of deploying wupdate.dll instead? I'd like to have
something like this in my templates:

#RUNDLL('wupdate.dll'),WIN32,RELEASE

Also, I think I saw somewhere you could rename the update program? Or was
that a request from someone?

--
Russell B. Eggen
www.radfusion.com
Skype Clarion chat: http://tinyurl.com/2273lm

[NewsArchive]

Hi Russ,

> Any possibility of deploying wupdate.dll instead? I'd like to have
> something like this in my templates:
>
> #RUNDLL('wupdate.dll'),WIN32,RELEASE

"wupdate.exe" is compiled from the SetupBuilder "wupdate.sb6 project.
SetupBuilder cannot generate dynamic link libraries!

> Also, I think I saw somewhere you could rename the update program? Or was
> that a request from someone?

You can rename the update program to whatever you want. Let us assume, you
rename your (own) web update client to "wupdate_russ.exe". No problem! You
only have to make sure that the "Include Web Update Client" function in your
project (that makes the application web update ready) points to your client
executable.

For example:

Include Web Update Client "c:\test\wupdate_russ.exe"

This will compile your own web update program into the setup.exe.

Does this help?

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Yup.

I've a few other ideas about the update from a template.

Thanks. ;-)

--
Russell B. Eggen
www.radfusion.com
Skype Clarion chat: http://tinyurl.com/2273lm

[NewsArchive]

Hi Russ,

> I've a few other ideas about the update from a template.

You can just create a small dll in VC or something (I would not use Clarion
or you'll have to have different dlls for different versions - total PITA)
that uses shellexecute to run the webupdater. I don't think #run would work
reliably under vista unless you run Clarion elevated. I'm pretty sure it
uses CreateProcess which can't elevate and the #run would fail.

Also remember that when using #run and #rundll the application folder (where
the app is) is the current folder so you need to trick the webupdate by
telling it which startup folder to use (shellexecuteex can do that).

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Not using Clarion is not an option.

Appreciate the feedback! ;-)

--
Russell B. Eggen
www.radfusion.com
Skype Clarion chat: http://tinyurl.com/2273lm

[NewsArchive]

Hi Russ,

> Not using Clarion is not an option.

Then you are in for a DLL hell my friend<g> I ended up with 24 dlls before
I finally broke down and learned enough C to do it outside of Clarion.
Never looked back:)

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

The reason why I won't use anything but Clarion is because I so easily avoid
DLL-hell. Never been an issue, I intend to keep it that way <g>.

--
Russell B. Eggen
www.radfusion.com
Skype Clarion chat: http://tinyurl.com/2273lm

[NewsArchive]

Hi Russ,

> The reason why I won't use anything but Clarion is because I so easily avoid
> DLL-hell. Never been an issue, I intend to keep it that way <g>.

If you have a dll called by #rundll that is compiled in say Clarion 6.3 and
you are using it with Clarion 6.2 you will get into problems. Any time the
RTL changes you need to create a new version of your dll. If this is for
your own development - i.e. not being deployed to Clarion developers, no
problem, but if it's for deployment of third party tools, it will cause
problems. Been there, done that<g> If you know a way around that I would
really like to hear it:)

Best regards,


--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

That is something totally under my control. I don't mix versions. So I
don't see this as an issue at all. Unlike some 3rd party vendors, I only
support the versions SV does. That does not mean the others are making a
mistake or I am. That is strictly the vendor's call. I also have the same
policy with List and Label. Whatever Combit supports, so do I.

Now to go full circle, the reason I want a wupdate.dll is so that a
developer could use the DLL from the templates to check for updates and
download one if it exists. But its no big deal if the EXE is the only
option available. I can still use that.

--
Russell B. Eggen
www.radfusion.com
Skype Clarion chat: http://tinyurl.com/2273lm

[NewsArchive]

Hi Russ,

> That is something totally under my control. I don't mix versions. So I
> don't see this as an issue at all. Unlike some 3rd party vendors, I only
> support the versions SV does. That does not mean the others are making a
> mistake or I am.

No, but you are excluding customers with a slightly older build - for
example Clarion 6.3 build 9059 and 9053 builds don't match - require new dll
if I'm not mistaken. Nothing wrong with that of course, but there may be
very valid reasons why developers don't go up from a specific version. In
many of my products I support Clarion all the way back to C4 which requires
a ton of DLLs if I hadn't done in it C<g>

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Still makes no difference since it has only one purpose. Even if a customer
is wildly off.

--
Russell B. Eggen
www.radfusion.com
Skype Clarion chat: http://tinyurl.com/2273lm