Serious framework problem with wyUpdate

Hi.

I have a serious update problem which my customers (naturally) complain about:

When they try to update our product, they are met with a dialog box showing:

Caption: "InstantUpdate.exe - .NET Framework Initialization Error".Text: "To run this application, you must first install one of the following versions of the .NET Framework: v4.0.30319. Contact your application publisher for instructions about obtaining the appropriate version of the .NET Framework."

and our product does not update.

This happens both on Windows 7 Proffessional (32-bit) and Windows Server 2008 R2 SP1 (64-bit). I use AutomaticUpdater to programmatically control the update process, and the message pops up whenever wyUpdate is about to start downloading the update files. Prior to that, wyUpdate has successfully checked for (and discovered) an update to our product, and it has also retrieved the description text of the new version.

I am very certain that when I (some time ago) created the new version of our product and created the update files I tested the whole thing and everything worked as usual. But now it seems that it has for no reason stopped working, without me having changed anything.

I know that wyUpdate.exe updates itself prior to updating the user's application, and I tend to belive that wyUpdate updates itself to a version requireing .NET 4.0 - could that be?

I have tried to verity this by blocking the access to wyday.com (by means of the .hosts file in Windows) to prevent the automatic update of wyUpdate, but then wyUpdate throws an exception and does not continue with downloading the update files for my product.

Please help, it is very ugent to get the update process running again!

The version of our product that must be updated uses wyUpdate.exe version 2.6.18.4.

Regards, Martin.

Additional information:

Using the ServerViewer.exe tool, I can see that wyserver.wys states that wyUpdate.exe version 2.6.18.4 or later is required. This perfectly explains why wyUpdate.exe 2.6.14.0 downloads a new version of itself (InstantUpdate.exe) for handling file download and extraction. But why does it download a version requirering framework 4???

- Martin.

Double click your client.wyc file. What do you see for the wyUpdate self-update sites? Also, check your File -> Properties -> wyUpdate page in wyBuild. Make sure .NET 2.0 is selected.

Self-update site is: http://wyday.com/files/wyupdate/updates/client.net4.wysIn wyBuild .NET 2.0 is selected.

Notice, that the client.wyc file was created with an earlier version of wyBuild (wyBuild has updated itself since then).

I just looked into the client.wyc file for the previous version (which has updated well). Here the self-update site is http://wyday.com/files/wyupdate/updates/client.wys (!)

- Martin.

Self-update site is: http://wyday.com/files/wyupdate/updates/client.net4.wys

That's the .NET 4.0 version. My guess is that someone switched your project to .NET 4.0, rebuild wyUpdate, then switched back to .NET 2.0.

Everything is working fine here - the correct self-update sites are being set when "Build wyUpdate" is clicked. What happens when you rebuild wyUpdate? Is the .NET 2.0 site shown or the .NET 4.0 site?

When I rebuild wyUpdate it's the .NET 2.0 site.

I guess you're right in your assumption that someone (I?) had accidentally switched wyBuild to .NET 4 when the client.wyc file was generated (and later switched back again to 2.0). However, that is impossible for me to tell for sure, since the project file (.wyp) from that time has long been gone.

In my earlier post I stated that I carefully tested the update, but maybe that test was done on a machine that had .NET 4.0 installed already - and therefore I never saw the problem?

New question: Given the current situation, what do you think would be the best way to solve the situation?1) Tell the customers to manually install framework 4.0 first, and then try to update anew?2) Distribute a corrected client.wyc and have the customers manually replace the old file with the corrected one?3) ???

- Martin.

2) Distribute a corrected client.wyc and have the customers manually replace the old file with the corrected one?

It's easiest just to give them the fixed client.wyc file. Make sure the version number is correct (matches the version they have installed).