Anonymous sequence an clientgen

Question

Hi there!
The clientgen ant-task has problems when using anonymous sequences like
<element...
<complexType>
<sequence maxOccurs="unbounded">
<element name="..."..
<element name="..."..
</sequence>
</complexType>
</element>
It will generate only one setter and getter for any of the inner elements of the
sequence, instead of an array of elements, allowing to specify a larger number
of elements.
I think, I found a hint in the documentation that this is the fact and clientgen
is not able to handle this.
However, I have a fixed schema and need to handle this. Is there any workarround?
greetings
Heiner

Answer 1

Sorry for the delay in getting back to you.
Once you start changing hands so many times of (a calls b, which calls c, which calls d...), it gets hard to track.  Generally speaking once outside you stay outside, but with App-V 5 the VFS is open to read/execute and its possible the exe is never
actually inside, you just think it is because the .hta opens. 
Try to lower the number of actions going on.  Start in the VE (by using powershell, and confirm you are inside by evaluating get-appvclientpackage "name" to see the inuse property is true.  Once there, run the exe manually with the options
(assume passed through command line).  Does it work?  Then back up, run the hta, and run, does that also work?
If you do one step at a time, and aren't sure if you are in the VE you can always evaluate the powershell command again, or check the file system/registry system appears as virtualized.
When someone refers to VFS vs PVAD capturing, they are referring to the DIR path you put into the sequencer GUI.  You can quickly tell by looking at your package.  If the files captured are immediately under Root, you captured to the PVAD. 
If they are under Root\VFS\ you captured to the VFS.  Here is a good link to read, this blog is definitely one (of many) to check out, a lot of great information:
http://blogs.technet.com/b/gladiatormsft/archive/2014/08/25/app-v-5-installing-to-the-pvad-don-t-do-it-yes-i-said-it.aspx
That said, you should upgrade to SP3, and SP3 actually hides the whole PVAD vs VFS option, defaulting everything to VFS.  If you did package to PVAD, to be honest it might just be worth your time to redo in VFS before other troubleshooting.  VFS
captures have a better (generally speaking) rate of success.
Let me know if I'm not clear on anything.