# Wednesday, September 17, 2014


Last year I wrote a blog post on on how to run Stylus Studio installer in silent mode titled How to Run Unattended Stylus Studio Install

Here I will show you how to run the uninstaller.

First you need to create a response file running the uninstaller, using the following commands which creates the response file at c:\uninstall1.iss.  
It really important to use a path with ASCII letters only.

SET X15_R2_GUID={CE879889-18D1-410C-8FEB-561243541860} 
SET UNINSTALL_FOLDER=c:\Program Files (x86)\InstallShield Installation Information\%X15_R2_GUID% 
SET UNINSTALL=%UNINSTALL_FOLDER%\Setup.exe 
"%UNINSTALL%" -uninstall /r /f1c:\uninstall1.iss 

Once the un-installation process is completed you can perform the un-installation in silent mode
 
SET X15_R2_GUID={CE879889-18D1-410C-8FEB-561243541860} 
SET UNINSTALL_FOLDER=c:\Program Files (x86)\InstallShield Installation Information\%X15_R2_GUID
SET UNINSTALL=%UNINSTALL_FOLDER%\Setup.exe 
"%UNINSTALL%" -uninstall /s /f1c:\uninstall1.iss 

Notice that each Stylus Studio version and edition use a different GUID; these are stored in a hidden folder
c:\Program Files (x86)\InstallShield Installation Information

If you need help to locate your Stylus Studio GUID post a message on the Stylus Studio Developer Network

Hope this helps
Ivan Pedruzzi
Stylus Studio Team


posted on Wednesday, September 17, 2014 2:39:07 PM (Eastern Daylight Time, UTC-04:00)  #    Comments [0] Trackback
# Monday, August 04, 2014

Just a quick note to let you know that we have released a Stylus Studio update (1928d) which bundles the latest Saxon processors.

Here you can find what was fixed

Ivan Pedruzzi
Stylus Studio Team
posted on Monday, August 04, 2014 7:26:51 AM (Eastern Daylight Time, UTC-04:00)  #    Comments [0] Trackback
# Wednesday, May 28, 2014


Before build 1928b Stylus Studio could not run XSLT transformations using external processors, which output very large files.  The wiring was not designed to scale and the scenario output URL was not taken in consideration.

Our long time customer Yitzhak Khabinsky was working on a project which required transforming a 500 MB XML file into 650 XML output.  Their deployment is Microsoft.NET therefore XslCompiledTranform is the XSLT processor used in production. They tried to test the transformation in Stylus Studio without success.

Yitzhak's team sent us a test case and asked if we could make it work. After few days of hard work we came up with a solution which provides great benefits to any customer running command line processors.

1)  We have wired the transformation output file (either the output URL or the temporary file) into the Preview window, doing so Stylus Studio now can load a large amount of data in the Text Preview with minimal memory consummation, thanks to our custom memory manager.

2)  We introduced a dialog which shows the progress and allows canceling the operation.

 

In the following screenshot Stylus Studio is loading 1.3 GB XML output file in the Preview Window, notice in the task manager that the memory allocation picks no more than 90 Mb.




posted on Wednesday, May 28, 2014 9:04:50 PM (Eastern Daylight Time, UTC-04:00)  #    Comments [0] Trackback