 | |
VisStudio 2003 EnvDTE/automation interface causes exception
Visual Studio.net (General) microsoft.public.vsnet.general
 |
| | Thread Tools | Search this Thread | Display Modes |
#1
 
| |||
| |||
|
VisStudio 2003 EnvDTE/automation interface causes exception -
08-01-2003
, 04:47 AM
#2
| |||
| |||
|
|
Dave: Wish I had better news: I have had similar problems with both versions of VS.Net. We don't use BuildIt, but we do have some custom add-ins that interact with VS.Net. We get exactly the same exception (call was rejected by callee). All I can tell you is this: 1. I have made multiple posts to MS, but I have heard nothing of a fix. 2. For us, it only seems to happen if I run the code in the debugger. I have not yet gotten an error running "stand alone", outside of the debugger (makes it really hard to debug, you basically don't get to have a debugger) 3. I have received 2 suggestions from MS: 1. In VS.Net, go to tools | options and set to MDI Environment, instead of Tabbed. That seemed to work for me at first, but then the problem returned . 2. If you are running an AntiVirus scanner, like McAfee, turn it off. For me, it's not an option to run without antivirus protection, so I haven't tried it. If anyone else has had better luck, I'd love to hear about it. "Dave" <kdlevine (AT) wi (DOT) rr.com> wrote in message news:%23oB5oHBWDHA.3924 (AT) tk2msftngp13 (DOT) phx.gbl... I am working on automating our build process so I downloaded the BuildIT app. Based on it I wrote a test build app that uses the automation interface exposed through the EnvDTE object and I have run into several problems. I am using the latest version of DevStudio and all code is written in C#. Our solution has about 30 C# projects in it with some complex dependencies, and the release build produces two MSI files (client and server files). One problem I am currently having is that when I invoke the SolutionBuild.Build method it will grind away for some time and then throw an exception that "the call was rejected by the callee" (or something similar). I do not have this problem when I open and build a simple test solution. Another problem is that when I invoke the SolutionBuild.Clean method it does not appear to actually do anything. Is this method functional in the current release? Also, if a solution build fails is there any means of determining which project failed? There is a property called LastBuildInfo which simply returns a pass/fail indication....is that all I can get? Is there a means of capturing the build output so that I can get feedback during the build process? Thanks for any help provided, Dave L |
#3
| |||
| |||
|
|
Well, in that case have I got good news for you.... I googled up a solution to the problem. The problem is that the call takes so long to complete that COM times out. The way to fix is is to implement an IMessageFilter in the .net code that calls the interop layer. This is easier then it sounds (once someone has you how, that is). The code that does this is on a weblog by Shawn Ness. Here's a link to the fix... http://weblogs.asp.net/savanness/posts/6012.aspx Now all we have to do is get some MSFT dude to archive this so the next time someone asks... "J.Marsch" <jeremy (AT) ctcdeveloper (DOT) com> wrote in message news:u53yq7DWDHA.1676 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Dave: Wish I had better news: I have had similar problems with both versions of VS.Net. We don't use BuildIt, but we do have some custom add-ins that interact with VS.Net. We get exactly the same exception (call was rejected by callee). All I can tell you is this: 1. I have made multiple posts to MS, but I have heard nothing of a fix. 2. For us, it only seems to happen if I run the code in the debugger. I have not yet gotten an error running "stand alone", outside of the debugger (makes it really hard to debug, you basically don't get to have a debugger) 3. I have received 2 suggestions from MS: 1. In VS.Net, go to tools | options and set to MDI Environment, instead of Tabbed. That seemed to work for me at first, but then the problem returned . 2. If you are running an AntiVirus scanner, like McAfee, turn it off. For me, it's not an option to run without antivirus protection, so I haven't tried it. If anyone else has had better luck, I'd love to hear about it. "Dave" <kdlevine (AT) wi (DOT) rr.com> wrote in message news:%23oB5oHBWDHA.3924 (AT) tk2msftngp13 (DOT) phx.gbl... I am working on automating our build process so I downloaded the BuildIT app. Based on it I wrote a test build app that uses the automation interface exposed through the EnvDTE object and I have run into several problems. I am using the latest version of DevStudio and all code is written in C#. Our solution has about 30 C# projects in it with some complex dependencies, and the release build produces two MSI files (client and server files). One problem I am currently having is that when I invoke the SolutionBuild.Build method it will grind away for some time and then throw an exception that "the call was rejected by the callee" (or something similar). I do not have this problem when I open and build a simple test solution. Another problem is that when I invoke the SolutionBuild.Clean method it does not appear to actually do anything. Is this method functional in the current release? Also, if a solution build fails is there any means of determining which project failed? There is a property called LastBuildInfo which simply returns a pass/fail indication....is that all I can get? Is there a means of capturing the build output so that I can get feedback during the build process? Thanks for any help provided, Dave L |
|
« Previous Thread
|
Next Thread »
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.