Latest Contributions by RichZwaap

Hi Aaron, Are you seeing this error when you run the application?  Or just in Visual Studio when you have the XAML page open?  If the error is occurring when viewing the XAML, then something's gone wrong with locating the assembly at design-time, in which case it won't affect the functionality of the application when executing. -Rich ... View more

Hi Robert, Copying the deployment folder to your project's output directory happens as a result of build commands managed by the Runtime NuGet package.  If you've not added the package to a project (be it an application or otherwise), then it has no knowledge of that project and therefore has no mechanism to perform the copy.  This is a limitation in your particular use case.  You will either have to reference the Runtime in your main app or manage copying of the deployment folder explicitly. Hope this helps. -Rich ... View more

Hi Schuyler, I wanted to clear up what's going on here and what the available options for addressing it are.  First, what the linker does is analyze the code in your app and discard anything that's not used - more info here.  By default, it does not include XAML in what it looks at.  In your case, the MapView class itself is only being referenced in XAML and not anywhere in your code.  So the linker then thinks that nothing in the Esri.ArcGISRuntime.Xamarin.Forms assembly (which essentially just includes the Xamarin Forms MapView and SceneView) is being used, so it excludes this assembly from the final compiled app. Setting the linker to "don't link" gets around the issue by opting out of linking entirely.  This is fine for debug builds, but for release you wouldn't want to do this, as it opts out of the size reductions the linker can bring. Alternatively, there are two ways to get around this while still letting the linker do it's thing: Opt-in to XAML Compilation.  This will enable analysis of the XAML at compile-time, so the linker will then recognize that the MapView class is in fact used and thus preserve the Esri.ArcGISRuntime.Xamarin.Forms assembly.  To do this, add "[assembly: XamlCompilation(XamlCompilationOptions.Compile)]" to the AssemblyInfo.cs file in your iOS app project. In your code behind, add a method that never gets called that includes a reference to a class in the Esri.ArcGISRuntime.Xamarin.Forms assembly. Mark the method with the [Preserve] attribute to instruct the linker not to remove it.  You could, for instance, add this: // this code is never executed, but is included to prevent the linker from excluding the Esri.ArcGISRuntime.Xamarin.Forms assembly from the compiled app [Xamarin.Forms.Internals.Preserve] private void UnusedMethod() {     var unusedMapView = new Esri.ArcGISRuntime.Xamarin.Forms.MapView(); } Hope this helps. -Rich ... View more

This issue has been fixed in version 3.2 of the Viewer, which has just been released.  Please go to the Resource Center to download it.  Sorry for the inconvenience. ... View more

Version 3.2 has been released and includes a fix for this issue.  You can download it from the Resource Center. ... View more

The 3.2 setups are now available for download.  You can get them from the Viewer's Resource Center.  This includes a fix for the on-click pop-ups not respecting layer definitions (as well as time extent and parent layer visibility). ... View more

Any update on when this will be? Should be this week - we're currently going through final testing of the release. ... View more

Sorry, there's not currently any way to configure this.  Since the time is important in some data, the Viewer defaults to including it in order to cover those scenarios.  This is certainly something we would like to address, but it does not look like we'll be able to in the forthcoming 3.2 release. ... View more

The problem I have is that we have an IT policy that we cannot have IIS (or any web server) on any machines but designated servers. Well that's unfortunate.  Since the Application Builder is a web application, it can only be installed on a machine with a web server (specifically IIS). But, if I access the Silverlight Builder remotely...I shouldn't need a local web server right? Correct.  If the Viewer is installed on another server, you'll be able to access and use the Application Builder in your browser - provided that you have access to the Application Builder site from your machine. I should also add that, while this doesn't help in your particular case, it is possible to configure the Application Builder to deploy applications to another server.  This can be done as follows: On the machine that apps are going to be deployed to, create a network share that maps to the folder that will contain the apps. On the shared folder, grant write access to the account that will be used to deploy the applications.  Note that this is the account that the Application Builder's IIS application pool will be run under. On the machine where Application Builder is installed, open IIS Manager and modify the identity of the SilverlightViewerAppPool application pool to match the user account that was granted write access in the previous step. On disk, navigate to and open the Application Builder's web.config file.  With a default intallation of Windows, IIS, and the Viewer, the path to the web.config would be C:\inetpub\wwwroot\Builder\web.config. In the web.config, find the AppsBaseUrl and AppsPhysicalDir keys.  Update the value of the AppsPhysicalDir key to specify the path to the network share (e.g. \\machine_name\apps).  Update the AppsBaseUrl value to specify the URL that maps to the network share (e.g. http://machine_name/apps/). Also, any Viewer applications created with the Application Builder can be moved to another server just by copying the folder containing the app.  The folder name will match the name given to the app at the time it was deployed. Hope this helps. ... View more

Hi Brian: Yes, we should be able to get this fixed - there are several bugs related to the on-click pop-ups not respecting layer configurations that we're working on. ... View more

Hi Oleg: If the related data is a layer, then it could be added to the application separately and edited directly.  If the related data is a table, then this is a limitation of the product; the Viewer does not currently provide a way to add or delete records to/from a tabular data source. ... View more

Hi Brian: As Brett points out, the out-of-the-box search tool provides similar functionality to what you're requesting.  However, there is the additional inconvenience that you need to click a button to open the search UI.  To implement a search box that's embedded in the Viewer's header, you'll need to implement a custom control, then modify the Viewer layouts to include that control.  You can find an example of a textbox control exposed in the Viewer header here.  The example shows embedding a label that can be configured in the Application Builder, and it only shows including it in one layout.  Still, the approach to embedding a custom control in a layout is applicable here. Hope this helps. ... View more

Hi Dan: The upcoming release will include a new Query Tool, support for URL parameters (e.g. to start a Viewer app at a certain extent or location), and enhanced support for secured ArcGIS for Portal content and federated services.  On the localization front, a whole bunch of new languages are in the pipeline.  And last but not least, the release will also include a bunch of bug fixes. ... View more