Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 02 Oct 2013 14:00 by ADMIN
ADMIN
Cody
Created on: 12 Feb 2013 17:24
Type: Bug Report
1
TS installs Newtonsoft.Json.dll in the GAC which breaks our apps
We are evaluation Telerik Test Studio as a possible replacement to the Microsoft testing tools.    However, I noticed that you install the Newtonsoft.Json.dll in the GAC.  We also use that particular dll in the products we develop and having Telerik Test Studio installed causes our products not to run -- getting a runtime binder exception on the Newtwonsoft.Json.dll.  

Why are you installing this dll in the GAC?  This is a common, opensource dll that should not be placed in the global assembly cache.

This is a deal breaker for us, so I'm hoping you have an alternative.
6 comments
ADMIN
Daniel Djambov
Posted on: 02 Oct 2013 14:00 
Telerik: Issue is fixed and solution will be available in next product release in October 2013 - please check for product upgrade with latest internal build to get the problem resolved.
ADMIN
Andy Wieland
Posted on: 07 Aug 2013 15:44 
I have a potential customer who is using TeamCity CI (DealerOn), and this has been identified as a deal-breaker for them.  They would like to know if it is possible to get this fixed in a hotfix prior to SP1, or if there is any timeframe we can pass on to them.

Thank you!
Andy W
ADMIN
Konstantin Petkov
Posted on: 07 Jun 2013 07:20 
Unfortunately we have to add the assembly back to GAC for the upcoming 2013 R1 of Test Studio. A number of critical issues popped up which we are unable to address otherwise in time.

This problem is top priority in our list to work on post R1.
ADMIN
Konstantin Petkov
Posted on: 11 Apr 2013 07:21 
This has been also addressed with internal build 2012.2.1527. Please contact the support team if you need assistance.
Andreas
Posted on: 11 Apr 2013 06:58 
We struggle with the same issue. In which version will the patch be included, and how to get is? Thanks!
ADMIN
Konstantin Petkov
Posted on: 15 Feb 2013 13:05 
The problem will be addressed via a custom build on top of the SP2 that is about to be released next week.
Create an account Log In
View
Type
Status