Debugging problem with version 8.1.2

[alexr]

VS -> Tools -> Options

[fx.practic]

alexr thank you very much.

[rgoudie]

I am also experiencing this issue. It is extremely inconvenient. My breakpoints are not being hit, so debugging is no longer useful.

With all due respect, it is not a solution to allow breakpoints to be hit. The breakpoints should be hit automatically as they have in all previous versions of NinjaTrader.

Why is NinjaTrader seeing files as being changed when they have not?

Thanks.

Edit: Just came back to state that the source code did not change between the automatic NinjaScript Editor compilation and the pressing of the Run button in the Strategy Analyzer. This is not part of the issue.

[alexr]

Even with source control turned off, I often have to hit the "Save" button in Studio to get the breakpoint up to date.
ps
And of course, when several projects are open at the same time, it's generally a complete mess with source code control.
ps.ps.
in general, about a third of the time is spent updating the source code for debugging

it is not acceptable

sorry for my english

[QuantKey_Bruce]

What you need to understand here is that when you click "Save" in Visual Studio, NinjaTrader's Script Editor has a FileSystemWatcher that sees the changed file and picks it up, and reapplies the template code at the bottom of the file that allows strategies to reference the indicators, then saves the file again (so that the updated template is also saved). It does this whether the template at the bottom has changed or not. This results in it being updated source code from a Visual Studio perspective, because Visual Studio also sees that the file has changed, and this means that you get a warning that the source code differs. Now that you have this understanding of what happens behind the scenes, what you are experiencing should make more logical sense, even if it is not how you want it to work ideally.

[alexr]

that is not indocator, just addon

upd. i.e. when the "Save" button is pressed, compilation and updating of the pdb takes place, which the studio still considers irrelevant))) but at the same time the breakpoints are updated.
I don't know the settings of the NT compiler, so it's hard for me to predict the behavior of the studio

[rgoudie]

I am trying to debug a strategy. It is important to remember that this issue is only appearing in the most-recent version of NinjaTrader. I never experienced this issue in any prior version.

[fx.practic]

I have a new issue: blue Windows "death screen" two times in a row.
Steps:
- run NT;
- run Visual Studio;
- attach;
- press "save" in Visual Studio.

Result: endless compilation ended with the "death screen".
Report emailed.

QuantKey_Bruce yeah, it's time to roll back. That's too much for me )

[QuantKey_Bruce]

Come back to 8.1.1.7. We have cookies.

[neo302]

Hello alexr,

You could hover your mouse over the breakpoint and follow the instructions in the breakpoint message seen below.

"To allow this breakpoint to be hit: click the 'Settings...' button that appears, then click 'Location', 'Allow the source code to be different from the original'.

After following those instructions the breakpoint will be hit.

After clicking the Settings button in that hover dialog the Location it mentions is the blue link at the top of the options. You can then check the box to allow the breakpoint and it will turn red/be hit. It will produce a warning the first time its hit and you can select yes to allow the breakpoint to be hit. After that it can be hit multiple times without warning.

I just upgraded and I'm having the same problem.
Is there anything new around this to have debugging work properly as it did before?

Thank you

[kkc2015]

QuantKey_Bruce Thank you for bring me back to my senses, if it is broken, go back to the previous functional model and enjoy some cookies.

[benJephunneh]

This is an issue with the latest update of NinjaTrader, just as endless compiling has become a problem with the update. It's strange that your software techs/engineers claim to have never across this issue, as if the only people who test your software are the customers. When I worked in software, I always understood the source of people's problems and whether it was fixable. NT seems to endlessly ask, "Send us your code. Send us your trace files. Did you do this and that? Did you finish your vegetables? Did you take your nap?" Etc. It's the same problem your techs came across when they tested the software, so why pretend the problem is with our code?