fazza
Posts: 12
Joined: Tue May 19, 2009 11:22 am

Sequence Number and Folder Synchronize

Sequence Number
I have an aip project that everytime i added a file, the sequence number is a duplicate number from other file. There is no way to find the seed number or to find out what is the next sequence number. I did what people suggested, re-adding the files or editing the table editor, but in the future the problem rise again. I would say this is a workaround, not a solution. This problem somehow becomes a frustation within our developer.

Current behaviour:
When file2 is added, a sequence number was given to file2. The sequence number can be a duplicate from file1. When the project is build, file2 is not added to the msi cab and resulting an error during installation.

Expected behaviour:
When file2 is added, a sequence number was given to file2. The sequence number can be a duplicate from file1. When the project is build, resequencing is being performed. Therefore file1 and file2 will be given with different sequence number.


Synchronize Folder
The synchronize folder option adds all the files to the xml when saved. During check-in the xml difference will be huge due to different sequence and different files added. The synchronize folder should only synchronize but does not add the files to the xml. This will create a clean xml (.aip) file.

Current behaviour:
When there are files in the folder, the synchronize will add all the files and add new entry to the xml files.

Expected behaviour:
When there are files in the folder, the synchronize will add all the files but does not add it to the xml files.


I hope the problem mentioned is clear. Let me know if you need more detail.

thanks,
Faried
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Sequence Number and Folder Synchronize

Hello Faried,

The duplicate sequence number occurs during conflict resolving or merging in versioning systems.
Both have version 1.1 of installer.aip
Developer A adds somefile32.exe to the project, next sequence number is 203, doesn't commit yet
Developer B adds somefile64.exe to the project, next sequence number is 203, doesn't commit yet either.
Now they both commit, merging occurs, somefile32.exe and somefile64.exe now have a duplicate sequence number.
To prevent this, simply instruct your developers to carefully merge data and check for duplicate sequences when doing so.

Regarding folder sychronization, synchronized files need to stay inside the project file.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
fazza
Posts: 12
Joined: Tue May 19, 2009 11:22 am

Re: Sequence Number and Folder Synchronize

GabrielBarbu wrote:The duplicate sequence number occurs during conflict resolving or merging in versioning systems.
Both have version 1.1 of installer.aip
Developer A adds somefile32.exe to the project, next sequence number is 203, doesn't commit yet
Developer B adds somefile64.exe to the project, next sequence number is 203, doesn't commit yet either.
Now they both commit, merging occurs, somefile32.exe and somefile64.exe now have a duplicate sequence number.
To prevent this, simply instruct your developers to carefully merge data and check for duplicate sequences when doing so.
How can we merge it carefully? I assume you just increase the file somefile64.exe to 204 manually. Am I correct? But when I add a new file to the project file, the sequence number given will be 204. That means from now on, I have to keep on updating the sequence number. Now that can be a problem when using sync folder because the files is not yet added, therefore the sequence number is still unknown.
GabrielBarbu wrote:Regarding folder sychronization, synchronized files need to stay inside the project file.
Is there a reason why the synchronized files need to be in the project file?

Our case is:
In PC devA, the sync folder contains 100 files. (he is working on project A)
In PC devB, the sync folder contains 200 files. (he is working on project B)
In PC devC, does not have this synchronized folder locally. (he is an admin)
When they all check-in to the source control at different time, the project file will changes hugely. As a matter of fact, there are only 1 or 2 files being added. From history perspective, this is hard to see, what has been change to the project file. What we really interested at is the folder in the Server not in developer PC. Our temporary solution is to delete all the files in the sync folder before check in.

best regards,
Faried
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Sequence Number and Folder Synchronize

Hello,
How can we merge it carefully? I assume you just increase the file somefile64.exe to 204 manually. Am I correct? But when I add a new file to the project file, the sequence number given will be 204. That means from now on, I have to keep on updating the sequence number. Now that can be a problem when using sync folder because the files is not yet added, therefore the sequence number is still unknown.
It is recommended that only one developer works on the project at a time. Simultaneous editing is not recommended for the very reason duplicate sequences occur.
This being said, Advanced Installer knows which is the last sequence. It will see your 204 sequence which you manually added and will insert the next file with the 205 sequence.
Is there a reason why the synchronized files need to be in the project file?
Advanced Installer needs to know about which files belong to which components, which belong to which features. If files are not inserted in the project, upon synchronization new components will be generated (with different GUIDs), which is not a valid behavior.

Please let me know if I have misunderstood your issue.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
waspy
Posts: 64
Joined: Fri Oct 03, 2008 10:58 am

Re: Sequence Number and Folder Synchronize

Dear Guys,

This is a very interesting thread. We hit the problem of sequencing from time to time. It is not clear if this is a problem inherited from the previous versions and specific to a project or something that is not functioning properly. The fact is that it creeps in somehow from time to time even in the systems under strict source control where simulatanious editing is restricted. In this case we are forced to send the file to you or try fixing it ourselves giving the problematic sequence a large number. Just as of a curiosity... wouldn't it be possible to detect the duplicate sequences when the project is loaded and save them in the correct order afterwards? I think that would save all of us a big trouble :).

As for the sync folder... Indeed this feature works as designed, but I think it would be such a great idea to add an option to control this behavior. In many cases the "on-the-fly" synchronization is very useful. Let me give you an example... In the end of every iteration we receive so called customization files (a number of files that are changed quite frequently by the users). We know that we just need to include all of them in one particular folder in out installation package. We have several version of the installer (platform specific, development and integration versions). Firstly, to implement changes this synchronization needs to be preformed manually for every individual project. Secondly, we need to make sure that person who performs the project modifications has all the files, because otherwise the folders will get out of sync. Thirdly, the files come very late and even if all the files are in place, somebody has to do the synchronization again at the very last moment. This is just very inconvenient. So what we do now is we simulate the "on-the-fly" inclusion, by removing all the files from the Customizations folder when editing the installer project. In this case no synchronization is performed and files are included on the build server during project compilation. Of course you know all the specifics of this process and different GUIDs can cause the problem (under which condition?), but it works perfectly for now, so wouldn't be an idea to make a nice feature out of it?

Kind regards,
Alexei
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Sequence Number and Folder Synchronize

Hi Alexei,
wouldn't it be possible to detect the duplicate sequences when the project is loaded and save them in the correct order afterwards?
This improvement is already on our TODO list and it will be available in a future version.
As for the sync folder... Indeed this feature works as designed, but I think it would be such a great idea to add an option to control this behavior. In many cases the "on-the-fly" synchronization is very useful.
I'm not sure I understand what you mean. Can you please give me an example of how this feature would work?

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
waspy
Posts: 64
Joined: Fri Oct 03, 2008 10:58 am

Re: Sequence Number and Folder Synchronize

Hello Cosmin,

Thanks for looking into it... What I had in mind was a checkbox that would control the synchronization behavior (e.g. "Include in project"). If it is checked, the file references are included in the project when it is saved, otherwise - the actual files are included when the project is build and references are NOT saved in the project.

Kind regards,
Alexei
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Sequence Number and Folder Synchronize

Hi Alexei,

We will consider including this improvement in a future version. Thank you for your suggestion.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Feature Requests”