The tool should build the assemblies as described here: http://www.telerik.com/help/winforms/installation-deployment-and-distribution-redestributing-telerik-radcontrols-for-windows.html
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)
One of the programs we develop is internal, and this makes it a good testing ground for the Telerik updates to make sure there aren't any bugs that will negatively impact customers using the other software we sell. When using the Telerik Control Panel to update to a newer version of Telerik, older versions are forced to be uninstalled. This requires us to go back and reinstall the older versions immediately afterwards until we're ready to update our other software to the latest version of Telerik. It would be very helpful if we could install newer versions without the requirement of uninstalling the older versions. Thank you!
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.
This way, one will be able to connect to e virtual machine where the desired product is already installed and ready for use.
Currently RadControls for WinForms targeting .NET2.0 are always added to the GAC. This feature should be optional so customers can have in GAC only controls they use .
When a form has any RadControl on it and is configured to be localizable then a resource file is generated. For each RadControl on the form there are entries in the resource file that specify the current version of the RadControls. Implement update of the
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.
Stop Expanding ALL the Telerik Toolbox control groups when Visual Studio 2017 loads a project! YES, we know your there! We PUT you there.. If we need you, we know where you are! Please quit over-convoluting the toolbox menu by obnoxiously expanding all your toolbox control groups!
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: - 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;
The strings in the Project Update Utility form are white on a white background, so they are invisible for the user.
1. Extract in some folder the dev version dlls. 2. Open the Bin40 folder. 3. Try to start VisualStyleBuilder or ThemeViewer tool.
Our development process includes several applications that use the UI for WinForms. As such, we will download the latest release and evaluate all of our applications against it prior to updating all of our developers and our build servers. However, using the Control Panel does not provide any option for maintaining the previous install, so whichever developers are doing the evaluation have to manually reinstall the prior version, or manually install the new version, in order to be able to roll back if we decide not to adopt the latest release. Please add an option in the control panel to maintain the previous version when installing updates.
I see no use for the templates that are currently provided. I'm never going to build a new Word or Outlook type application. Some templates that might be useful would be along the lines of structure for business apps. Something that would give a framework for building apps for business use.
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
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.