Terms and Conditions

XAMARIN, INC.
XAMARIN COMPONENT STORE TERMS OF SERVICE 1.0
Introduction
1.1 All use of the Xamarin Component Store ("Xamarin Component Store") is subject to the terms and condition herein (collectively, ("TOS").
1.2 You ("User") accept the TOS by either (1) clicking to agree or accept where these options are presented, or (2) actually using the Xamarin Component Store. If User is accepting on behalf of User employer or another entity, User represents and warrants that: (i) User has full legal authority to bind User employer or such entity to the TOS; (ii) User has read and understands the TOS; and (iii) User agrees, on behalf of the party that User represents, to the TOS. If User does not have the legal authority to bind, do not click the "I Accept" button or use the Xamarin Component Store.
1.3 User may use Xamarin Component Store to browse, download and purchase subscriptions, products, tools and services (collectively ("Products"). Some of these Products may be offered by Xamarin while others may be made available by third parties. User agrees that Xamarin is not responsible for any Product that originates from a source other than Xamarin. User agrees that User is solely responsible for all fees associated with purchases User make on the Xamarin Component Store.
Xamarin Component Store
2.1 Xamarin may permanently or temporarily stop providing all or a portion of the Xamarin Component Store to User or to users generally at Xamarin’s sole discretion, without prior notice to User.
2.2 If Xamarin disables access to User’s account, User may be prevented from accessing the Xamarin Component Store, User account information and Products that are stored with User account.
2.3 Xamarin may make available to User various payment methods to facilitate the purchase of Products from the Xamarin Component Store. User agrees to abide by any relevant terms that govern the use of the particular payment processing method. Xamarin reserves the right to add or remove payment methods at its sole discretion.
2.4 Xamarin may discover Products on the Xamarin Component Store that violates the applicable Distribution Agreement or other legal agreements, laws, regulations or policies. User agrees that in such an instance Xamarin retains the right to remove those Products, in its sole discretion.
User Use of Xamarin Component Store
3.1 In order to access certain services in the Xamarin Component Store, User may be required to provide information, such as User’s name, address, and billing details. User agrees that any such information User provide to Xamarin will always be accurate, correct and up to date.
3.2 User agrees to use the Xamarin Component Store only for purposes that are permitted by the TOS and any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions. User agrees to comply with all applicable export controls. By using the Xamarin Component Store, User represents and warrants that User is not prohibited from receiving exports or services under US or other applicable export laws. User agrees to comply with all local laws and regulations regarding the download, installation or use of the Products.
3.3 User agrees not to attempt to access or access the Xamarin Component Store by any means other than through the interface that is provided by Xamarin, Inc. User specifically agree not to attempt to access or access the Xamarin Component Store through any automated means.
3.4 User agrees that User will not engage in any activity that interferes with or disrupts the Xamarin Component Store or the servers and networks which are connected to the Xamarin Component Store. User agrees that User will not use any of the Products in a way that interferes or disrupts any servers, networks, or websites operated by Xamarin or any third party.
3.5 User agrees that User will not reproduce, duplicate, copy, sell or distribute the Xamarin Component Store.
3.6 User agrees that User is solely responsible for, and that Xamarin has no responsibility to User or to any third party for, User’s use of the Xamarin Component Store and any Products, any breach of User’s obligations under the TOS, and for the consequences, including without limitation, loss or damage of any kind which Xamarin may suffer as a result of such use or breach.
3.7 User agrees to comply with any and all applicable tax laws, including the reporting and payment of any taxes arising in connection with User’s use of the Xamarin Component Store or the purchase of Products, and that the reporting and payment of any such applicable taxes are User’s responsibility.
3.8 User agrees that Xamarin or third parties own all right, title and interest in and to the Xamarin Component Store and the Products available through the Xamarin Component Store, including without limitation all applicable Intellectual Property Rights in the Products. "Intellectual Property Rights" means any and all rights existing under patent law, copyright law, trade secret law, trademark law, unfair competition law, and any and all other proprietary rights worldwide.
Open Source Products
Some components of Products may also be governed by applicable open source software licenses. In the event of a conflict between the TOS and any such licenses, the open source software licenses will prevail with respect to those components.
Updates
Products may communicate with Xamarin servers from time to time to check for available updates to the Products. By purchasing these Products, User agrees to such automatically requested and received updates. User agrees that Xamarin may collect certain personally identifiable information from users of the Products and Xamarin will have the right to compile and distribute statistical analyses and reports utilizing aggregated data derived from information and data obtained from User, users, other Xamarin customers and other sources.
6. Export Regulations
Products available on the Xamarin Component Store may be subject to export controls or restrictions by the United States or other countries or territories. User agrees to comply with all applicable United States and international export laws and regulations. These laws include restrictions on destinations, end users, and end use.
Indemnification
To the maximum extent permitted by law, User agrees to defend, indemnify and hold harmless Xamarin, its affiliates and their respective directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses, including attorneys’ fees, arising out of User’s use of the Xamarin Component Store, including User’s downloading, installation, or use of any Products, or User’s violation of the TOS.
Term and Termination
8.1 The TOS will continue to apply until terminated by either User or Xamarin as set out below.
8.2 If User wants to terminate the TOS, User may do so by ceasing User’s use of Xamarin Component Store and any Products purchased from the Xamarin Component Store.
8.3 Xamarin may at any time, terminate the TOS with User if: (A) User has breached any provision of the TOS; or (B) Xamarin is required to do so by law; or (C) Xamarin decides to no longer provide the Xamarin Component Store.
8.4 When the TOS terminate, Sections 3.6, 3.7, 3.8, 4, 5, 6, 7, 8.4, 9, 10 and 11 will survive.
DISCLAIMER OF WARRANTIES
9.1 SUBSCRIBER EXPRESSLY UNDERSTANDS AND AGREES THAT THE USE OF THE XAMARIN COMPONENT STORE AND ANY PRODUCTS OBTAINED THROUGH THE XAMARIN COMPONENT STORE IS AT SUBSCRIBER’S SOLE RISK AND THAT THE XAMARIN COMPONENT STORE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND, TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW.
9.2 USE OF THE XAMARIN COMPONENT STORE AND ANY PRODUCTS OBTAINED THROUGH THE USE OF THE XAMARIN COMPONENT STORE IS AT SUBSCRIBER’S OWN DISCRETION AND RISK AND SUBSCRIBER IS SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM, MOBILE DEVICE, OR OTHER DEVICE, OR LOSS OF DATA THAT RESULTS FROM SUCH USE.
9.3 TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, XAMARIN FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, WITH RESPECT TO ANY AND ALL PRODUCTS AND THE XAMARIN COMPONENT STORE.
9.4 NONE OF THE PRODUCTS ARE INTENDED FOR USE IN THE OPERATION OF NUCLEAR FACILITIES, LIFE SUPPORT SYSTEMS, EMERGENCY COMMUNICATIONS, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL SYSTEMS, OR ANY OTHER SUCH ACTIVITIES IN WHICH CASE THE FAILURE OF THE PRODUCTS COULD LEAD TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE.
LIMITATION OF LIABILITY
SUBSCRIBER UNDERSTANDS AND AGREES THAT XAMARIN AND ITS AFFILIATES SHALL NOT BE LIABLE TO YOU UNDER ANY THEORY OF LIABILITY (WHETHER CONTRACT, TORT INCLUDING NEGLIGENCE OR OTHERWISE) FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL CONSEQUENTIAL OR EXEMPLARY DAMAGES THAT MAY BE INCURRED BY YOU THROUGH USE OF THE XAMARIN COMPONENT STORE OR ANY PRODUCTS OBTAINED FROM THE XAMARIN COMPONENT STORE, INCLUDING ANY LOSS OF DATA, WHETHER OR NOT XAMARIN OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING.
General Terms
11.1 The TOS constitute the whole legal agreement between User and Xamarin and govern User’s use of the Xamarin Component Store and Products, and completely replace any prior agreements between User and Xamarin in relation to the Xamarin Component Store, Products, and Professional Services.
11.2 If Xamarin does not exercise or enforce any legal right or remedy which is contained in the TOS (or which Xamarin has the benefit of under any applicable law), this will not be taken to be a formal waiver of Xamarin’s rights and that those rights or remedies will still be available to Xamarin.
11.3 If any court of law, having the jurisdiction to decide on this matter, rules that any provision of the TOS is invalid, then that provision will be removed from the TOS without affecting the rest of the TOS. The remaining provisions of the TOS will continue to be valid and enforceable.
11.4 No person or company will be third party beneficiaries to the TOS.
11.5 The rights granted in the TOS may not be assigned or transferred by User, whether by operation of law or otherwise, without the prior written approval of Xamarin.
11.6 The TOS will be governed by the laws of the State of California without regard to its conflict of laws provisions. User and Xamarin agree to bring any and all actions under the TOS in exclusively in a court of competent jurisdiction located within the county of Santa Clara, California to resolve any legal matter arising from the TOS and each party agrees to submit to the exclusive jurisdiction of such court and waives all objections to such venue.

You must agree to the Terms of Service to download components.

Component Terms and Conditions

TMS component license agreement

TMS component license agreement between

TMS software and holder of the component license.

This license applies to single developer, small team and site licenses
except where explicitly noted. If you hold a single developer license,
then the term “*licensed developers*” in this document applies to the
single developer holding the license. If you hold a small team
license, then the term “*licensed developers*” in this document applies
to the two developers holding the license. If you hold a site
license, then the term “*licensed developers*” in this document applies
to all developers within the company holding the license.

The license of the component gives all license holders the right to:

use the component for development of applications or any type of
software module in general by the licensed developers.

sell any commercial compiled application with the control, published
by the company holding the license.

make modifications to the source code of component for own use.

use the component and source code on all development systems used by
the licensed developers.

request future versions of the component at any time either through
the web or by email for
2 years after purchase. After expiry of the registration TMS software
can no longer provide any old version of software, documentation or
samples. TMS software is not a backup service and expects backups to be
made by the licensed user.

access to priority email support by the licensed developers during
the license period.

sell any number of applications in any quantity without any additional
run-time fees required

The license of the component gives SITE LICENSE holders the right
to:

change at any time the number of developers using the TMS software
components within the company holding the license

notify TMS software at any time to allow new developers within the
company to access the priority email support

allow any number of developers within the company holding the license
to access the web based interface for obtaining product updates.

The license agreement prevents all license holders from:

distributing parts or full source code of any component from TMS
software.

using parts or full source code of components from the TMS software
for creating any type of other components that are distributed or sold
with or without source code.

changing the source code of any component from TMS software and sell
or distribute this as a modified product.

creating a descendant compiled product such as OCX or ActiveX control
and sell or distribute this as a product

using the control in applications sold with different publisher name
than the company holding the license

The license agreement prevents SMALL TEAM LICENSE holders from:

transferring the license to another company

using the components by more than two developers in the company
holding the license

The license agreement prevents SINGLE DEVELOPER LICENSE holders
from:

transferring the license to another developer

transferring the license to another company

using the components by multiple developers in the company holding the
license

The license agreement terminates immediately after violation of any of
the terms and conditions described

Disclaimer:

THIS SOFTWARE IS PROVIDED TO YOU "AS IS" WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESSED OR IMPLIED INCLUDING

BUT NOT LIMITED TO THE APPLIED WARRANTIES OF MERCHANTABILITY AND/OR
FITNESS FOR A PARTICULAR PURPOSE.

YOU ASSUME THE ENTIRE RISK AS TO THE ACCURACY AND THE USE OF THE
SOFTWARE AND ALL OTHER RISK ARISING OUT OF THE

USE OR PERFORMANCE OF THIS SOFTWARE AND DOCUMENTATION.

tmssoftware.com bvba SHALL NOT BE LIABLE FOR ANY DAMAGES WHATSOEVER
ARISING OUT OF THE USE OF OR INABILITY TO

USE THIS SOFTWARE, EVEN IF tmssoftware.com bvba HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL
tmssoftware.com bvba BE LIABLE FOR ANY

CONSEQUENTIAL, INCIDENTAL, DIRECT, INDIRECT, SPECIAL, PUNITIVE, OR OTHER
DAMAGES WHATSOEVER, INCLUDING BUT NOT

LIMITED TO DAMAGES OR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION,
LOSS OF BUSINESS INFORMATION, OR OTHER

PECUNIARY LOSS, EVEN IF tmssoftware.com bvba HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

You must agree to the Terms of Service to download this component.

Thanks for downloading TMS FlexCel Studio for .NET!

If you haven't already, check out the Getting Started documentation for TMS FlexCel Studio for .NET here.

APIMate will show you the needed code (in C# or VB.NET) to create the file. Full source for APIMate is included, so you can study how it works too.

2. A reporting engine

This is a higher level component for creating xls or xlsx files. When using it, you create a file in Excel which will be
used as a template where the reporting engine will fill the values. Internally, this component uses the xls/x engine to create the files,
but it allows you to do it in a more declarative way. It allows you to use Excel as the report designer.

Add a named range (in the ribbon-> Formula tab->Name Manager). Name it "__Customer__", and
make it go from A1 to C1. This name must have 2 underscores at the beginning and end, and the
text between the underscores must be the same as the text between <#.... .> tags. It tells
FlexCel which rows are used for each record in the database.

Release Notes

New method [[vcl T]]XlsFile.AddAutoShape to add autoshapes with the API. The new method allows you to add an autoshape to a file. As usual APIMate will provide you with the needed code.

Support for Visual Studio 2017 RC. Setup now installs in Visual Studio 2017.

Support for .NET Core 1.1. Project.json was changed to a csproj in order to build in 1.1.

Support for drawing mirrored images when rendering. Now when a bitmap is flipped vertically or horizontally, FlexCel will also draw it like this when exporting it.

New method TCellAddress.DecodeColumn. This method is provided for symmetry with the existing TCellAddress.EncodeColumn, but it is normally not required as you can use TCellAddress to get the full cell address string for a row and a column. This method could be used in the rare case you only wanted the column string and not the full cell address.

Breaking Change: Support for losslessly rotated JPEG images. Now when inserting JPEG images that are rotated via the "orientation" attribute in the JPEG file, FlexCel will automatically rotate the image so it appears with the desired orientation in Excel.
Before FlexCel behaved as Excel 2010 or older, just entering the image as is, so Excel would show it rotated. Now it works like Excel 2013 or newer, where we rotate the image in Excel to compensate. All orientation values are supported, included mirrors. Note that this change might be breaking if you were manually rotating the images before entering so they would show fine. If you ware rotating the images manually, you should remove the code as now it will be done automatically. There is also a new method ImageUtils.GetJPEGOrientation which you can use to tell if a JPEG image is rotated or not.

Bug Fix. When autofitting a column which contained multiple lines but the cell was set to not wrap, FlexCel would consider that the cell could wrap and so end up with a smaller column width than needed.

Bug Fix. When replacing hyperlinks in a shape with a report there could be an exception.

Bug Fix. Support for reading xlsx files with custom properties with repeated names or empty names.

New on v 6.13.0.0 - January 2017

Support for rendering Right-To-Left sheets. Now FlexCel can export sheets where A1 is at the right side of the page and the cells grow to the left instead of to the right. A new property XlsFile.SheetIsRightToLeft allows you to read or write the right to left state of the sheet directly without needing to use SheetOptions. APIMate will now also suggest SheetIsRightToLeft instead of SheetOptions for RTL sheets.

Improved right to left support for text. Now FlexCel will support mixed right to left and left to right text more as the Unicode BIDI algorithm defines it. The Context property of the cell is now also used to figure out if it is rtl text embedded in ltr text or ltr text embedded in rtl text.

New static properties [[vcl T]]ExcelFile.CompressionLevel, [[vcl T]]FlexCelConfig.XlsxCompressionLevel and [[vcl T]]FlexCelConfig.PdfPngCompressionLevel. Properties ExcelFile.CompressionLevel and FlexCelConfig.XlsxCompressionLevel are the same and control the zip compression level used to creating xlsx files. FlexCelConfig.PdfPngCompressionLevel controls the compression level for pdn and png files. FlexCel uses "zcDefault" zlib compression level, which normally gives the best ratio between speed and size. But note that Excel itself uses zcFastest when saving xlsx files, resulting in faster saves but also bigger files. While you won't probably want to change the defaults, now you can. Note: We require .NET 4.5 or newer for this property to work.

New static property FlexCelConfig.DpiForReadingImages. This new property FlexCelConfig.DpiForReadingImages allows you to force a resolution in the images you are loading. Normally FlexCel will use the resolution stored in the images to calculate the desired width in inches, but now you can override whatever is saved in the file by changing this property.

New implementation of wildcard matching for all functions that use them. The new algorithm to match patterns like * or ? and used in functions like MATCH or COUNTIF is now much faster and can use much less memory in pathological cases.

New method FlexCelReport.Run(Stream templateStream, Stream outStream, TFileFormats fileFormat). This method allows you to specify the resulting file format when running a report to a stream.

Better handling of expressions or formats defined both in an included report and the master report. Now when an included report has the same expressions or formats defined in the config sheet as the master, those local definitions will be used, instead of raising an error of repeated formats/expressions.

Breaking Change: Better handling of image resolution in reports. Now when adding an image to a report and resizing it, FlexCel will take in account the image resolution if it is saved in the image. If the image doesn't have a resolution saved, FlexCel will use the screen resolution.
You can revert to the old way of assuming a resolution of 96 dpi for all images by changing FlexCelConfig.DpiForReadingImages

Bug Fix. When exporting to HTML and a merged cell covered hidden rows or columns, the resulting html could be wrong.

Bug Fix. When exporting to HTML with embedded SVG images, the fill colors in the SVG images would be wrong if there were gradients.

Bug Fix. When exporting to SVG, text in controls or shapes could go a little lower than it should.

Bug Fix. The formula parser would fail to detect some unicode characters as valid characters for a sheet name or named range.

Better display of complex numeric formats. Now we handle some complex formatting the same as Excel does, handling also invalid formats which Excel doesn't allow better.

Bug Fix. Now FlexCel allows names with spaces as macro identifiers when loading files. While those aren't valid names and Excel won't let you enter them directly, you can enter them with VBA code, and FlexCel was refusing to read those files. Now FlexCel will open them correctly.

Bug Fix. In .NET Core we could fail to read formulas

Bug Fix. When a file had "Precision as displayed" set and there were cell formats including percentage signs, the numbers might be rounded wrong.

Bug Fix. There could be an stack overflow when a camera object rendered a range of cells which included the cells where the camera object was.