When trying to compile an indicator that I'm working with in the editor, NT will give compile errors on *.cs files that are not even loaded into memory. IOW, it is going out to disk and trying to compile *.cs files that I'm not even currently using or calling from the current *.cs file. Not sure if this is an "intended behavior", but I don't think its a good idea.
IMHO, it should try to compile the currently loaded *.cs. BTW, it will not compile the currently loaded *.cs, even if it has no compile errors, until you first fix the *.cs files with the errors on disk.
Very unusual for a programming environment.
Brooks

Comment