ReadMe for ArcFM for Silverlight 3.2

Version 13
Visibility: Open to anyone

    ArcFM for Silverlight 3.2 Release Contents

    ArcFM for Silverlight has two components: 1) the Silverlight SDK, and 2) the Silverlight page. The Silverlight SDK is built on Esri's Silverlight API and allows developers to extend the existing functionality within custom web applications. The web page provides an advanced Silverlight UI. Some examples of functionality include the ability to locate and identify features, as well as redlining and printing.

     

    All new functionality in the 3.2 release is outlined in What's New in ArcFM for Silverlight 3.2?

     

    Bug Fixes

    • MM52897: ArcFM Properties automatically applied to results in Silverlight
    • MM53038: Redline dropdown doesn't respect the order of the features in the TOC in ArcMap
    • MM52075: Layers in the ToC become unchecked
    • MM52044: Duplicate Layers in Silverlight Locate Drop Down
    • MM52250: Multilevel relationships can cause malformed REST queries
    • MM52859: Silverlight's Full Extent button zooms to entire world when basemap is present layer list
    • MM52258: Document ExtentLayer attribute in Layers tag in page.config

     

    Installation Instructions

    ArcFM for Silverlight Application

    After installing the prerequisites as detailed in the supported versions webpage, you can begin installing the ArcFM for Silverlight application.

     

    1. Download the installers and double-click ArcFM_Silverlight_Page_3.2.msi to begin installation.
    2. At the Welcome screen, read the license agreement and click Next (to select the components to install) or Quick Install (to install the typical components and finish with no further steps).
    3. At the Destination Folder screen, browse the folder in which the application should be installed. Click Next.
    4. Click Install to initiate installation.
    5. The installation will conclude with a Finish dialog. Click Finish.

     

    ArcFM for Silverlight SDK

    After installing the prerequisites as detailed in the supported versions webpage, you can begin installing the ArcFM for Silverlight SDK.

     

    Note: You can remove the Telvent Silverlight API Toolbox from Visual Studio. We recommend using the Schneider Electric Silverlight API Toolbox in its place.

     

    1. Download the installers and double-click ArcFM_Silverlight_SDK_3.2.msi to begin installation.
    2. At the Welcome screen, read the license agreement and click Next (to select the components to install) or Quick Install (to install the typical components and finish with no further steps).
    3. At the Destination Folder screen, browse the folder in which the application should be installed. Click Next.
    4. At the Product Features screen, select which product features and templates you want to install. Click Next.
    5. Click Install to initiate installation.
    6. The installation will conclude with a Finish dialog. Click Finish.

     

    Known Issues

    • IRelQueryTable – This does not provide direct access to the joined tables.  SOEs are unable to query joined table (NIM102137).
    • Identify and Query - Identify and Query return slightly different results when the requested datum is different than both data and service (NIM092797).
    • Transformation - ArcObjects should present a special method or utility that picks the best transformation for the developer given the input and output spatial reference and the location for the data (like REST does). Trace results display slightly off of actual features.  Also affects Fiber Server OTDR trace.  And we're not able to use the transformation file provided as a work around (NIM093100).
    • Identifying a Feature Class - Identifying on a feature class with an outer join causes issues if a returned feature is not related to anything (NIM092688)
    • IEIDHelper - With IEIDHelper.PartialComplexEdgeGeometry property set as True, if the OutputSpatialReference is different from the spatial reference of the feature class used to build the network, the IEIDHelper doesn't return the geometry for partial complex edges. If the customer has a basemap and operational layers are not in the same spatial reference, then there is no tracing (NIM091804).
    • Map Tab Control - Value does not fall within the expected range exception when the map is on a tab control and trying to change the map extent from another tab (NIM104340).
    • Geocode - The esri.arcgis.client.bing.geocoder class' Geocode method should allow ranking of results based on the application's current extent (NIM103104).
    • World Address Locator - World Address Locator produces incorrect results. (http://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer) The Find operation should better manage which underlying locator is used when the location/distance parameters are used. This bug can be worked around by including either the city or zip code in this search (NIM103042).
    • ArcFM Silverlight SDK - Will get an error the first time you try to use one of the Controls (Error HRESULT E_FAIL has been returned from a call to a COM component). Build your solution; you should not see this error again.
    • ArcGIS Online (AGOL) WebMaps Feature Layers - Editable Feature Layers from WebMaps have a Visible setting of true, per Esri standards, and will thus always appear as visible in ArcFM for Silverlight. However, these feature layers do not appear in the TOC.
    • ArcGIS Online (AGOL) WebMaps Group Layers - Visibility of Group Layers from WebMaps in the ArcFM for Silverlight Page can be different than the layer visibility set in the WebMap if there is mixed visibility between the Group Layer and its children (NIM090328).
    • Attribute Viewer - For values affected by Autoupdaters (AU's), after editing a feature, you may need to close and reopen the attribute details form to see the updated values or re-identify the feature in the Attribute Viewer.
    • Bing Map Layers - If you have a Bing layer present, other layers may have issues with scale range visibility. This may cause issues both with the TOC and the Identify drop-down. As a workaround, set the initial extent in the page.config so that at least one non-annotation layer is visible.
    • Custom Searches and Tracing - Getting wrong location for the results when there are multiple datums in a custom search.
    • IISConfig.exe on Windows Server 2003 - When configuring IIS on Windows Server 2003, you will have to manually enable 32-bit ASP.Net for 2.x and 4.x framework.
    • Installing SDK - The installation of the current ArcFM for Silverlight SDK requires that you first uninstall previous versions of ArcFM for Silverlight and then install the most recent version of ArcFM for Silverlight.
    • Map Services - Map services which have a different spatial reference than cached map services (such as Bing and AGOL maps) are not re-projecting correctly. Locating on devices will appear away from where the actual feature is located.
    • Map Services - The Esri map control requires a clientaccesspolicy.xml file to access map services not on the web host. See Making a Service Available Across Domain Boundaries for more information.
    • Proxy URL - Using a Proxy URL (and appending the 6080 port when not using the IIS Web Adaptor) in the page.config does not allow the TOC to expand for your services and layers to be visible.
    • Searching - When using an ArcSDE service to connect to an Oracle database, doing a Search for features using the "LIKE" option behaves like an exact match. A direct connection to Oracle performs the "LIKE" option as expected.
    • Trace Buffers - If you enable Trace Buffers, and a trace is performed with the Remove or Add selection management options selected, the Trace Buffer highlights anything that is in the Attribute Viewer after the trace is completed. Using the Remove or Add selection management options can result in features that are not part of the trace results highlighting with a Trace Buffer.
    • Use of Special Characters in Layer Names - Layer names cannot accept the following characters: <
    • User Account Control - The ArcFM Silverlight SDK installer must be run by an administrator when installing on a computer running a Microsoft operating system with User Account Control enabled.
    • Uninstall VS 2012 Templates - If you have the VS 2012 templates installed, you cannot use the SDK uninstaller to remove them.
    • Basemap is a different coordinate system - Users cannot place network features using ArcFM Silverlight/Server if the basemap is uses different spatial references than what the service was published with. This is a known Esri issue.

     

    Documentation

    You can review all new functionality in the release at the ArcFM Solution Resource Center. In addition, the Resource Center also offers the latest Using and Configuration Guides for each product. You can view this information before installing the latest release.

     

    SDK Installer: To install the ArcFM Solution SDK Documentation, the Microsoft Windows SDK or Microsoft Visual Studio must be installed. The SDK installer is a large file to download (~600mb). Installing the SDK will take several minutes. The ArcFM Solution Resource Center contains everything available in the SDK installer plus some additional information (e.g., free tools and technical white papers).