I am trying to learn how to use Visual studio to Manipulate test studio test.
I followed instructions from this link https://docs.telerik.com/teststudio/features/test-maintenance/export-visual-studio
When i choose to open the file in Visual studio i get error i click ok and nothing visually happens in visual studio.
if I open the .csproj file directly in visual studio i just see XML skeleton.
I have added some screen shots so that you can perhaps understand what im trying to do.
My team has 2 applications using Telerik.UI.for.AspNet.Core, one is using v2020.3.1118 and the other is using v2021.1.119. Each application up until now was worked on by 2 different developers, but now one developer has been assigned both applications.
The developer was originally working with v2020.3.1118 and has that installed on his machine via control panel. Now that he has been assigned the application with v2021.1.119, he can't build it until he installs the new version via control panel. The problem is that he has to uninstall the older version when the new version is installed (control panel seems to force this).
Is there something we are missing here, it seems odd to only allow one version to be installed at a time. We cannot update the older version to the newer without triggering a full QA regression (both manual and automated) that takes several weeks to complete before it goes into our release pipeline.
Scan.cshmtl via View:
@(Html.Kendo().Grid<Main_Kendo.Models.ScannerViewModel>() <--- Html.Kendo gets red underline error ???
columns.Bound(b => b.Scan).Width(140);
columns.Bound(b => b.BarcodeImage).Width(140);
columns.Bound(b => b.DropZone).Width(140);
columns.Bound(b => b.EnteredBy).Width(100);
columns.Bound(b => b.EnteredDate).Width(130);
columns.Command(command => command.Destroy()).Width(110);
The error message:
HtmlHelper <dynamic> doesn't contain a definition for Kendo and no accessible extension method for 'Kendo' accepting a first argument of type HtmlHelper
Already have ScannerViewModel in Models folder, Kendo.Mvc was missing references that I added.
This problem is back with the latest version of Telerik UI R2 2021 (2021.1.119).
After updating the packages using the Telerik Control panel no projects will build om Visual Studio 2019 and Nuget packages will not install.
C:\Program Files\dotnet\sdk\5.0.102\NuGet.targets(131,5): error : The local source 'C:\Program Files (x86)\Progress\ToolboxNuGetPackages' doesn't exist.
The workaround is to manually create this folder: 'C:\Program Files (x86)\Progress\ToolboxNuGetPackages'
In order to upgrade to new versions of products I have to uninstall all the existing ones, first. This takes a hundred years and is ridiculously slow.
Add an auto-uninstaller for updated products selected to be installed. That way, I can run it all overnight and, hopefully, it'll be done by morning.
running Control Panel always asks for an update, but when download progressbar display, app crash, with these details:
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
Server stack trace:
at Telerik.CommonInstaller.Application.ControlPanel.SelfUpdater.InitiateDownloader(String downloadAddress)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object args, Object server, Object& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(System.Runtime.Remoting.Messaging.Message, Boolean)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(System.Object, System.Runtime.Remoting.Proxies.MessageData ByRef)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessageSink)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
Faulting application name: ProgressControlPanel.exe, version: 2020.2.624.1, time stamp: 0x5ef36079
Faulting module name: KERNELBASE.dll, version: 10.0.19041.662, time stamp: 0xe6477cce
Exception code: 0xe0434352
Fault offset: 0x0012a892
Faulting process id: 0x2bc4
Faulting application start time: 0x01d6ca1c0fe4f7c7
Faulting application path: C:\Program Files (x86)\Progress\Control Panel\ProgressControlPanel.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: d06cad62-cf72-426e-b267-d03dd1cd40e9
Faulting package full name:
Faulting package-relative application ID:
After I update Telerik Control panel and several products (no issues reported). Then I went to open one of my UI for WPF projects and/or UI for UWP projects and VS 2019 starts to load the project then just gets into a "Not Responding" state. Waited 15 minutes, still same not responding so I had to "end task".
Any ideas of what the Telerik updates may have done to my VS environment?
I have configured the Control Panel to install my Telerik selection into "V:\Telerik".One entry in that directory is a folder "ToolboxNuGetPackages".
Last night I updated the Telerik libraries to the current version using the Progress Control Panel. A few minutes ago, I created a new solution for a WPF netcoreapp (in Jetbrains Rider), added references to the required Telerik libraries and tried to build the otherwise untouched solution.
It failed during the ResolvePackageAssets task, because nuget was unable to find the fallback package folder "C:\Program Files (x86)\Progress\ToolboxNugetPackages".
With a bit of help from StackOverflow I found that this setting is defined in the file "C:\Program Files (x86)\NuGet\Config\Telerik UI for WPF.config", and I for one did not put it there. In fact, I had changed it a few days ago,while investigating some other build failures; after all, it was a non-existing path, so things could not get worse. Now, after the update, the original path is back ... and as installer the Control Panel is my prime suspect.
So I'd like to ask somebody at Telerik to check if the Control Panel does write the contents of that file and if so, to make sure that it uses the actual location of the ToolboxNuGetPackages folder.
In my case, I changed the path to "V:\Telerik\ToolboxNuGetPackages", unloaded and reloaded the project and it built without further problems.
I tried to submit this via the "Get Technical Support" item in my account page, but the UI is so user-friendly that submissions for the Control Panel are impossible there.