Theme Names aren't sorted in the Properties window of VS2019
when upgrading from telerik winforms r3 sp1 2018 to r1 2019 using vb.net 2012 i received an error
what is we have to do
To reproduce: please refer to the attached sample video 1. Uninstall the already existing version of the Telerik UI for WinForms suite. Ensure that you don't have any installation and the Telerik menu is not visible in Visual Studio. 2. Open Visual Studio >> Tools >> Extensions and Update and search for Telerik WinForms VSExtensions. Install it. 3. After restarting Visual Studio, create a new Telerik project. You may be prompt to download the latest version during the creation process. 4. Run the Toolbox configurator in order to obtain the proper version in the toolbox. 5. After the project is created, open the form's designer and drag a Telerik control from the toolbox and drop it onto the form. Open the Designer.cs and you will notice that control's declaration is inside the InitializeComponent method, not outside as expected. The issue is not reproducible each time you follow the steps. It was reproduced with Visual Stidio 2012 on Windows 10. Workaround: Download the Telerik UI for WinForms msi from your account and install the suite.
I have updated my OS to Win 10 from Win 8.1 and now none of the RadForms will open in VS 2015 Designer. Some esoteric error message: "Value cannot be null. Parameter name: instance" is displayed. Is there something I could do other than re-installing the entire Telerik product line? Lajos Szoke
To reproduce: 1. Download the Telerik_UI_For_WinForms_2014_3_14_1202_Dev_NuGet.zip and extract on computer 2. Create a project which contains RadPdfViewer and RadPdfViewerNavigator 3. Install all nuget packages 4. You will see that the Telerik.WinControls.PdfViewer.dll is not installed because is not included in the package. Workaround: Download the zip file with Dlls and themes only (Telerik_UI_For_WinForms_2014_3_14_1202_Dev_hotfix.zip) from your account. Resolution: The new nugget package is added in our suite. Its name is UI.for.WinForms.PdfViewer.[Version].nupkg.
We just upgraded our WinForm UI from Q3 2013 to Q2 2014 and we started getting a "An unhandled exception of type 'System.TypeinitializationException' occurred in unknown module" before our 'Main' method is ever hit in Program.cs. This didn't occur when we referenced the Q3 2013 assemblies. I've attached the error and our reference list from Solution Explorer in VS 2013 Update 2.
Since version 2014.1.226 when adding a Telerik item template (e.g. RadForm) inside a project folder, VS extensions crash with the following error: System.NullReferenceException: Object reference not set to an instance of an object. at Telerik.VSX.Internal.ProjectManagement.ProjectFileLocator.GetProjectItemForPath(String relativePath) at Telerik.VSX.Internal.ProjectManagement.ProjectItemWrap.ContainedInProject(IProjectWrap porjectWrap) at Telerik.WinControls.VSX.TemplateProcessing.WFScenarioManager.Launch(IServiceProvider serviceProvider, String itemName, String scenarioPath, String scenarioName) at Telerik.WinControls.VSPackage.VSItemTemplateWizard.LaunchScenarioManager(ServiceProvider serviceProvider, Dictionary`2 replacementsDictionary) at Telerik.VSX.VSPackage.ItemTemplateWizardBase.RunStarted(Object automationObject, Dictionary`2 replacementsDictionary, WizardRunKind runKind, Object customParams) at Telerik.VSX.VSPackage.WizardBase.<>c__DisplayClass5.<Microsoft.VisualStudio.TemplateWizard.IWizard.RunStarted>b__4() at Telerik.VSX.VSPackage.WizardBase.CatchExceptionAndSendReport(Action action)
To reproduce: - build a sample porject and sign it; - build the dlls from the source code using the OEMKEY approach, specifying the public token for the certain application; - use these dlls in the purposed application; - after withing more than 10 attempts, the evaluation copy message appears;
1. Extract in some folder the dev version dlls. 2. Open the Bin40 folder. 3. Try to start VisualStyleBuilder or ThemeViewer tool.
Upgrade utility miss to change the TelerikData.dll reference. In result, the reference remains pointing to older version of that assembly, which could lead to unexpected exceptions. Resolution: The issue is no longer reproduced. In Q3 2011 we introduced Upgrade Wizard which replace the Update Utility.
The strings in the Project Update Utility form are white on a white background, so they are invisible for the user.