Filesize of manifest.xsf

[Ram Kaushik]

Hello all:

I noticed something interesting as I was rearranging elements in my
data source. The filesize of manifest.xsf and hence of the xsn file
increased about three-fold. As I was making several changes at the
same time, I'm having difficulty identifying which changes resulted in
this.

I've tried examining the manifest.xsf in an xml editor but am unable
to figure out reasons for the large file yet. Everything still works
OK so I'm not too worried but was curious about the reasons for the
increase in size.

Is InfoPath somehow storing "old" entries pertaining to the old
datasource before rearranging? Is there a way to "clean out" the
manifest.xsf safely?

Would appreciate any help - thanks!

Ram Kaushik

 

[Jim Budde]

I have seen it hold on to secondary datasource files that I removed, but it
for some reason retains them. You can remove the entries manually by
editing the xsf file in a text editor. Just make sure to make a backup of
it beforehand, you can VERY easily mess up your project by editing things
incorrectly.

 

[Ram Kaushik]

Jim, thanks for the response. I don't have any secondary datasources
in this form. When I open the manifest.xsf file in an xml editor, I
notice a few other interesting things.

1. There are xsf:xmlToEdit tags with item attributes pointing to "old"
xpaths that no longer exist on the form. (??)

2. The xsf:FragmentToInsert elements seem to be pretty large and are
sometimes pointing to "old" structures.

Like you indicated, I don't really want to change or delete anything
in manifest.xsf till I figure out what's going on. (especially since
everything works OK) Any other thoughts?

 

[Ram Kaushik]

Thanks for the insight, Greg.