• If this is your first visit, you will have to register before you can post. To view messages, please scroll below and select the forum that you would like to visits. Questions? Be sure to check out the Forum FAQ.

Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

The '...Indicator Name..." does not exist in the current context - CS0103

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    The '...Indicator Name..." does not exist in the current context - CS0103

    Hi All
    After a Windows update installed my NT7 platform suddenly cannot compile any indicator or strategy, even newly created blank indicators. All giving the error code above. I have tried reinstalling .Net framework and NT7 itself to no avail. Any pointers how I can try troubleshooting this, please?

    #2
    Which version of Windows?

    Comment


      #3
      Hello,

      Thanks for your post.


      When you compile all scripts are compiled together for performance, this is normal and expected. so if one script has an error, you will not be able to compile until all scripts are valid.

      Regarding the errors you are getting, it seems that the platform can not find the files listed. Can you check that they exist on the file system by opening the folder: Documents\NinjaTrader 8\bin\Custom\Indicators

      Look specifically for the files listed in the error with an @ at the begging or @ADL

      If they do not exist, likely you could exit the platform and do a re install and select Repair during the re install to place these files back.

      Can you check this and let me know if they exist or not before we continue?

      I look forward to being of further assistance.
      Marco G.NinjaTrader Customer Service

      Comment


        #4
        Hi Marco

        Thank you so much for the speedy response. It seems something did indeed corrupt my files. Normal uninstall and reinstall did not work. Restore form an older NT7 backup restored all files except the scripts. I manually deleted all of the custom scripts without the @ prefix, restart machine and NT7. Came up cleanly. Am able to work on NT7 as intended and I will have to rebuild one or two of the scripts from scratch. Thanks for the help.

        Comment

        Latest Posts

        Collapse

        Topics Statistics Last Post
        Started by rafaelabe1977, Today, 03:51 AM
        1 response
        9 views
        0 likes
        Last Post sledge
        by sledge
         
        Started by jenifeery79, Today, 05:03 AM
        0 responses
        4 views
        0 likes
        Last Post jenifeery79  
        Started by rexmie888, Today, 04:00 AM
        0 responses
        6 views
        0 likes
        Last Post rexmie888  
        Started by terminatorT1000, Yesterday, 06:40 PM
        1 response
        16 views
        0 likes
        Last Post NT-Roland  
        Started by cmarkb, Today, 02:15 AM
        4 responses
        16 views
        0 likes
        Last Post cmarkb
        by cmarkb
         
        Working...
        X