# Tuesday, May 13, 2014

Starting with Stylus Studio X15 Release 2 is possible to transfer a license from one computer to another without contacting our support team. 

When you activate Stylus Studio we build a unique hardware identifier and passed to our license server, this is helpful for tracking software usage with large organizations which may run hundreds of Stylus Studio instances. If you work on multiple workstations and try to activate your Stylus Studio license on a different hardware you get stuck on the following error:

This is no longer the case, just run the Stylus Studio un-installer ( Control Panel ->  Unistall Programs) and you are free to re-install on a different system.

There are actually two additional methods for deactivating a license: 

  • From inside the IDE, click on Help -> Deactivate From this Computer.  This command is disabled in evaluation mode.

  • Using a command line switch with the Stylus Studio executable



Let us know what you think about this new feature

Ivan Pedruzzi

Stylus Studio Team

posted on Tuesday, May 13, 2014 12:31:34 AM (Eastern Daylight Time, UTC-04:00)  #    Comments [0] Trackback
# Wednesday, May 7, 2014
May 2014 - X15 Release 2 is Here!
The Stylus Studio team is very excited to share the latest and greatest version of Stylus Studio with you. Stylus Studio X15 Release 2 adds support for the latest in XML technologies while increasing performance and productivity.

Read and click the links below to find out more about Stylus Studio X15 Release 2 including features, availability and more.

X15 Release 2

Stylus Studio X15 Release 2 is now available. This latest update includes Saxon, DataDirect XQuery, Apache FOP 1.1 integration, major performance enhancements through support for Oracle Java 1.8, and more. See all of the details on this update on our website.

AUP Subscribers

Stylus Studio X15 Release 2 is available free of charge to all active Stylus Studio AUP Subscribers. To download X15 Release 2, Click Here. If you are not an AUP subscriber, you can learn more about AUP on our website.

Stylus Studio X15 Release 2 Is Now Available
IVI Technologies announced the immediate availability of the Stylus Studio X15 Release 2 XML Enterprise Suite. Read the full press release.
Visit the XML Editor Blog
The Stylus Studio team has always enjoyed publishing tutorials, insightful articles and other helpful tips for our users. Check out the blog for the latest.
See The Best Articles of the Year
Get a summary of the best Stylus Scoop articles and posts from 2013! Check out any articles you may have missed.


Don't want any more emails? Go to the Unsubscribe Page

Copyright © 2014 IVI Technologies Inc. All Rights Reserved.

This message was sent because you have expressed interest in Stylus Studio through the Stylus Studio website. In accordance with our Privacy Policy, if you would prefer not to receive further notifications or email communications of this type, please go to the following web page and update your subscription profile, or contact us through postal mail at: IVI Technologies Inc., c/o Stylus Studio Consumer Affairs Office, 8672 SW 40 Street, Suite 206, Miami, FL,33155, USA.

View the trademarks, service marks, or registered trademarks of DataDirect Technologies in the U.S. and other countries. Any other trademarks or service marks contained herein are the property of their respective owners. All rights reserved.

posted on Wednesday, May 7, 2014 11:27:45 AM (Eastern Daylight Time, UTC-04:00)  #    Comments [0] Trackback
# Friday, May 2, 2014

We received an interesting question on SSDN which deserves more attentions then a simple few lines response

The original post can be found here

Here is a way to approach the problem. 

First we need to add a node with an empty pattern to the custom conversion which will catch all unexpected rows. 

Then we can build a schema from the converter's output which will be used to validate the document and to make sure no unexpected element are present.

At last we can build a simple XML pipeline which converts the fixed-width data to XML and performs validation against the schema. 

We can test the pipeline directly in Stylus Studio and when we are ready to deploy we can can just copy our project folder into XML Pipeline Server (http://www.xmlpipelineserver.com/) and we are ready to go.

XML Pipeline Server loads the pipeline and creates folder for each input and output blocks,  it monitors the folder bound to the input and triggers the pipeline execution as soon as a new file arrives.

If you like to know more about XML Pipeline Server drop us a line at stylussuport@ivitechnologies.com

Ivan Pedruzzi
Stylus Studio Team

posted on Friday, May 2, 2014 10:23:16 AM (Eastern Daylight Time, UTC-04:00)  #    Comments [0] Trackback