Home/ Questions/Q 7494625
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T17:40:48+00:00

I have tried every way I can find to make my custom control understand

  • 0

I have tried every way I can find to make my custom control understand URI packs – both in generic.xaml and code. All examples I find works fine in my user controls, but never in custom controls.

All files are set to Resource – except for generic.xaml, if I change that the custom control stops displaying all together.

If I try any kind of pack URI I get errors at compile time. Relative or absolute, doesn’t matter. I’ve tried putting the images in other assemblies as well, but with no luck.

If I try New Uri("/Images/btnImage.PNG", UriKind.Relative) it looks for C:\Images\btnImage.PNG, which is wrong. I’ve also tried Images/btnImage.PNG or ./Images/btnImage.PNG but then it looks for C:\MyProject\bin\Debug\Images\btnImage.PNG.

The only thing I get to work is an absolutely absolute URI – i.e. New Uri("C:/MyProject/Images/btnImage.PNG", UriKind.Absolute).

  1. Do custom controls only understand file system absolute URI’s?
  2. If 1 = No Then Return correctAnswer (please)
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I ended up using pack URIs, but not without hitting a few snags along the way.

    Most examples don’t bother to mention you can’t use the “short version” pack URIs to refer to the current assemply if the projects a class library.

    • 0