Long running macro in .NET 2003 causes odd error message...

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

snichols - 23 Feb 2006 02:13 GMT

I have a very long-running macro for .NET 2003. In essence, it
traverses every code file in my solution and uses the code dom to do
some analysis and refactoring work. It will run for quite a long time
without issue. However, after a long enough run, I get the error
message "System call failed".

Is anyone aware of a built-in timeout on macro run time? It seems that
about 20 minutes is all I can get before the error pops up.

I've looked high and low for a method to offload the macro to another
thread for processing. I mean, I don't want to have the IDE freak out
on me. Can anyone point me in the right direction for this problem?

Any help would be appreciated!

steve

Reply to this Message

Boni - 23 Feb 2006 09:31 GMT

Hi Steve,
I had more or less the same problem, which I solved using try catch block.
I.E
1. copy list of files from DTE to arraylist
2.for each file in arraylist
try
do something
catch
log("error when processing file"+X)
end

Sometimes in batch process DTE seems to hang and generate exceptions. I just
retry after some delay.
HIH,
Boni

>I have a very long-running macro for .NET 2003. In essence, it
> traverses every code file in my solution and uses the code dom to do
[quoted text clipped - 12 lines]
>
> steve

Reply to this Message

snichols - 23 Feb 2006 16:57 GMT

Interesting. I see that step one involves copying a list of files from
DTE to your own list. Is that the preferred method of dealing with DTE
data? To copy it?

Also, do you implement your delay in the macro itself? Or do you rerun
your macro starting where it last left off?

steve

Reply to this Message

Boni - 24 Feb 2006 15:15 GMT

Hi Steve

> Interesting. I see that step one involves copying a list of files from
> DTE to your own list. Is that the preferred method of dealing with DTE
> data? To copy it?

For me it was a workaround. I dont think it is proposed way.

> Also, do you implement your delay in the macro itself? Or do you rerun
> your macro starting where it last left off?

Hear is pseudocode:

while counter<maxnumof repetitions
try
DoWork
exit while
catch (e as exception)
counter+=1
thread.sleep(100)
end catch
end while

With best regards,

Reply to this Message

snichols - 27 Feb 2006 19:53 GMT

Thanks for the info. Here's what I found:

VS .NET 2003 macros run in another process. They communicate with the
IDE via some form of IPC (Inter Process Communication). It seems that
the connection between the macro host and the IDE can be lost
occasionally.

When I converted my macro to an add-in, this problem was resolved.
Add-ins run in the same process as the IDE and, as such, they don't
lose connection.

steve

Reply to this Message

Long running macro in .NET 2003 causes odd error message...

Free Magazines