Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 Incompatibilies with AQTime ?

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
Kakashi Posted - Jun 13 2007 : 12:30:08 PM
Hi,

I'm currently evaluating Visual Assist X with VS2005 and noticed an incompatibility with the AQTime add-in ( http://www.automatedqa.com/products/aqtime/ ).

Whenever you add an AQTime project to your solution (or then even open a solution with an AQTime) to benchmark the code (at least C code) and then you close Visual Studio 2005, the devenv.exe process doesn't exit.

I know that as using the evaluation, I am not eligible for support, but I thought I would tell you anyway as other person may have this problem or may encounter some day and that it prevents me from buying your product.

I'll try to contact AQTime as well in the meantime so they can test their product as well...

Thanks in advance,
15   L A T E S T    R E P L I E S    (Newest First)
Kakashi Posted - Aug 27 2007 : 5:43:27 PM
Thank you feline.

I'm really looking forward to this to buy the product.

Thanks again.
feline Posted - Aug 24 2007 : 08:44:38 AM
Is there no sign of a beta release for AQTime? I recall seeing an email go by about a beta release of TestComplete a little while ago.

I will ask about a fix for this inside VA.
Kakashi Posted - Aug 23 2007 : 1:03:46 PM
Hi,

Will the next version of VAX fix this ?
According to what the AQTime folks say, it is a problem in both VAX and AQTime, so I guess that any of you fixing the problem and releasing a new version should fix this problem.

