update failed to install - hidden & read-only files [Solved]

Ok, the update is out. This should fix your problems.

Friday May 15th @ 3p.m. Eastern Standard Time at the very latest.

OK - I may try and buy some more time from our client to hold off for the updated version of wybuild. Is 5 days realistic or is it likely to longer (no pressure on you of course!!):-)

Yes, this is caused by updating/deleting files that are Read-only. I've fixed this as well. An update should be out in 4-5 days.

Wyatt,
Hidden files isn't a problem - I've now made them visible.

However I am now getting a big failure which ends with the tell "Microsoft about this problem alert". The Information includes EventType clr20r3 P1 wyupdate.exe p2 1.3.1.0 P3 49ae9ca7 etc.

Is it some sort of exception error?

Problem is I get it on all test machines with this update. I will try again to do a small selective update and see what happens. I'm not sure why I was able to create one update which apart from the hidden file errors worked, and now I have this issue. There are no wyUpdate errors it just crashes out after "backing up and updating files".

Ok, I've confirmed this exact behavior on my own tests. Thanks for reporting this. It'll be fixed in the next version.

So, wyUpdate is having problems updating hidden files? Do you need to update hidden files? That is, is it critical to your application that the files/ folders be hidden?

I'm sorry for the trouble this is causing you. I'm going to look into this, because it definitely sounds like a bug.

- Wyatt

OK I think I may have solved this one - one of the files which was being updated appeared to be a hidden file - it seems that the update procedure didn't like that. I'm really hoping that is the answer and that it's not after all something in wyupdate product itself. I've tested on three machines now - only one failed and this managed to work again when I made the file visible. Thanks for great and prompt support on this.

Answer to question 1 - yes latest version of wyBuild

Errors occur when installing the updates - updates are built ok, with no errors.

With a recent test - I simply added a small file to the application I ended up with a microsoft end task error report exception information code 0xe0434f4d etc.

All errors seem to happen after I click the alert box to "end process".

Yes, FSCOMMAND exists before the update.

No access is what looks like a message from your app "access to c:\documents\directory\fscommand\... is denied" -

No file called fscommand

Admin level access

I'll see what I can do about acces to the app - trouble is it's pretty large

I'm going to try a "start again process with each element of the app" -

It's really frustrating because all my testing was done a month or so ago and everything worked brilliantly. I even got my client to buy into .NET etc. I love your app, it (used to) work so well!

I've also just tried this with a very small update and get the same issue with the entire process failing. Ouuch!