TiJa's Posts

Hi, The first problem should be solvable by using the %CSIDL_STARTMENU% variable, which resolves to a particular user's start menu location when ran from the user's context, see: http://msd... See more...
Hi, The first problem should be solvable by using the %CSIDL_STARTMENU% variable, which resolves to a particular user's start menu location when ran from the user's context, see: http://msdn.microsoft.com/en-us/library/bb762494(VS.85).aspx http://msdn.microsoft.com/en-us/library/bb762181(VS.85).aspx I found an example in VBscript at this site: http://www.pcreview.co.uk/forums/thread-416978.php Bye! Tim
Hi, I am not sure if the ThinApp tooling allows this. However, there are several other methods for doing so, see: http://blogs.technet.com/heyscriptingguy/archive/2004/11/11/can-i-pin-a-fil... See more...
Hi, I am not sure if the ThinApp tooling allows this. However, there are several other methods for doing so, see: http://blogs.technet.com/heyscriptingguy/archive/2004/11/11/can-i-pin-a-file-to-the-start-menu-by-using-a-script.aspx http://blogs.technet.com/deploymentguys/archive/2009/04/08/pin-items-to-the-start-menu-or-windows-7-taskbar-via-script.aspx Best regards!
You'll also need to check the isolation mode of the two registries to be sure that they merge properly. If the Word registry is a full isolation mode, it will not recognize the overlapping Visio ... See more...
You'll also need to check the isolation mode of the two registries to be sure that they merge properly. If the Word registry is a full isolation mode, it will not recognize the overlapping Visio registry keys. Check out the ThinApp manual on p46 for the literal example of Visio 2007 (with Office 2003). You'll probably want to use WriteCopy as a quick test to see if it works in that scenario. http://www.vmware.com/pdf/thinapp402_manual.pdf
Perhaps I should emphasize that this is not an issue but rather the intended behaviour (no irony intended).
From my experience with application virtualization: there is no easy way to do this. What you are seeing is precisely what you want to achieve with application virtualization: not contaminating t... See more...
From my experience with application virtualization: there is no easy way to do this. What you are seeing is precisely what you want to achieve with application virtualization: not contaminating the system with application files such that the application is easier to maintain. Hence, it is logical that system applications can't see the virtualized application, because it is not "really installed" in one form or the other. That being said, your specific Word/Visio problem is as follows: as far as I have understood, Word and Visio communicate through eachother using COM(+) and its derivates such as OLEv2. In order to let "the system application recognize the virtual application", you would need to link the virtualized COM objects of Visio to the system (for a physically installed application, this basically comes down to creating a bunch of not-to-user-friendly registry keys). That's not possible because the system cannot look inside the ThinApp'ed application and say "hey, I see you have some COM objects stored there". Therefore, what you need to do is make sure that Word can see the COM registrations of Visio and Visio those of Word. You can only achieve this by running both applications inside the same virtual environment. That can be done in two ways: - either create a new ThinApp package that contains both Word (or the entire Office suite) and Visio - use linked applications to merge the Visio virtual environment with the Word virtual environment. It's possible that there is another approach to this problem (yet I don't immediatelly see one), so I'll glady hear what other people can suggest. Hope that helps! Tim
Hey Saxion, Can you start by providing us a little more information? Are you starting the applications locally or over a network share? Are you using IIS for the AppSync update serv... See more...
Hey Saxion, Can you start by providing us a little more information? Are you starting the applications locally or over a network share? Are you using IIS for the AppSync update server (what location did you provide?). How are the updates named? What are examples of error messages that you are receiving? Bye, Tim