Latest Contributions by dotMorten_esri

The approach I've seen used is: Grab a snapshot of the map using WriteableBitmap. Remove the map and replace it with the snapshot image. Popup a preview window on top, and insert the map in there. When you click print, you simply print this preview window. When you close the preview, move the map back and remove the temporary image snapshot. It's a little tricky, but it gives a really good experience, and allows the user to adjust the map based on the paper size in the preview. ... View more

"A lot of customers still like to see the layer list and want the ability to turn layers on and off. " Did you look at this sample? http://help.arcgis.com/en/webapi/silverlight/samples/start.htm#SubLayerList as well as this: http://help.arcgis.com/en/webapi/silverlight/samples/start.htm#LayerList ... View more

Sorry I dropped the ball on this thread. Yes this is currently a known issue. I'll see what we can do... ... View more

Dominique is hitting a key point here. The problem is that parsing and rendering that many features will effectively cause the framerate to go all the way down (since this has to happen in the UI thread), and there wouldn't be any frames available to update a progressbar. So even if you did make a progressbar, you wouldn't be able to update the progress while this is taking place. Each layer raises progress differently. Tiled and Dynamic Layers raise progress as the images downloads. Graphics and Element layer doesn't raise any progress, and FeatureLayer raises progress when an Update (ie querying featureserver for features) is taking place, and not when the actual rendering happens. The common thing here is that progress is showing that the app is waiting for data from the network - not the rendering progress itself. ... View more

Personally I think you would be better of not using the Toolbar, but instead just put a set of buttons in a stackpanel., It's more flexible, more customizable and way simpler than using the Toolbar. ... View more

"There has been some rumours about it for a while and I think that clients would like to see this feature so that they can build their own apps." The point here is that they WON'T be building their own apps. They will just be configuring an existing app. If they need to build their own apps, but doesn't want to be a developer, Expression Blend is the solution. ... View more

There's a pre-release version available. I think the final version should be out this month. ... View more

What does the layout tree around the map look like? Could you share a simplified example? ... View more

v2.0 requires Silverlight 4, and Silverlight 4 requires Visual Studio 2010, so yes, you need to upgrade. You can use the free Express version if you don't have access to the full version of VS2010. ... View more

You don't create a feature template. You reference the ones in FeatureLayer.LayerInfo.Templates/FeatureTypes. If your FeatureService has FeatureTypes but only one template for each type, you can just specify the FeatureType. If you only have Templates (no types), you can just reference the Template name. If you have FeatureTypes with multiple templates in each, you will have to use the array combination as you mention. ... View more

Btw, feel free to share what type of scenarious you are trying to solve with an OOB app. What are must-haves, what are nice-to-haves etc. ... View more

Will there be any Silverlight configurable apps in Managar in AGS 10? Nope. Manager is part of Server/WebADF. The Client API's are not. Currently, these Client API's are made for developers. We might include something like this down the road, but for now, the closest thing you will get is the XML configurable Flex app. Alternatively if you require Silverlight, you can get fairly far with no code using Expression blend, as shown in this session: http://proceedings.esri.com/library/userconf/devsummit10/tech/tech_68.html (starting at 29:00) We know this OOB thing is a common occuring request, and we are looking into accomodating the request down the road. I personally feel it's going against what these Client API's are really good for though: Making a simple targeted app, that does one thing, but does this one thing really well. An OOB app would always have to try and do everything, and thus never be that simple targeted app that your users will love to use and be productive with. I say, create one app that solves one problem, and create a different app that solves a different problem. Anyone can quickly learn how to use an app with one button, will only require very little development to make, likely have at most very few bugs, and will be easy to maintain and later extend if needed. The OOB will quickly become a big monstrous thing that tries to do everything, basically be ArcMap on the web and never be exactly what you need, or be easy to later retrofit to fit your needs. I know this does require a developer, and I do understand where you're coming from with this request, but this is just my opinion (and I am a developer after all:-) ... View more

"The performance gain that I was refering to is loading them as static resources rather than creating multiple copies of the same image when using the UniqueValueRenderer based on an attribute" When you specify a symbol for each UniqueValueRenderer, it will not create new instances, but re-use the same instance you are defining for that unique value on all the graphics that unique value matches. So it is already re-used. The problem with the PictureMarkerSymbol is that for each instance, the image is decoded over and over again, and this will happen even if you define it as a static resource. We found that the best way to work around this is to create a Rectangle, Grid or Border and set the fill or background to an ImageBrush, but make sure the brush is defined as a static resource. That way the image will only be decoded once, and if you have 100s of points using the same symbol, performance will be a lot better. I talk about this issue (and other tips on how to optimize symbols) in this session: http://proceedings.esri.com/library/userconf/devsummit10/tech/tech_68.html (general intro to symbols starting at 43:20, symbol performance from 58:10) ... View more

xmlns:esri="http://schemas.esri.com/arcgis/client/2009" should be enough for both core and toolkit assemblies, including the MapProgressBar. I've seen VS2010 be a little "weird" with these namespaces, and sometimes "forget" what assemblies they map to. Usually just removing the namespace declaration, save, and put it back in fixes it for me when it does this. ... View more

What happens if you disable caching in the REST endpoint? Or have the rest endpoint do caching of the images instead of just the URL to the images? ... View more