There is also a problem when running mvn install in the command line while VS addin is running and the project is making use of Castles Dynamic Proxy. check the error below:
[INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] C:\Documents and Settings\rlhof\.m2\pab\gac_msil\NMaven.VisualStudio.Addin\0.14-mae stro-1.5.2-M3__NMaven.VisualStudio\Castle.DynamicProxy.dll (The process cannot access the file because it is being used by another process) we can remove this one by changing this one to Processes because we wont need it for marshaling the commands sent to the webservice bong wrote: > > We could stop the process though by calling proc.Kill() to kill running > child process in the > OnDisconnection method of NMaven.VisualStudio.Addin.Connect class > > > Evan Worley wrote: >> >> I don't believe this is the case if the parent process terminates >> unexpectedly. Have you tried that scenario? You should be able to make >> this happen by using the windows task manager to kill the VS process. >> >> On Thu, Apr 3, 2008 at 12:03 AM, Leopoldo Agdeppa <[EMAIL PROTECTED]> >> wrote: >> >>> Hello >>> >>> Using the System Diagnostics.Process in Calling NMaven, once the VS is >>> exited, by default on windows processes exists its child processes, and >>> I >>> have confirmed this by exiting VS while running a maven build, >>> >>> in this way, we won't need to keep communicating with the server just to >>> know if VS is still running, windows will handle the child process >>> termination automatically and cleanly >>> >>> thanks >>> bong >>> >> >> > > -- View this message in context: http://www.nabble.com/Embedder-vs.-System.Diagnostics.Process--tp16405147p16626733.html Sent from the nmaven-dev mailing list archive at Nabble.com.
