File expected..... error

[NewsArchive]

Hi friedrich and all,

While trying to update, all were working ok, now I´m getting the following
error

File expected from server and receiver file do not match MyDll.dll etc etc
etc

Whats wrong??

Thanks

--

Saludos / Regards,

Use TraceIt the best way to trace and support your applications!.
http://www.armi.com.ar/ARMi_TraceIt_ing.htm

Alberto Michelis
ARMi software solutions
www.armi.com.ar

[NewsArchive]

Alberto,

> While trying to update, all were working ok, now I´m getting the
> following error
>
> File expected from server and receiver file do not match MyDll.dll
> etc etc etc
>
> Whats wrong??

The following should help:

http://www.lindersoft.com/forums/showthread.php?p=29392#post29392

You did not update the files on your server.

[NewsArchive]

mmhhh I always upload after compile.

--

Saludos / Regards,

Use TraceIt the best way to trace and support your applications!.
http://www.armi.com.ar/ARMi_TraceIt_ing.htm

Alberto Michelis
ARMi software solutions
www.armi.com.ar

[NewsArchive]

>
> mmhhh I always upload after compile.
>

This error only comes up if the files on your server do not match the files
you have used to build the installer. This feature is there to protect your
customers -- without it, your customers would have received an incorrect set
of update files.

--
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]

OK, Friedrich, I´ll look into it.
I´ve seen that many users does not understand the Sb error message, thats
because the message indicates the error but not the cause, this error is an
example...

File expected......

I think it should be better if you add a line indicating the cause like:

File expected.....
Note: The files on the update server do not match the files used to build
the installer or set the Add/Remove Program

another example:

Previous Version Detection Failed.
Note: Check the Product GUID or did not run the main installer.

I know you would say, this is an error message for your customer, not for
you, but I think the customer does not understand any of the messages :-))

Just and Idea...


--

Saludos / Regards,

Use TraceIt the best way to trace and support your applications!.
http://www.armi.com.ar/ARMi_TraceIt_ing.htm

Use TraceIt la mejor manera de tracear y dar soporte a sus aplicaciones!
http://www.armi.com.ar/ARMi_TraceIt_esp.htm

Alberto Michelis
ARMi software solutions
www.armi.com.ar

[NewsArchive]

Alberto,

> OK, Friedrich, I´ll look into it.
> I´ve seen that many users does not understand the Sb error message, thats
> because the message indicates the error but not the cause, this error is
> an example...

Well, "many users" is relative to where you draw the line. Based on the
number of SetupBuilder licenses out there, it's very very very few users.

Sure, there is always room for improvements. We'll list all possible error
codes and descriptions in the manual over the next 4-6 months. There is
already a new "Runtime Errors" section in the manual.

> File expected......
>
> I think it should be better if you add a line indicating the cause like:
>
> File expected.....
> Note: The files on the update server do not match the files used to build
> the installer or set the Add/Remove Program

Hmm, "Set Add/Remove Program"? What does the "File expected" error have to
do with it?

> another example:
>
> Previous Version Detection Failed.
> Note: Check the Product GUID or did not run the main installer.
>
> I know you would say, this is an error message for your customer, not for
> you, but I think the customer does not understand any of the messages :-))
>
> Just and Idea...

If users don't read the current description in the manual then I am sure
they will also not read what you suggested ;-)

From the current manual ("Detect Previous Version"):

---

Remarks:

This function uses the Product GUID of previously distributed versions to
determine if the application is installed on the client. It only works if
the previous installation created a Product GUID (code) in the following
section of the Windows registry:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Uninstall

SetupBuilder automatically creates this item if the Add/Remove Programs
Support option is enabled in the "General Information" Visualizer

---

Hope this makes sense.

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