============================================================================= The Endeca URL Optimization API for the Endeca RAD Toolkit for ASP.NET GENERAL (2.1.2) - Updated: November 2011 - The release notes may have been updated since the release date. Access the Product Downloads section of the Endeca Developer Network (https://eden.endeca.com) for the most recent version of the release notes. KNOWN ISSUES (2.1.2) Documentation: * The documentation for this release has not been updated. Updated documentation may be provided in a future release if necessary. Please see the EDeN knowledge base for the most recent documentation. COPYRIGHT (2.1.2) Copyright and patent information has been updated since the previous release of this software. The current copyright, trademark, and patent information is as follows: Copyright (c) 2001-2011 Endeca Technologies, Inc. All rights reserved. Portions of this software are subject to third-party rights, including: Corda PopChart(R) and Corda Builder(TM) Copyright (c) 1996-2005 Corda Technologies, Inc. Outside In(R) Search Export (c) 2011 Oracle. All rights reserved. Rosette(R) Globalization Platform (c) 2003-2005 Basis Technology Corp. All rights reserved. Teragram Language Identification Software (c) 1997-2005 Teragram Corporation. All rights reserved. Endeca, the Endeca logo, Guided Navigation, MDEX Engine, Find/Analyze/Understand, Guided Summarization, Every Day Discovery, Find Analyze and Understand Information in Ways Never Before Possible, Endeca Latitude, Endeca InFront, Endeca Profind, Endeca Navigation Engine, Don't Stop at Search, No Data Left Behind, Discovery Applications, Endeca Slipstream, and other Endeca product names referenced herein are registered trademarks or trademarks of Endeca Technologies, Inc. in the United States and other jurisdictions. All other product names, company names, marks, logos, and symbols are trademarks of their respective owners. The software may be covered by one or more of the following patents: US Patent 7035864, US Patent 7062483, US Patent 7325201, US Patent 7428528, US Patent 7567957, US Patent 7617184, US Patent 7856454, US Patent 7912823, US Patent 8005643, US Patent 8019752, US Patent 8024327, US Patent 8051073, US Patent 8051084, Australian Standard Patent 2001268095, Republic of Korea Patent 0797232, Chinese Patent for Invention CN10461159C, Hong Kong Patent HK1072114, European Patent EP1459206, European Patent EP1502205B1, and other patents pending. ============================================================================= GENERAL (2.1.1) - Release Date: August 2011 - The release notes may have been updated since the release date. Access the Product Downloads section of the Endeca Developer Network (https://eden.endeca.com) for the most recent version of the release notes. INSTALLATION (2.1.1) For installation tasks, see the INSTALLATION section of below for release 2.1.0. MIGRATION (2.1.1) This is a compatibility release for MDEX Engine 6.2 and provides support for the features enabled in that release, including enhancements to dimension search, and features enabled in MDEX Engine 6.1.4, including record and dimension value boost and bury. For information about compatibility with Endeca components, please refer to the Endeca InFront Compatibility Matrix. ============================================================================= GENERAL (2.1.0) * Release Date: June 2010 * The release notes may have been updated since the release date. Access the Product Downloads section of the Endeca Developer Network (http://eden.endeca.com) for the most recent version of the release notes. INSTALLATION (2.1.0) The Endeca URL Optimization API for the Endeca RAD Toolkit for ASP.NET is distributed as a Zip file named UrlOptimizationAPIRADNET-2.1.0.zip. 1. In your local environment, locate the Zip file that you downloaded from the Endeca Developer's Network (EDeN). 2. Extract the Zip file to a local drive. Endeca recommends extracting to C:\. Extracting the file to C:\ creates the subdirectory structure C:\Endeca\SEM\URLOptimizationAPIs\RAD Toolkit for ASP.NET\2.1.0. 3. Open your project in Visual Studio and add a reference to Endeca.Web.Url.Seo.dll. The specifics of this step vary depending on your version of Visual Studio and on the .NET language your application is written in. In general, you use the Visual Studio "Add Reference" dialog box to browse to \Endeca\SEM\URLOptimizationAPIs\RAD Toolkit for ASP.NET\2.1.0\bin\Endeca.Web.Url.Seo.dll. 4. Add references to the following Endeca RAD Toolkit for ASP.NET files: * Endeca.Data.dll * Endeca.Web.dll * Endeca.Web.UI.WebControls.dll (this is optional if you are not using the RAD Toolkit Server Controls) These assemblies are included as part of the Endeca RAD Toolkit for ASP.NET installation. 5. Add references to the following Endeca Presentation API for .NET files: * Endeca.Navigation.dll * Endeca.Logging.dll * Endeca.Navigation.AccessControl.dll These are also included as part of the Endeca RAD Toolkit for ASP.NET installation. MIGRATION (2.1.0) There are no required migration changes to make if you are going from version 2.0.0 to version 2.1.0 of the Endeca URL Optimization API for the Endeca RAD Toolkit for ASP.NET. Version 2.1.0 of the Endeca URL Optimization API for the Endeca RAD Toolkit for ASP.NET is compatible with Endeca IAP 6 using Platform Services 6.1.0 only. It is not compatible with IAP 5.1.x or Platform Services 6.0.1. The URL Optimization API for ASP.NET (for use with the Presentation API for ASP.NET) has been deprecated. BUGS (2.1.0) URL Optimization API: - BUG17348: The BuildUrl method did not respect the value for records per page. This has been fixed. KNOWN ISSUES (2.1.0) URL Optimization API: - OE4989: In an application with multiple UrlManager instances, the BasicUrlProvider (part of the RAD API for ASP.NET) is unable to process the state associated with commands that are registered to a different UrlManager. - OE4993: In some situations, such as the "see-all" links for a dynamic content spotlight cartridge, the Content Assembler reference application for the RAD Toolkit for ASP.NET does not provide enough information to the UrlBuilder.BuildUrl method to create properly search engine-optimized URLs. For information on how to write or modify an application built using the Content Assembler API for the RAD Toolkit for ASP.NET to work with the URL Optimization API, please refer to the URL Optimization API for the RAD Toolkit for ASP.NET Developer's Guide.