Devenv.exe not closing after successful build

FinalBuilder Discussion
1

I have noticed that after several days of running automated daily builds I see a bunch of devenv.exe tasks listed in task manager.  It appears that perhaps visual studio is not closing properly after a successful build.  But, it doesn’t seem to happen every time.

Has anyone else seen this behavior?

It’s kind of an annoyance to have these processes out there hogging memory when they’re not doing anything.

Any ideas?

Thanks

Paul

2

Hi Paul,

Sorry to hear you’re having problems. What versions of FinalBuilder and Visual Studio are you using?

Are the builds finishing normally, or terminating? FB build 5.0.0.65 and above contains a fix where (previously) devenv.exe was sometimes being left around if you manually terminate the Build VS.Net action.

However, if the builds aren’t being terminated then that is a little stranger. I don’t think we’ve seen that before.

Regards,


Angus

3

I am using FB version 4.2.0.305 and Visual Studio 2003 SP 1.

No, the builds are finishing normally, no problems.

I’m not sure that the problem even lies with FinalBuilder.  I think it might be just that for whatever reason devenv.exe isn’t unloading, but I can’t pin down the exact set of circumstances that lead to this, which is why I was asking if anyone else had the same problem.

I will try and monitor the situation and see if I can figure out exactly what leads to this.

Thanks for your help.