Just add a new version "1.1.0" and don't add any files to it. Now when you build your update the 1.1.0 -> X will include the full files.
Dealing With a Gap
BrentHi,
I ran into this today. It is not a problem with the software, so much as a problem with the user ... me. I was just looking for a way to fix it.
Say I have a product that initially releases as 1.0.0. I use wyBuild to publish updates 1.0.1, 1.0.2, etc. Later on, I compile 1.1.0. Users download and install 1.1.0. However, I never create version 1.1.0 in wyBuild, nor do I (of course) build any updates for 1.1.0. Subsequently, I compile 1.1.1. I have no access to the original 1.1.0 files.
Perhaps you see my problem already. This causes a gap that cannot be bridged. Anyone who installed 1.1.0 cannot upgrade automatically.
I realize this is my own procedural error. I also realize that I could go to a client who installed 1.1.0 and get the files I need. I would rather avoid this though.
Is there a clever way to fix this for those people? Or, should I just have people uninstall version 1.1.0 and install the current version, then pay more attention to what I am doing in the future?
-Brent
