Using such negative margin leads to some parts of the template to be actually outside of the control boundaries.
Multiple operations applied on a big RadBitmap can cause OutOfMemoryException because of used and not disposed unmanaged resources in a WriteableBitmap object. Steps to reproduce: - Execute multiple times the Rotate tool Observe: The memory goes up and retains such. Expected: The unmanaged memory is cleared. Findings: the memory leak is related to the WPF class WriteableBitmap which is internally used by the RadBitmap. Attached is a sample project illustrating the problem using only WPF classes. Note: At this point, we are not aware of a possible fix.
The compass elements are not on the proper places when the docking is on the second monitor. To reproduce this the DPI of the monitors should be different for example 125% (main) and 150% (secondary). Also, to reproduce this you will need to enable the DPI awareness of the application by setting the dpiAware and dpiAwareness settings in the app.manifest file.
A workaround for the issue is to apply a 1px top Margin.
OpenStreetMap provider uses OpenStreetMapSources which have MaxZoomLevel 18.
When Wraparound of the Map is True and you move (with SetView or ZoomLevel + Center properties) the map to zoomlevel > 18 , no tiles are loaded.
I think that deploying scenario for applications and protecting dll-s are complicated. I think that better way is to use control panel. I want to send you needed informations through control panel, a and I want to provide me my version of dll-s that are protected and I can use it in my app. You build it on your own. The way you are doing it now is complicated, and can produce issues.