wyUpdate - AutomaticUpdater for WPF.NET often download 2 times

hi WyBuild Supporter,We implemented AutomaticUpdater for WPF.NET but we got issue that sometimes wyUpdate download 2 times:-On first time: it checked current version and got/download latest version - it just took awhile but when this process extracted completed, the Downloading appear again and this time seems it got code from 1.0 to lastest and took longtime to complete.This issue happened 25% on our software and i believe it is bug of wyUpdate.Please give me advice or fix this issue ASAP.Thanks and regards.

and i believe it is bug of wyUpdate

It's not. See: FAQ: What's the "catch-all" update? Why is it so large? And why is it being downloaded?.

Short answer: a file is failing to be patched. Read the FAQ to find out which file it is.

hi Sam,Thanks for your reply, i unchecked the "Create a catch-all update" and it works fine now.

hi Sam,After updated next new version with unchecked "catch-all", our client got this issue http://img42.imageshack.us/img42/4598/img12042013192127.png (for 4 files were dotfuscated)I'm sure source files weren't changed and user can't change those dlls by themselves.Not sure why wyUpdate checked old version files for what, i think just need to replace by new file is fine right?Thanks and regards.

Not sure why wyUpdate checked old version files for what, i think just need to replace by new file is fine right?

wyUpdate uses the old files along with the small patch to create the new file. Thus the old files on the user's computer should match what's listed in wyBuild. Otherwise the "catch-all" file will be downloaded.

dotfuscated

Don't obfuscate you code. Why? Because (a) it can be undone very easily and (b) because the patches wyBuild generates are bigger than if wyBuild was just patching your un-obfuscated code.

wyUpdate uses the old files along with the small patch to create the new file. Thus the old files on the user's computer should match what's listed in wyBuild. Otherwise the "catch-all" file will be downloaded.

As i explained before, those files on old version are just dlls and user has no way to change them so why wyUpdate knew those files were changed. I'm sure 100% all files on old version folder still there and no one changed on them.Is there anyway to make wyUpdate ignore checking files on old version?About obfuscated dlls file, i think this is necessary for software and almost software company did it.For more, size of obfuscated files isn't bigger than un-obfuscated much.Thanks and regards.

Is there anyway to make wyUpdate ignore checking files on old version?

For patches? No. Patches, by the very definition, require the old file.

If you want to do straight file copies then use only a single version in wyBuild. This will put wyUpdate in the "file copy" mode rather than patch mode. Of course the updates will be larger in "file copy" mode.

Hello Sam,

Can you let us know how it compares and knows what is the old file? if we have File1.dll and File2.dll, and we have Source Code for File2.dll but not for File1.dll, to update File2.dll with a new binary only

File1.dll must have same name, binary, size, created date, modified date or just name and binary/size? what are all the properties.. I tried to look around for that, but couldn't find yet. If we move to another server to build, do we need to copy those old files over or just have the same binary, version etc... I hope I am making sense and you can fill in the details, even those we may not be mentioning here but may help us.. Thanks..

We had issue when we turned off "catchall" and tried to update it complained about a DLL.. but we don't know how it would be different from the previous version needing to be updated...

the 2nd issue we don't know is why the update package seems to update twice sometimes.. we can see in fiddler.. but it's hard to reproduce...

any ideas? thanks!

See: FAQ: What's the "catch-all" update? Why is it so large? And why is it being downloaded?.

Short answer: a file is failing to be patched. Read the FAQ to find out which file it is.