VMware Horizon Community
btrabue
Enthusiast
Enthusiast
Jump to solution

Side by Side thinapp update produces black cmd screen

I've updated a thinapp using the side by side updating method.  The application opens fine to the updated version but there is a black CMD screen that comes up first and it stays open.  Once the thinapp has opened we have found that it is ok to close that CMD screen.  Is there anything that I can do to prevent this black screen from appearing?  I know that as we move along and update some thinapps that this will raise questions among the users.  Is side by side the best way to update a thinapp without bothering the users?  Thanks!!

Reply
0 Kudos
1 Solution

Accepted Solutions
pbjork
VMware Employee
VMware Employee
Jump to solution

And that is true.. It is the Data Container which contains the update, therefore should it be updated with in-place (or Side by Side) update..

Please have a look at this blog post: http://blogs.vmware.com/thinapp/2012/01/in-place-update-using-a-separate-data-container.html

View solution in original post

Reply
0 Kudos
3 Replies
pbjork
VMware Employee
VMware Employee
Jump to solution

I've seen this same behavior if my package has a separate data container sharing the same name as my Entry Point, i.e. Mozilla Firefox.exe and Mozilla Firefox.dat. Is this true with your package?

Reply
0 Kudos
btrabue
Enthusiast
Enthusiast
Jump to solution

Yes, that is exactly true.  I thought that if I was doing a side by side update that the dat files should be the same name with the exception of the .dat.1, .2, etc.  Is this true?

Reply
0 Kudos
pbjork
VMware Employee
VMware Employee
Jump to solution

And that is true.. It is the Data Container which contains the update, therefore should it be updated with in-place (or Side by Side) update..

Please have a look at this blog post: http://blogs.vmware.com/thinapp/2012/01/in-place-update-using-a-separate-data-container.html

Reply
0 Kudos