Skip to main content

Bug in WP7 Training kit

Last week I lost a lot of time while implementing push notifications for my Windows Phone 7 app(more about it soon!). I implemented the push notifications similar to thearrangement that Microsoft has set up in the WP7 training kit. When I launch the app and then exit the app to go back to the home screen, I am able to successfully send a toast notification.

However, when I send the same exact shell toast notification to my application while the application is running in the foreground, I get an error complaining that there is an invalid character for the root XML node. I found out there is an error in the NotificationSenderUtility that comes with the WP7 push notification sample in the training kit to send the notifications.

Anyway the solution is simple, replace the PrepareToastPayLoad message inside the NotificationSenderUtility with this code: 

   1:  private byte[] PrepareToastPayload(string text1, string text2)
   2:          {
   3:              MemoryStream stream = new MemoryStream();
   4:              XmlWriterSettings settings = new XmlWriterSettings() { Indent = true, Encoding = new UTF8Encoding(false) };
   5:              XmlWriter writer = XmlWriter.Create(stream, settings);
   6:              writer.WriteStartDocument();
   7:              writer.WriteStartElement("wp", "Notification", "WPNotification");
   8:              writer.WriteStartElement("wp", "Toast", "WPNotification");
   9:              
  10:              writer.WriteStartElement("wp", "Text1", "WPNotification");
  11:              writer.WriteValue(text1);
  12:              writer.WriteEndElement();
  13:              
  14:              writer.WriteStartElement("wp", "Text2", "WPNotification");
  15:              writer.WriteValue(text2);
  16:              writer.WriteEndElement();
  17:   
  18:              writer.WriteEndElement();
  19:              writer.WriteEndElement();
  20:              writer.WriteEndDocument();
  21:              writer.Close();
  22:   
  23:              byte[] payload = stream.ToArray();
  24:              return payload;
  25:          }

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more