This question is locked. New answers and comments are not allowed.
Hey guys
I'm having an issue where I have a test studio project, with several dotnet libraries referenced. I added these references in the test studio standalone service. The problem is when I load the project in VS, it appears that the VS plugin automatically adds duplicate references.
So I have references in standalone that reference the DLL in C:\Windows\Microsoft.NET\etc etc etc and then VS adds references to C:\Program Files (x86)\Microsoft.net\etc etc etc
The program files cache is from installing the full .net SDK (which is my developer machine, makes sense).
The Problem: My test environments don't get the full .net SDK so when running projects that have been edited using the VS plugin and I get compile errors.
Current Solution: After making changes in the VS plugin, I have to reopen the project in the standalone client, and remove the duplicate DLL entries (C:\Program Files (x86)\etc etc etc) compile it, and the I can run it successfully.
Is there a better solution?
I'm having an issue where I have a test studio project, with several dotnet libraries referenced. I added these references in the test studio standalone service. The problem is when I load the project in VS, it appears that the VS plugin automatically adds duplicate references.
So I have references in standalone that reference the DLL in C:\Windows\Microsoft.NET\etc etc etc and then VS adds references to C:\Program Files (x86)\Microsoft.net\etc etc etc
The program files cache is from installing the full .net SDK (which is my developer machine, makes sense).
The Problem: My test environments don't get the full .net SDK so when running projects that have been edited using the VS plugin and I get compile errors.
Current Solution: After making changes in the VS plugin, I have to reopen the project in the standalone client, and remove the duplicate DLL entries (C:\Program Files (x86)\etc etc etc) compile it, and the I can run it successfully.
Is there a better solution?
4 Answers, 1 is accepted
0
Jon
Top achievements
Rank 1
Rank 1
answered on 21 May 2013, 05:25 PM
SOLVED:
Something must have gone wonky in my configs.
I rebuilt the VS project and everything seems to be playing nicely.
Something must have gone wonky in my configs.
I rebuilt the VS project and everything seems to be playing nicely.
0
Hello Jon,
Ivaylo
Telerik
We are glad you've managed to fix the issue you are experiencing.
Regards,Ivaylo
Telerik
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
Test Studio Trainings
0
Jon
Top achievements
Rank 1
Rank 1
answered on 04 Jun 2013, 04:20 PM
It appears that Visual Studio has readded the references.
Do you guys have any suggestions?
Do you guys have any suggestions?
0
Hello Jon,
Ivaylo
Telerik
I am sorry to hear you are experiencing this issue again.
Could you please provide me with the exact steps I need to follow in order to reproduce this behavior and investigate further. You can also add a short video demonstration of the problem you are experiencing. Jing is a quite useful screencast software you can use.
Looking forward to hearing from you.
Ivaylo
Telerik
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
Test Studio Trainings