Unable to attach to application ...

[Greg Poirier]

I am unable to debug a VS.Net InfoPath project that uses managed code (C#
via the VSTO SDK).

Searching MSDN on this problem turns up a few suggestions about relaxing
permissions on some system resources, which I have done to no avail. I also
reviewed Min Park's blog on the subject(s):
http://blogs.msdn.com/mkpark/articles/86872.aspx.

When attempting to start an InfoPath project in debug mode, I receive the
error: "Unable to attach to application 'Microsoft Internet Explorer'
(PID:xxxx) on machine 'YYYYY'. If I choose the continue option, I get
"Unable to attach to machine'. (At present, the InfoPath app is published to
a shared folder on my machine only.)

Attempting to attach the debugger directly to the InfoPath process does not
work when selecting the 'common language runtime' option; this results in
'Unable to attach to process'' message. Selecting the 'native' option only
works when attaching, but of course my breakpoints are not honored

FWIW, I have .NET frameworks 1.0, 1.1, and 2.0 installed side-by-side.

Any suggestions would be appreciated.

 

[virgul]

Is your toolkit for infopath correct install and when you have install
office sp1 have you first uninstall infopath instal the sp1 and
reinstall infopath.

 

[Greg Poirier]

I was able to fix this problem by following the advice from
http://blogstogo.com/dotnet2/archive/2004/12/14/554.aspx.
It is interesting to note, that before finding this help, I had first tried
removing the .NET Framework version 2.0, but the problem still persisted.