Latest Contributions by JohnFannon

Thanks Robert - I've been working on something similar this morning. My version gets the copyright string by making a request to each unique service url as the layers load, then updates the attribution text as in your example.  I'm still testing it, but it appears to be working. It would really help if Esri's documentation was clearer on exactly where the copyright text is derived from for the attribution widget.  ... View more

Hi Robert Thanks, but the sample you reference only includes MapImageLayers and not feature layers. I have a basemap plus feature layers from an ArcGIS online feature service and the copyright text from the feature service definition doesn't display in the default attribution widget. John ... View more

Are you using the correct 64-bit version of ESRIRegAsm? This should be at: C:\Program Files\Common Files\ArcGIS\bin\ESRIRegAsm.exe I'm not sure your step 4 is necessary as my installer class does not do anything with the ecfg file, it just executes the 64-bit EsriRegAsm. If you aren't installing using an MSI you can ignore the steps to edit the MSI with Orca. ... View more

Hi Soren It sounds like your class extension is built against the 32-bit assemblies, which explains why it works with desktop but not server. Server is looking for a class extension that is 64-bit and cannot find one. You need to create a separate solution for the server version and build this on a machine where ArcGIS Server is installed? This is required to build against the 64-bit Esri assemblies. You also need to follow all the other steps above, including setting the platform target to 64-bit for each project and for the setup and deployment project and changing the installer class (InstallerClass.cs) code to use the "/p:server" flag when installing/uninstalling. Here is the installer class for our class extension: using System; using System.Collections; using System.Collections.Generic; using System.ComponentModel; using System.Configuration.Install; using System.Linq; using System.Diagnostics; namespace InvokeESRIRegASM {     [RunInstaller(true)]     public partial class InstallerClass : System.Configuration.Install.Installer     {         public InstallerClass()         {             InitializeComponent();         }         public override void Install(System.Collections.IDictionary stateSaver)         {             base.Install(stateSaver);             //Register the custom component.             //-----------------------------             //The default location of the ESRIRegAsm utility.             //Note how the whole string is embedded in quotes because of the spaces in the path.             string cmd1 = "\"" + Environment.GetFolderPath(Environment.SpecialFolder.CommonProgramFiles) + "\\ArcGIS\\bin\\ESRIRegAsm.exe" + "\"";                         //Obtain the input argument (via the CustomActionData Property) in the setup project.             //An example CustomActionData property that is passed through might be something like:             // /arg1="[ProgramFilesFolder]\[ProductName]\bin\ArcMapClassLibrary_Implements.dll",             //which translates to the following on a default install:             //C:\Program Files\MyGISApp\bin\ArcMapClassLibrary_Implements.dll.             string part1 = this.Context.Parameters["arg1"];             //Add the appropriate command line switches when invoking the ESRIRegAsm utility.             //In this case: /p:Desktop = means the ArcGIS Desktop product, /s = means a silent install.             string part2 = " /p:Server /s";             //It is important to embed the part1 in quotes in case there are any spaces in the path.             string cmd2 = "\"" + part1 + "\"" + part2;             //Call the routing that will execute the ESRIRegAsm utility.             int exitCode = ExecuteCommand(cmd1, cmd2, 10000);         }         public override void Uninstall(System.Collections.IDictionary savedState)         {             base.Uninstall(savedState);             //Unregister the custom component.             //-----------------------------             //The default location of the ESRIRegAsm utility.             //Note how the whole string is embedded in quotes because of the spaces in the path.             string cmd1 = "\"" + Environment.GetFolderPath(Environment.SpecialFolder.CommonProgramFiles) + "\\ArcGIS\\bin\\ESRIRegAsm.exe" + "\"";             //Obtain the input argument (via the CustomActionData Property) in the setup project.             //An example CustomActionData property that is passed through might be something like:             // /arg1="[ProgramFilesFolder]\[ProductName]\bin\ArcMapClassLibrary_Implements.dll",             //which translate to the following on a default install:             //C:\Program Files\MyGISApp\bin\ArcMapClassLibrary_Implements.dll.             string part1 = this.Context.Parameters["arg1"];             //Add the appropriate command line switches when invoking the ESRIRegAsm utility.             //In this case: /p:Desktop = means the ArcGIS Desktop product, /u = means unregister the Custom Component, /s = means a silent install.             string part2 = " /p:Server /u /s";             //It is important to embed the part1 in quotes in case there are any spaces in the path.             string cmd2 = "\"" + part1 + "\"" + part2;             //Call the routing that will execute the ESRIRegAsm utility.             int exitCode = ExecuteCommand(cmd1, cmd2, 10000);         }         public static int ExecuteCommand(string Command1, string Command2, int Timeout)         {             //Set up a ProcessStartInfo using your path to the executable (Command1) and the command line arguments (Command2).             ProcessStartInfo ProcessInfo = new ProcessStartInfo(Command1, Command2);             ProcessInfo.CreateNoWindow = true;             ProcessInfo.UseShellExecute = false;             //Invoke the process.             Process Process = Process.Start(ProcessInfo);             Process.WaitForExit(Timeout);             //Finish.             int ExitCode = Process.ExitCode;             Process.Close();             return ExitCode;         }     } } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Once you've made these changes, you then need to build the solution and modify the resulting msi using Orca as described above to ensure that custom actions run using the 64-bit install utility (InstallUtil64). Note that the steps I described work for 10.2.1 and I have not tried building with later versions, but assume the process is similar. Regards John ... View more

Considering all the recent advancements in technology, the date format support in these applications is very poor. In a web map, on which almost everything depends, there are currently only two possible formats for fields with date and time, US format (m/d/yyyy hh:mm:ss) and international (d/m/yyyy hh:mm:ss) and neither are acceptable when users are international. The date format used in AGOL itself, most templates and widgets is also US format, which most of the rest of the world does not use. The ISO date format is designed for these scenarios as it avoids confusion. It should, as a minimum, be one of the format options and ideally, should be the default. The default date format should also be configured at the organisation or web map level.  At the moment we are constantly having to apologise to customers because the date formats aren't what they require.  ... View more

Thanks for this suggestion - I've taken a look at this and it looks like it could be an option and avoids the need for a proxy. It looks like you can set a filter on the view based on attributes, but not geometry. You can also set the extent of the view, but that doesn't seem to limit access to features outside the extent. It would still be useful to limit access using a geometric extent. ... View more

After a lot of digging and experimentation, it seems the following sets the layer's visibility successfully: FeatureSourceInfo.MobileCacheMapLayerDefinition.Visibility = true ... View more

Hi I appreciate it's been a while, but did you ever find an answer to this? I'm trying to do the same, but have hit the same issue where no feature types are shown in the SelectFeatureTypesPage.  Regards John ... View more