Problems on one PC: 'dotNET' is undefined
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2010
06:29 PM
07-20-2010
06:29 PM
Problems on one PC: 'dotNET' is undefined
Hello.
I have a dotNet .dll that I can't get the TestComplete 7.52 test script to access on one PC. It is a virtual PC running Windows/XP. Problem seems to start after the latest Windows Update.
It is working fine on other PC'es - and on the PC with problems I can run other .net applications outside TestComplete.
It seems not to be a problem with StrongNameVerification since this is set as on the other PC'es where I don't see the problem.
I have Reinstalled TC 7.52 and Executer after I checked that the .net class support was active - but still having problems.
The CLR-bridge property referes to my .dll as:
BK.Platform.Tools.TestTools.Helper.dll
and the instruction giving the error "'dotNET' is undefined" is:
var myFileIO = dotNET.BK_Platform_Tools_TestTools.FileIO.zctor();
What else can be relevant to check in TestComplete?
I have a dotNet .dll that I can't get the TestComplete 7.52 test script to access on one PC. It is a virtual PC running Windows/XP. Problem seems to start after the latest Windows Update.
It is working fine on other PC'es - and on the PC with problems I can run other .net applications outside TestComplete.
It seems not to be a problem with StrongNameVerification since this is set as on the other PC'es where I don't see the problem.
I have Reinstalled TC 7.52 and Executer after I checked that the .net class support was active - but still having problems.
The CLR-bridge property referes to my .dll as:
BK.Platform.Tools.TestTools.Helper.dll
and the instruction giving the error "'dotNET' is undefined" is:
var myFileIO = dotNET.BK_Platform_Tools_TestTools.FileIO.zctor();
What else can be relevant to check in TestComplete?
1 REPLY 1
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2010
08:16 PM
07-20-2010
08:16 PM
Hi Jan,
This problem seems to occur due to .NET Framework updates. See this SQAforums thread for a fix.
This problem seems to occur due to .NET Framework updates. See this SQAforums thread for a fix.
------
Yuri
TestComplete Customer Care Engineer
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
Yuri
TestComplete Customer Care Engineer
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
