ArcGIS API for Silverlight/WPF version 2.1 Release Candidate

[DavidAshton]

First please let me say the Legend is awesome!!! You guys Rock!

I have one hopefully small and easy.....///seems stupid question.  If I have a project that was built with 2.0 api and just download the 2.1  Release Candidate  how should I update the Referrences like the ESRI.ARCGIS.CLINT.TOOLKIT ref?  What is the best practice?

Thanks
David

[DominiqueBroux]

Dave is quite right.

Your service don't need to be hosted by ArcGIS.com. It just need to be accessible publically, and so by the arcgis.com web site.

[YurongTan]

I know this error, it is annoying 😛

Unfortunately, we have no control over this but we are trying to get some clarification from Microsoft regarding this issue.

The error only appears in Design view. You can still run your application without problem.

If you remove LayerIDs in your Legend, this error will go away.

The only thing I can say is that our team is aware of this Design view error and we too are finding answers about how we can possibly get this issue resolved or atleast workaround so that our users can still see Design view without the annoying error popping up 😛

[REPLY]
I am not sure if this is Microsoft Silverlight thing.  Look at the ESRI Silverlight Viewer.  If you create an "app" through the Viewer GUI and this legend issue is non exists.  The control of the legend (turn on/off and expand/collapse of layler list) will work perfectly with an app from the Viewer GUI.  In addition, you can also have an app with a fully controllable legend and layer listing.  However, when the same legend control is incorperated/merged into an app based on either the standard or the showcase template, that legend gets stuck.  I am talking about 3.0 API here.  How could one explain that it works with one ESRI thing and doesn't with another ESRI thing? [REPLY]

[DominiqueBroux]

You pointed out a design issue that should not impact the runtime.

However, when the same legend control is incorperated/merged into an app based on either the standard or the showcase template, that legend gets stuck. I am talking about 3.0 API here. How could one explain that it works with one ESRI thing and doesn't with another ESRI thing?

I don't figure out any reason for that. Could you share more détails on how to reproduce this issue?
Thanks

[YurongTan]

You pointed out a design issue that should not impact the runtime.


I don't figure out any reason for that. Could you share more détails on how to reproduce this issue?
Thanks

Look at this incident which is more than two months old.
Esri Incident #1113122.

The we all including the analyst got very frustrated. 

I have map services that I used in creating a simple app using the SL Viewer GUI and I would like to use the same map services (some services have sub-layers) for an re-invented app with additional functionality and got stuck with this issue.  If you can't find the notes for the incident, just drop a note here and I can supply them.  Thanks in advance for looking into this.

[DominiqueBroux]

Look at this incident which is more than two months old.
Esri Incident #1113122.

The we all including the analyst got very frustrated.

I have map services that I used in creating a simple app using the SL Viewer GUI and I would like to use the same map services (some services have sub-layers) for an re-invented app with additional functionality and got stuck with this issue. If you can't find the notes for the incident, just drop a note here and I can supply them. Thanks in advance for looking into this.

If you have a way to reproduce the problem without using the silverlight viewer that would be very helpful.
If you'd rather you can send your repro case to my mail