Error and weird behaviour in executable launch

[RandelPrandel]

Hello guys, 

So, finally got the app working again. The issue was with a few paths, which weren't transferring into the executable. so fixed 'em. 

I am still working on the accessibility of the block diagram on the app. But as my application doesn't really need the debug window on my executable, i chose lesser or the two evils, for now. 

I don't really want to do a remote debug session but if that's the only way to go, i will do that. 

But thanks for the invaluable input guys. I'll still keep this thread active for any new ideas to pour in  . 

Regards,

RP

[nathand]

---

RandelPrandel wrote:

I don't really want to do a remote debug session but if that's the only way to go, i will do that. 

---

Yes, that is the only way to go. The only way to access the block diagram of an executable (with debugging enabled) is through a remote debug session. The "Enable Debugging" switch allows you to do remote debugging; it never allows "in-application" debugging. You can debug an executable running on the same computer as the LabVIEW development environment but it's still a remote debugging session - you must use the development environment to do it. Did you try remote debugging, or were you hoping to do something else entirely?

[RandelPrandel]

Hey Nathan, 

You are on the money, I was trying to accomplish just that but did not know that there's no other way to do it. Thanks. 

I'll give remote deguggin a try and hopefully it'll work. 

Thanks again, 

RP