Under Review
Last Updated: 13 Mar 2019 20:03 by David

I'm working on a project that has a service component that will be generating Excel xlsx documents for distribution.  While there is a UI for administrative tasks, the service itself will run without an interface.  I'm using the Documents.Core, and several other associated libraries to accomplish this.  Two issues I've encountered, one is setting up the project with the appropriate libraries and keeping the version in sync with the Admin application, second is protecting those libraries once they are packaged for release.  I had a support ticket open to determine how to accomplish the latter, but the first is still a manual issue.  

So the feature request is to include the ability in the project templates and/or Convert to Telerik WPF Application to support a headless document solution.  It would ideally include (only) the required libraries and maintain their linkage to the appropriate library version with the rest of the solution which occurs with a full Telerik WPF UI app.  It would also include the necessary boilerplate code and references to properly protect the libraries.  I was referred to another feedback request on improving the overall library protection build process, but while related, what I'm asking for here is not exactly the same.

Under Review
Last Updated: 01 Feb 2019 09:20 by ADMIN
I want to import a FlowDocument into IDocumentEditor in order to obtain a RadDocument which I can convert to PDF.
Under Review
Last Updated: 24 Jan 2019 14:15 by ADMIN
Created by: Stefan
Comments: 1
Category: MultiColumnComboBox
Type: Feature Request
the multicolumncombobox has this weird display with X buttons which is completely inconsistent with a combo box.  Potentially make sense when you are multi-selecting but single select I would like to operate in the same way as a rad combo box so the user doesn't see any difference.