NinjaTrader Version 8.1.3.0 cannot debug anymore using visual studio

[junkone]

I downloaded the latest ninjatrader version.
i clicked on the "visual studio icon" in the ninjatrader code editor to launch VS
The VS launched is VS2022 Enterprise edition with version 17.7.4
I added the EMA indicator on the chart
I set a break point in @EMA.cs and followed the documented process to launch the debugger using the "attach process"
For reasons unexplainable, the VS believes the source code loaded is different from original version.
This is a new defect for the latest version as i have never seen this behaviour before.

[junkone]

i never had this issue until 8.1.3.0

and i am showcasing this as a issue that started with 8.1.3.0
I specifically demonstraetd the issue with a NT indicator @EMA.cs so you can try to reproduce it yourself..
Just to prove its a defect, here is a screenshot of the debugger on visual studio 2022 able to get into the breakpoints for @EMA.CS without any additional actions that i have to take

[-=Edge=-]

i never had this issue until 8.1.3.0

Could this possibly be your culprit!

https://forum.ninjatrader.com/forum/ninjatrader-8/add-on-development/1299280-8-1-3-0-crashes-on-attach-to-process-in-visual-studio-2022?p=1299292#post1299292

Please Be Save in this Crazy World!

[junkone]

I dont get a crash. and i am debugging @EMA.cs which is a ninja trader supplied indicator. so the posted article is not relevant

[junkone]

why is this behaviour different between Ninjatrader 8.0.27.1 vs 8.1.3.0.
Why is the source code changing and different from original when using

your own documentation makes no reference to this change in process.
https://ninjatrader.com/support/helpGuides/nt8/NT%20HelpGuide%20English.html?visual_studio_debugg ing.htm

Here is a recording of the debugging as you have indicated and there is a new popup(minute 1) that states that the source code has changed with a question!!!

Finally, i am a above average skilled programmer with decent skills in debugging. I know this has changed and if you tried to compare debugging between these 2, you will see how "annoying it is.

I still believe that its a defect caused by 8.1.3.0 compilation process and is very very annoying. Just imagine if i have multiple files that are on the debugger, i would be having multiple popups.

[junkone]

i disabled this flag from visual studio and dont see the popups anymore

[jeronymite]

As stated in post # 2, during compilation the open source code is compiled into NinjaTrader’s assembly source. The code that runs within NinjaTrader coming from the internal source is different than the open source script you are editing which is kept separate and exposed.

NinjaTrader_BrandonH This is rather confusing. It sounds like you are saying that, at one and the same time, the open source code that is compiled into the distributed NinjaTrader is both the same and different from the visible open source provided in the NinjaTrader distribution.

Can you clarify, please?

Thanks.

[nicthe]

Hello,

I am experiencing this issue. "Required source files to exactly match the original version" workaround will not work.



Microsoft Visual Studio Community 2022
Version 17.8.4
VisualStudio.17.Release/17.8.4+34408.163
Microsoft .NET Framework
Version 4.8.09032

[NinjaTrader_ChelseaB]

Hello nicthe,

After clearing this checkbox may I have you shutdown NinjaTrader and Visual Studio, and then restart both and re-attach the debugger?

Is the behavior the same, and is the checkbox still unchecked after restarting?