|
POST
|
Hi, You will need to obtain a Bing key directly from Microsoft - you can send an email to [email protected]. There are additional details in the Bing Maps FAQ: http://links.esri.com/bing_faq. Cheers Mike
... View more
07-29-2013
08:08 AM
|
0
|
0
|
1180
|
|
POST
|
Hi, Can you post your code? - most folk on the forum here will have the sample data so we should be able to able to help you out pretty easily I hope. Cheers Mike
... View more
07-29-2013
12:50 AM
|
0
|
0
|
2050
|
|
POST
|
Hi, Thanks for the questions - please note that any details given here may be subject to change... 1) Will the new Runtime SDK for .NET have any concept of package-based offline functionality like the current RuntimeLocalServer? Yes, we plan to include the new offline geodatabase/routing/geocoding functionality demonstrated in March at the Dev Summit and more recently at the UC within the new Runtime SDK for .NET will include. Additionally, the "Windows Desktop" portion of the new SDK will continue to support existing package-based workflows using the RuntimeLocalServer. 2) The Windows Store SDK lists support for Windows 8 only. This thread already mentions XP support will not be available. What about Windows 7 support for the new Runtime SDK for .NET? Yes, the new ArcGIS Runtime SDK for .NET will support development/deployment of WPF applications on Windows 7 and 8 - that's the "Windows Desktop" API within the new combined SDK. However, the Win Store App and Win Phone 8 portions of the new Runtime SDK will most likely follow Microsoft's system requirements which, as far as I'm aware, are Windows 8 only. For all three APIs it's Visual Studio 2012 and .NET 4.5. We will be investigating support for VS2013. Cheers Mike
... View more
07-25-2013
12:58 AM
|
0
|
0
|
3197
|
|
POST
|
1. .NET 4.5 does not support Windows XP. Many of our customers still run Windows XP. We cannot go to our customers to tell them to upgrade the OS just to use our software. Targeting a framework that excludes an OS that's still widely used is not acceptable. We've been discussing this subject extensively over the last year, but continuing to support XP is increasingly presenting us with significant challenges in our development as well as preventing us from taking advantage of new features in .NET 4.5. Therefore we recently announced that for the existing WPF SDK the next release (10.2) will be the last major release to support Windows XP. For the new SDK, it's built for Windows Store and Windows Phone 8 as well as the windows Desktop and therefore needs to be built on .NET 4.5. 2. You say that the new .NET SDK will not support custom symbols. Are you going to provide alternatives? How are we going to display our custom symbols now? We are still investigating ways in which we can provide support for custom symbols in the new .NET SDK. One alternative is to use RenderTargetBitmap to render the WPF elements as images then use the images as PictureMarkerSymbols or PictureFillSymbols, although I appreciate that will not work for any animated symbols with StoryBoards, etc. I'd be really interested to see any custom symbols you've defined in XAML - if you're able to share them, you can email me at [email protected]. Cheers Mike
... View more
07-24-2013
05:52 AM
|
0
|
0
|
3197
|
|
POST
|
Hi, The next release of the ArcGIS Runtime SDK for WPF will be 10.2.1 towards the end of the year. At the same time we'll be releasing the new ArcGIS Runtime SDK for .NET which includes the API for Windows Desktop - i.e. a new WPF API. And there will be future releases of the existing WPF SDK, which will include bug fixes and enhancements to synchronize with the rest of the ArcGIS platform (i.e. Server / Online). This means you have time to migrate. Typically what we've found so far is that migration is quite straightforward, because although it's a new API, it's really an evolution of the existing API - here's the approx process: #. Open up the project #. Remove the reference(s) to ESRI.ArcGIS.Client.*.dll #. Add a reference to Esri.ArcGISRuntime.dll #. Change the XAML and code namespace statements (i.e. the xmlns and usings) #. Rebuild... and work through the build errors. #. The majority of classes and class members share the same names and behave the same way so in many cases your code will recompile after a few modifications and will continue to work as it did with WPF. However, there are a few changes - the new API... - is built on .NET 4.5 - so your app. needs to be targeting .NET 4.5. - makes extensive use of the Task-based async pattern instead of events - so there will likely be some changes to some areas of logic in your app (e.g. Layer.Initialized events, Mouse events). - will only use the ArcGIS runtime map engine (previously called the accelerated display mode in WPF) which means no support for XAML custom symbols. We are working on equivalency in other areas where the WPF accelerated display mode was lacking, such as rotation. To help you migrate: - For the 10.2.1 release of the WPF SDK we've added Task-based async support in many areas to help you start taking advantage of .NET 4.5 features such as the await keyword - but realistically you - In the 10.1.1 release, you can make sure you're working with the accelerated display mode (and let us know if you experience any issues). - Join the beta testing in the late summer to test out the new .NET SDK and help us make sure it does what you need it to. Cheers Mike
... View more
07-17-2013
06:27 AM
|
0
|
0
|
3197
|
|
POST
|
It would be nice if all the Metadata would be made available. You are populating it anyway. We'll take that on board - thanks for the feedback. Cheers Mike
... View more
07-16-2013
05:04 AM
|
0
|
0
|
895
|
|
POST
|
Hi, That's a good question - and I can't see anything in the API which would allow you to determine that. We are investigating improving the service-level metadata for a future release, so I'll make sure that gets consideration too. There's nothing on either the ArcGISTiledMapServiceLayer class or ArcGISDynamicMapServiceLayer - because by the time you've initialized one of those classes you've already made the decision and currently we don't have a service browser API as such. If you're working with WebMaps or Portal items there might be something in there that could help? You could make the REST call yourself (using the ArcGISWebClient class http://resources.arcgis.com/en/help/runtime-wpf/apiref/index.html?ESRI.ArcGIS.Client~ESRI.ArcGIS.Client.ArcGISWebClient_members.html). Then to help process the results you could use something like http://json2csharp.com/ to generate a class from the JSON response. Alternatively, you could as the default, always try to create an ArcGISTiledMapServiceLayer instance then fall back to an ArcGISDynamicMapServiceLayer if the InitializationFailed event fires (if will be raised if the service doesn't have a cache). Cheers Mike
... View more
07-15-2013
05:05 AM
|
0
|
0
|
895
|
|
POST
|
Hi, For the existing WPF SDK we're currently investigating adding both rotation as defined in a feature service (i.e. on a renderer) and also rotation directly on a symbol. We hope to include this in the next release but we're concerned about the performance implications in the non-accelerated display mode. It will be in the new Windows Desktop API as part of the ArcGIS Runtime SDK for .NET, which only uses the core runtime map rendering. Regarding animation in the core runtime map (accelerated display mode in WPF), it is on the roadmap and we're aware that it's a significant requirement for many folk developing with the WPF SDK, but at this time is unlikely to be in the next release (10.2.1). Cheers Mike
... View more
07-11-2013
11:56 PM
|
0
|
0
|
3065
|
|
POST
|
Hi, Yes, if you are planning to undertake the development of a new custom desktop application then you should look at the ArcGIS Runtime first. There are still some areas where it does not offer the functionality of ArcGIS Engine, such as 3D visualization, but we will be doing our best to close that gap over the next couple of releases. It might be the case that your timescale is short, in which case you may need to continue to use ArcGIS Engine but you should consider ways in which you could architect your application that will ease your migration to the ArcGIS Runtime in future. Unfortunately I don't know the extensibility plans for the new ArcGIS Pro app. It's too early to say, but the ArcGIS Professional App might use some components of the ArcGIS Runtime - just as the current ArcGIS for Desktop already does for 64-bit Geoprocessing. Cheers Mike
... View more
07-11-2013
06:32 AM
|
0
|
0
|
3065
|
|
POST
|
Hi, The new ArcGIS Professional App is the next generation of ArcGIS for Desktop and is an out-of-the-box, end-user GIS application. The new ArcGIS Runtime SDK for .NET is, as you summarized, a developer SDK based on .NET 4.5, extensively uses the new Task-based async functionality of .NET 4.5, and supports development in Visual Studio 2012. I hope that clarifies the role of the two products. Cheers
... View more
07-11-2013
05:36 AM
|
0
|
0
|
3065
|
|
POST
|
Hi, No, the new ArcGIS Professional Application is not currently based on the new ArcGIS Runtime SDK for .NET. Cheers Mike
... View more
07-11-2013
04:28 AM
|
0
|
0
|
3065
|
|
POST
|
http://blogs.esri.com/esri/arcgis/2013/07/05/the-history-and-future-of-the-arcgis-sdks-for-net/
... View more
07-11-2013
01:30 AM
|
0
|
25
|
15675
|
|
POST
|
Hi, Please you post a snippet of your code to help ascertain what might be the issue? Cheers Mike
... View more
07-11-2013
01:24 AM
|
0
|
0
|
1472
|
|
POST
|
Hi, That error message occurs when a symbol or renderer is not supported in the accelerated display mode. Unfortunately the symbology used by the out of the box measure action is not supported in the accelerated display - this is resolved in the next release (10.2.1) but in the mean time if you need to provide measure action functionality and you're using the accelerated display (which I would always recommend if possible) then you should take a look at this Geodesic Operations sample: http://resources.arcgis.com/en/help/silverlight-api/samples/start.htm#GeodesicOperations. Cheers Mike
... View more
07-11-2013
01:20 AM
|
0
|
0
|
960
|
|
POST
|
Hi, We've just published a blog post which outlines our plans in much greater detail: http://blogs.esri.com/esri/arcgis/2013/07/05/the-history-and-future-of-the-arcgis-sdks-for-net/. The current thinking is that for the ArcGIS Runtime SDK for WPF we will continue to target .NET 4.0 and support VS2010 for the rest of the 10.2.X release cycle, until the next major release (e.g. 10.3 or 11). The forthcoming 10.2.1 release of the WPF SDK later this year includes support for the new Task-based pattern as an alternative to events to help you start taking advantage of new features in .NET 4.5. Also to be released later this year will be the new combined ArcGIS Runtime SDK for .NET (Store / Phone / Desktop) which will target .NET 4.5 and support VS2012 from the outset. Both will be available in beta towards the end of the summer. We'll begin testing with VS 2013 internally but we won't be able to officially offer support for it until it's released. Cheers Mike
... View more
07-11-2013
01:11 AM
|
0
|
0
|
990
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 04-14-2026 05:04 AM | |
| 1 | 02-20-2024 07:02 AM | |
| 1 | 01-19-2026 06:44 AM | |
| 1 | 12-10-2025 07:16 AM | |
| 1 | 11-21-2025 08:12 AM |
| Online Status |
Offline
|
| Date Last Visited |
07-02-2026
06:07 AM
|