Skip to main content

WinRT: Something went wrong with Share. Try again later.

Last week I was happily implement the Share charm in a Windows 8 application, when it suddenly started to fail. Every time I clicked on the share button, no list of apps was shown. Instead I got the following message:

Something went wrong with Share. Try again later.

OK, I thought, probably I made some mistake, so I removed my last changes but no luck… Bedroefde emoticon No matter what I tried I couldn’t get the Share charm working again.

So what happened?

I discovered that if you debug your Search contract code,  it can result in system-wide shutdown of the service, meaning that no Windows Store app can share any content with other apps anymore. Typically, this happens when you stop debugging (in Visual Studio) while in DataTransferManager’s DataRequested event handler.

I found a fix on Andrej Tozon’s blog: restart the Explorer.exe process.

Here are the steps in case you don’t have any clue how to do this:

  • Open Task Manager
  • Select the Details tab
  • Find Explorer.exe (easiest to sort by Name)
  • End Task (button in right lower corner will do the job).
  • Select File –> Run new task
  • Type Explorer.exe in the input box
  • Press OK (and taskbar is back)

That should to the trick…

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...

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.

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...