So far, none of AQTime or VAX have released a version fixing this internally fixed problem (I've waited a bit before posting again anticipating a new version, but the problem is still there with VAX 1559).

I would appreciate if you could tell me what are the plans regarding this.

Thanks a lot in advance,

Kakashi.
feline Posted - Jul 20 2007 : 11:45:00 AM
This is good news, thank you for the update.
n/a Posted - Jul 19 2007 : 2:55:50 PM
Hello,

Please take a look at this post:

http://www.automatedqa.com/forums/d.cgi?cmd=article&group=automatedqa.public.aqtime&item=3722&utag=
feline Posted - Jun 25 2007 : 2:12:17 PM
Are you seeing any problems while the IDE is running and you are working?
Hopefully the problem only shows up when shutting down the IDE.
Kakashi Posted - Jun 25 2007 : 10:36:16 AM
Hi Feline,

Thanks a lot for your time and efforts in reproducing the bug and glad it was assigned an case ID.
I think it is a bit strange too : Visual Studio needs to restart once during the installation (after Document Explorer, IIRC), while it doesn't need to restart at all on Win2003 (install everything in one go without requiring any reboot).
It is the only difference I can think of (asides differences on the system DLLs etc, obviously), between WinXP and Win2003 when it comes to Visual Studio.

Thanks again.
feline Posted - Jun 23 2007 : 3:05:43 PM
I have reproduced the problem here, but so far no idea why it happens:

case=7257

The fact it is OS specific is a little odd, normally problems with VA don't care about the OS.
feline Posted - Jun 22 2007 : 12:05:04 PM
As an aside I am *so* impressed with the security settings in Windows 2003 and IE 7 *rolls eyes*

I run windows update, to make sure I have SP2, and all the other patches installed. I am told I must add this site to my list of secure sites before it will work. However I cannot add it, since it is not a secure site - the URL starts "http:" not "https:"

Lets just hope I don't need to run windows update to reproduce this.
feline Posted - Jun 22 2007 : 07:56:31 AM
I am off to create a Win2003 machine now, that is one OS I don't currently have installed.
Kakashi Posted - Jun 21 2007 : 2:11:37 PM
Hi,

Sorry for the time it has taken to come back to you but I couldn't find time to do some more proper and serious testing until today.

I tried on two Virtual Machines :

The first one with Windows XP SP2 fully patched.
The second one with Windows Server 2003 SP2 fully patched.

and the same versions of VAX and AQTime.
Nothing else is installed at all than default Windows + VS2005 SP1 + VAX + AQTime (tried changing the order of install of these last two, but the outcome is the same)

Everything seems to work fine with Windows XP : no ghosts devenv.exe at all, but it happens with Windows 2003 SP2 as it does on my machine.

Can you please try to reproduce this ?

Also, my investigations seem to show that the VAX components unload successfully, but that the ghost devenv.exe still have the aqtoolwin.dll loaded, which seems to indicate a problem with AQTime since VAX has already exited, but maybe VAX is doing something preventing AQTime to exit itself properly, or something like that, since there is no problem with exiting devenv when only AQTime is installed, even on Win2003.

I'll post a message on the AQTime forum inviting them to take a look at this thread too.
Hopefully, everyone will be able to collaborate with each other since incompatibilities like that hurt your both businesses, no matter whose "fault" it is.

PS: The easiest way to reproduce this is to open up VS2005 and then create a new AQTime project on an empty solution, then exit VS2005 and check for the ghost devenv.exe...
feline Posted - Jun 14 2007 : 10:24:43 AM
I completely missed that new menu item

Now I know it is there I have added a AQtime project to my test solution, using win2k, VS2005 professional SP1 and VA 1557. I am not seeing any problems here at all.

I am wondering if this is an OS specific problem. They are rare, but not unheard of.

Do you see this problem if you create a new default project in VS2005, and then add an AQtime project? Some difference in our projects, or settings, is an obvious place to look for the cause of the problem.

Do you have any other plugin's installed in the IDE?
Kakashi Posted - Jun 13 2007 : 2:40:04 PM
If it helps, I generated this log file :


DLLMain {
} DLLMain
DllGetClassObject {
} DllGetClassObject
OnConnection {
	GetRegValue {
	} GetRegValue
	OC1
	SubClassWin {
	} SubClassWin
	OC3
	ComSetup {
		GetRegValue {
		} GetRegValue
		SetMainWnd
		WTComSetup
	} ComSetup
	Register events {
	} Register events
} OnConnection
OnAddInsUpdate {
} OnAddInsUpdate
BeforeExecute {
} BeforeExecute
BeforeExecute {
} BeforeExecute
BeforeExecute {
} BeforeExecute
BeforeExecute {
} BeforeExecute
BeforeExecute {
} BeforeExecute
BeforeExecute {
} BeforeExecute
WM_SETTEXT {
} WM_SETTEXT
OnStartupComplete {
	CCOMSetup {
		DLLMain {
		} DLLMain
		DLLMain {
		} DLLMain
		DLLMain {
		} DLLMain
		DLLMain {
		} DLLMain
		OK
	} CCOMSetup
	GetRegValue {
	} GetRegValue
	GetRegValue {
	} GetRegValue
	GetRegValue {
	} GetRegValue
	Testing events {
		Testing events
		BeforeExecute {
		} BeforeExecute
		AfterExecute {
			VisualAssistX.Options
		} AfterExecute
		Receiving events
	} Testing events
	VA_CurrentWnd {
	} VA_CurrentWnd
} OnStartupComplete
BeforeExecute {
	BeforeExecute2 {
		Edit.GoToFindCombo
	} BeforeExecute2
} BeforeExecute
VA_CurrentWnd {
} VA_CurrentWnd
BeforeExecute {
	BeforeExecute2 {
		Edit.GoToFindCombo
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		
	} BeforeExecute2
} BeforeExecute
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DllCanUnloadNow {
} DllCanUnloadNow
BeforeExecute {
	BeforeExecute2 {
		
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		Edit.GoToFindCombo
	} BeforeExecute2
} BeforeExecute
OpenProject {
	p2
	p3
	GetIncludePath {
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
	} GetIncludePath
	OpenProject {
		
	} OpenProject
} OpenProject
VA_CurrentWnd {
} VA_CurrentWnd
DLLMain {
} DLLMain
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
VA_CurrentWnd {
} VA_CurrentWnd
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
BeforeExecute {
	BeforeExecute2 {
		AQtime.Profile.AddAQtimeProject
	} BeforeExecute2
} BeforeExecute
DLLMain {
} DLLMain
DLLMain {
} DLLMain
VA_CurrentWnd {
} VA_CurrentWnd
BeforeExecute {
	BeforeExecute2 {
		
	} BeforeExecute2
} BeforeExecute
VA_CurrentWnd {
} VA_CurrentWnd
WM_SETTEXT {
} WM_SETTEXT
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
AfterExecute {
	AQtime.Profile.AddAQtimeProject
	VA_CurrentWnd {
	} VA_CurrentWnd
} AfterExecute
DLLMain {
} DLLMain
VA_CurrentWnd {
} VA_CurrentWnd
DLLMain {
} DLLMain
BeforeExecute {
	BeforeExecute2 {
		AQtime.Profile.Profilers
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		AQtime.Profile.Profilers
	} BeforeExecute2
} BeforeExecute
OpenProject {
	p2
	p3
	p4
	GetIncludePath {
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		SetRegValue {
		} SetRegValue
		GetRegValue {
		} GetRegValue
	} GetIncludePath
	OpenProject {
		
	} OpenProject
} OpenProject
VA_CurrentWnd {
} VA_CurrentWnd
BeforeExecute {
	BeforeExecute2 {
		
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		Edit.GoToFindCombo
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		AQtime.Profile.Profilers
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		Edit.GoToFindCombo
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		Edit.GoToFindCombo
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		AQtime.Profile.Profilers
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		Edit.GoToFindCombo
	} BeforeExecute2
} BeforeExecute
BeforeExecute {
	BeforeExecute2 {
		File.Exit
	} BeforeExecute2
} BeforeExecute
AfterExecute {
	File.Exit
	VA_CurrentWnd {
	} VA_CurrentWnd
} AfterExecute
WM_SETTEXT {
} WM_SETTEXT
OnBeginShutdown {
	Register events {
	} Register events
} OnBeginShutdown
DllCanUnloadNow {
} DllCanUnloadNow
OnDisconnection {
	SetRegValue {
	} SetRegValue
	od1
	UnSubClassWin {
		DLLMain {
		} DLLMain
	} UnSubClassWin
} OnDisconnection
DllCanUnloadNow {
} DllCanUnloadNow
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain
DLLMain {
} DLLMain

Kakashi Posted - Jun 13 2007 : 1:58:03 PM
Thanks for your very quick reply and sorry for my lack of details.

VS2005 Professional Edition - Version 8.0.50727.762 (SP.050727-7600)
OS: Windows Server 2003 SP2 fully patched as of today.

AQTime version : the latest one, same than the one you downloaded on the website.

VAX : Latest too (1557)

The problem occurs when you add a AQTime project to the solution, which you do by accessing the "Add AQTime project" item located in the (discretly named) "Profile" menu that AQTime added to VS2005.

AQTime should also display itself in the list of the VS products installed on the VS2005 splash-screen.
You can also see it on the IDE about dialog box.

From that moment you add the AQTime project, exiting Visual Studio should result in the ghost devenv.exe never disappearing from the task manager (and every subsequent Visual Studio openings results in its own ghost devenv.exe still running in the background).

If you open a project without an AQTime solution or a single C file not part of a project or a solution, the ghost devenv.exe issue doesn't occur.
It isn't only when reopening a solution having an AQTime project in that solution.

I'm reporting this here because I noticed that this problem doesn't occur when I uninstall Visual Assist X.

Thanks a lot for your help, and feel free to ask more details if needed or if you can not reproduce it.

PS: I just retried on a separate machine (same VS2005 and OS, VAX and AQTime from the website, just different hardware... and the same happens.
feline Posted - Jun 13 2007 : 1:04:49 PM
Which version of VS2005 are you using? Which version of AQtime are you using?

I have just installed "AQtime520x86Demo.exe" on a win2k machine. During the install I made sure that I selected VS2005, VS2003 and VC6 integration. I have all 3 IDE's installed on this test machine.

However when I run VS2005 there is no sign of any AQtime plugin or extension. When I look in:

IDE tools menu -> Add-in Manager -> list of available add-ins

only VAX is listed. I am not seeing any problems loading or quitting VS2005 with VA 1557 installed.

Have I missed some step?

We would certainly like to try and fix this problem, even though you are only evaluating VAX.

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000