Hello,Recently Microsoft introduce de new design of the road layer for Bingmap.
Previously, just by adding this line in the code behind, the style was adapted:
Microsoft.Maps.MapControl.Core.
MapConfiguration.Load(new System.Uri("http://dev.virtualearth.net/silverlight/mapcontrol/v1/v1.1_MapControl.xml"));
But, with your control, how can I reproduce this?
Hi, loicbar,
To replace the old road style with the new one, you could use the following approach:1) Update the Bing Maps service reference in your project by right-clicking it and chosing Update Service Reference.2) Change the MapStyle of your ImageryMetadataRequest instance to Road_v1.
Please, keep in mind that the Bing Maps Teem officially stated in their blog, that beginning on May 1, the new style will become the default and only road style, so possibly a further change in the name of the style might follow. More information on MapStyle Enumeration is available here.
Hope that helps,Milana Zhileva
Hi Milana,
It's already June, and Microsoft did not change it's default style yet. Any idea how we could achieve the new layout?
Thanks!
It sounds really strange. Could you, please, check if the Service References folder is deleted when you remove the reference and add it again.
very weird, I don't have a MapStyle in VEImageryServiceReference (which is my service reference).
I also do not have a mapstyle enum in my Reference.cs file. I've tried deleting and adding the service reference again.
this is code from your Reference.cs file
[System.Diagnostics.DebuggerStepThroughAttribute()]
[System.CodeDom.Compiler.GeneratedCodeAttribute("System.Runtime.Serialization", "4.0.0.0")]
[System.Runtime.Serialization.DataContractAttribute(Name="ImageryMetadataRequest", Namespace="http://dev.virtualearth.net/webservices/v1/imagery")]
public partial class ImageryMetadataRequest : BingMapsNewStyleSL.BingMapServRef.RequestBase {
private BingMapsNewStyleSL.BingMapServRef.ImageryMetadataOptions OptionsField;
private BingMapsNewStyleSL.BingMapServRef.MapStyle StyleField;
[System.Runtime.Serialization.DataMemberAttribute()]
public BingMapsNewStyleSL.BingMapServRef.ImageryMetadataOptions Options {
get {
return this.OptionsField;
}
set {
if ((object.ReferenceEquals(this.OptionsField, value) != true)) {
this.OptionsField = value;
this.RaisePropertyChanged("Options");
public BingMapsNewStyleSL.BingMapServRef.MapStyle Style {
return this.StyleField;
if ((this.StyleField.Equals(value) != true)) {
this.StyleField = value;
this.RaisePropertyChanged("Style");
This is code from my Reference.cs file
public partial class ImageryMetadataRequest : McKinsey.BI.Silverlight.VEImageryServiceReference.RequestBase {
private McKinsey.BI.Silverlight.VEImageryServiceReference.ImageryMetadataOptions OptionsField;
private Microsoft.Maps.MapControl.PlatformServices.MapStyle StyleField;
public McKinsey.BI.Silverlight.VEImageryServiceReference.ImageryMetadataOptions Options {
public Microsoft.Maps.MapControl.PlatformServices.MapStyle Style {
Hi Roel,
The MapStyle set in the sample is BingMapServRef' s one. Probably this is the reason why it doesn't work as I am using the same url you shared few forum posts above.
Please, let me know if it works for you with mapImgRequest.Style = BingMapServRef.MapStyle.Road_v1; (in terms of the sample I attached to my previous forum post).
Thanks,Milana Zhileva
Thanks for your sample. It works indeed.
I tried updating the reference again, but no success...
Which uri did you provide to add your service reference?
this is the one I used:
http://dev.virtualearth.net/webservices/v1/imageryservice/imageryservice.svc/mex
my MapStyle refers to the enum in the Microsoft.Maps.MapControl.PlatformServices namespace which is different from yours
Please find attached a sample application (), implementing the approach I described above which is working as expected. There are two things that need to be done to get it running though: add Infragistics dlls and replace the BING_MAPS_SECRET_KEY string with the one you'd have obtained from Bing Maps portal.
I think that the issue you are experiencing is probably connected with the update of the Service Reference, may be you could try to do it again.