If there's a better newsgroup to post this in, please let me know.
I've been working on a mixed application - back end .NET and front end
VB6.0.
I've always been able to start the back end in the .NET debugger, and have
it start VB6.0. I could then run the front end in its own debugger, and by
dint of appropriately placed breakpoints move back and forth between the two
debuggers.
We've been interested in the possibility of moving to the new Team
Foundations Source Control, so I loaded the Team Explorer (and thereby the
2.0 Framework) on my development machine.
Alas! If I now start both debuggers, as had been my wont, the entire front
end closes down the first time I try to instantiate a class from the back
end. All of VB6.0 closes down.
The only way I've found to debug the back end is by having it write messages
to the event viewer - rather a primitive method.
Since I'm not actually using any of Team Foundations at this time (I just
have it loaded on my machine), my suspicions turn towards having the 2.0
Framework installed.
But of course the problem could be somewhere else entirely.
Any thoughts?
- Turtle
I've been working on a mixed application - back end .NET and front end
VB6.0.
I've always been able to start the back end in the .NET debugger, and have
it start VB6.0. I could then run the front end in its own debugger, and by
dint of appropriately placed breakpoints move back and forth between the two
debuggers.
We've been interested in the possibility of moving to the new Team
Foundations Source Control, so I loaded the Team Explorer (and thereby the
2.0 Framework) on my development machine.
Alas! If I now start both debuggers, as had been my wont, the entire front
end closes down the first time I try to instantiate a class from the back
end. All of VB6.0 closes down.
The only way I've found to debug the back end is by having it write messages
to the event viewer - rather a primitive method.
Since I'm not actually using any of Team Foundations at this time (I just
have it loaded on my machine), my suspicions turn towards having the 2.0
Framework installed.
But of course the problem could be somewhere else entirely.
Any thoughts?
- Turtle