MarkOviedo's Posts

The Problem : I am trying to troubleshoot a ThinApp application package. The package has required links to Crystal Runtime 2008 SP1 and .NET Framework versions 2.0, 3.0, 3.5 SP1. The package run... See more...
The Problem : I am trying to troubleshoot a ThinApp application package. The package has required links to Crystal Runtime 2008 SP1 and .NET Framework versions 2.0, 3.0, 3.5 SP1. The package runs successfully on a Windows XP SP2 machine, but on a Windows Vista SP1 machine, it crashes when trying to show a Crystal report in the viewer. The package was built with ThinApp 4.0.3. My Troubleshooting Steps : I copied the LogMonitor.exe and supporting dll's to a Windows Vista SP1 test client. When I started the application package, the log file becomes so large that the application failed to launch. I then checked the Suspend box in LogMonitor, and now when I launch the application package, it crashes immediately. Some Relevant Notes : I had built roughly the same package with ThinApp 4.0.1 trialware and did not run into this issue. The app packaged under 4.0.1 ran successfully under Windows XP and Vista machines. In both cases, I had built all packages on a VM Workstation running Windows XP SP2. My Question : How do I troubleshoot this?
In our deployment model, we build ThinApp packages at our company and then deploy them out to different servers at customer intranet sites. We have been able to leverage the ThinApp scripting cap... See more...
In our deployment model, we build ThinApp packages at our company and then deploy them out to different servers at customer intranet sites. We have been able to leverage the ThinApp scripting capability to externalize basically any file in the package. This allows us to build 1 core package, deploy it at multiple customer sites, and then just change any .config files outside of the package for each customer. This greatly simplifies the management of our packages, since we just need to build one version of the package and then can configure it per customer via configuration files. We have been experimenting with the AppSync capability, and have found that it would be especially useful to externalize the AppSync URL in much the same way we can with our configuration files. This would open many doors for us in terms of flexible deployments. Namely, we could create a package at our company, test it internally by pointing to a local web server, then stage that package out to a customer site, and just update the AppSync URL to point to their customer web server. Another common scenario is that we will deploy a ThinApp package into a customer test environment, and then need to push the same package into the customer's live environment. We would like to be able to move the package from the test web server to the live web server, and just update the AppSync URL in the live environment to point to the live web server. Is it possible to do this today with ThinApp? If this needs to be a feature request, where do I post it?