Ninjascript file change notification issue

[wbennettjr]

There is some weird issue with the file change notifications when creating new indicators from Visual Studio. The file in visual studio is not updated to reflect the NT generated indicator code. If I go to the Ninjascript Editor and open the new indicator, make a change and compile, then it is updated in VS.

[NinjaTrader_DaveI]

Hello,

Just to be certain -- you are creating a new .cs file in VS, then you are presented with a prompt to update your VS project, correct? The NinjaScript generated code is added by the NinjaScript Editor itself, so this would be expected based on the order in which you are doing things, if I'm reading you correctly.

The recommended workflow is to create your new NinjaScript objects in the NinjaScript Editor, compile, then open your Custom project in VS. If your Custom project was already open, when you switch back to it, you should be prompted to reload the project, after which you should see your new class with the auto-generated code in your project.

[wbennettjr]

Thanks Dave. I guess I was going rogue and not following recommended practices

I have VS set to auto reload the file if it is saved and there are external changes. Everything works except for picking up the NT generated code. This seems weird to me as VS should be picking up file changes.

Do I need to add NinjaScript properties from the NinjaScript editor as well? I just tested and if I add a new property in VS, it does not see the updated generated code. If I go and open the indicator in the NinjaScript editor, I see the generated code was indeed updated. Seems the file is being updated in a way that does not trigger the file change notification in VS.

[NinjaTrader_DaveI]

There actually was an issue with the Custom project not updating as expected in the current release, and we have applied a fix to that issue which will be included in the next Beta release. It's a good bet that this issue is coming into play in your case.

No matter what you've added in VS (once the class is already present in the Custom project and has been compiled in the NS Editor), including properties, you should only have to save the project in VS, and the NS Editor should automatically update and compile, at which point VS should prompt you to reload the project with all of the new changes to the auto-generated code, if the auto-generated code has indeed updated.

Please keep this issue in mind to test in next Beta release, as I expect that you should see expected results at that time, and please let me know if you run into the same issue.