This is a migrated thread and some comments may be shown as answers.

Converting to coded step removes(?) System assembly

7 Answers 50 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Alan
Top achievements
Rank 2
Alan asked on 08 Aug 2012, 11:32 PM
Hello,

I converted a step to a coded step in my test file 'Policy_Coverage'.  When attempting to execute, I receive the errors below, all of which are in a different test file 'GL_Smoke_Driver'.  The execution worked fine before I converted to code, and when I remove the Policy_Coverage.cs file, execution is normal again.  I double checked the assemblies and they are all there.  What the heck happened?

j:\...\GL_Smoke_Driver.tstest.cs: Line 9: (CS0234) The type or namespace name 'Data' does not exist in the namespace 'System' (are you missing an assembly reference?)
j:\...\GL_Smoke_Driver.tstest.cs: Line 11: (CS0234) The type or namespace name 'Xml' does not exist in the namespace 'System' (are you missing an assembly reference?)
j:\...\GL_Smoke_Driver.tstest.cs: Line 78: (CS0246) The type or namespace name 'SqlConnection' could not be found (are you missing a using directive or an assembly reference?)

Many thanks,
Alan

7 Answers, 1 is accepted

Sort by
0
Alan
Top achievements
Rank 2
answered on 09 Aug 2012, 03:10 PM
Well, it's miraculously working this morning.  I'll continue to monitor in case this happens again.
0
Cody
Telerik team
answered on 09 Aug 2012, 03:52 PM
Hello Alan,

Thank you for the update! While I don't like things that miraculously fix themselves, I'm also a firm believe in "if it ain't broke, don't fix it". We'll be here if you need further assistance.

Greetings,
Cody
the Telerik team
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
0
Alan
Top achievements
Rank 2
answered on 21 Aug 2012, 03:29 PM
Hi there...me again...

I am getting this error again after upgrading a script from the old version 2012.1.411 to the new version 2012.1.719 on two scripts with only the three errors duplicated as above (Data, Xml, SqlConnection).  The other scripts received the update perfectly.  Let me know if you think an assembly dropped off or was renamed, etc.  I'll zip the project into a support ticket if needed.

Thanks!
0
Accepted
Cody
Telerik team
answered on 21 Aug 2012, 10:01 PM
Hello Alan,

First please try adding assembly references to System.Data and System.Xml as shown in the attached screen shots. Be sure you're pulling from the folder C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0.

If that doesn't help then yes please do send me the entire project for analysis.

Kind regards,
Cody
the Telerik team
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
0
Alan
Top achievements
Rank 2
answered on 21 Aug 2012, 10:40 PM
Thanks!  That did the trick.  I remember including those at one time, so I wonder where they went.  I also needed System.Windows.Forms.dll in addition to the two you specified above.

Thanks again for the help!
0
Cody
Telerik team
answered on 24 Aug 2012, 09:03 PM
Hello,

It's possible this was caused when we upgraded Test Studio to use .NET 4.0 instead of .NET 3.5. If you added the .NET 3.5 assemblies in the past then upgraded Test Studio to a .NET 4.0 version, the old .NET 3.5 assemblies would not be compatible and taken out. In the scenario you have to manually add the .NET 4.0 equivalent assemblies back in.

Regards,
Cody
the Telerik team
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
0
Alan
Top achievements
Rank 2
answered on 27 Aug 2012, 12:43 PM
That makes perfect sense...I bet that's what happened.  Thanks again for the help!
Tags
General Discussions
Asked by
Alan
Top achievements
Rank 2
Answers by
Alan
Top achievements
Rank 2
Cody
Telerik team
Share this question
or