Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

How to get rid of this warning?

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

  • ETFVoyageur
    replied
    Thank you, Jessica. It will be really nice to not have all of those NT warnings, so my own stand out immediately.

    Leave a comment:


  • NinjaTrader_JessicaP
    replied
    This behavior was confirmed on our end. We will be investigating this further. Please keep an eye on the NinjaTrader 8 Release Notes page for updates and bugfixes.



    Leave a comment:


  • koganam
    replied
    Originally posted by NinjaTrader_JessicaP View Post
    Hello ETFVoyageur, one last question I had,



    I am unsure what the standard solution you are referring to here is. Do you have any web resources bookmarked, or file locations in a standard Ninja installation, that I can use as a starting point?
    Just read the text of the error. It is clearly saying that it is getting a clash between the source file from NT, and the Vendor.dll gumball file. These are being reached in the same space, so it is hardly surprising. There is no need to do anything special to see the warnings. Just build using VS, and you will see the warnings. Yes, even on a pristine, just installed, NT8, with absolutely nothing added. They pretty much always show up in VS, because it is how things are setup by NT itself.
    Warning CS0436 893 The type 'TextPosition' in 'Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs' conflicts with the imported type 'TextPosition' in 'NinjaTrader.Vendor, Version=8.0.0.12, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs'. Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs

    Leave a comment:


  • ETFVoyageur
    replied
    Originally posted by NinjaTrader_JessicaP View Post
    Hello ETFVoyageur, one last question I had,



    I am unsure what the standard solution you are referring to here is. Do you have any web resources bookmarked, or file locations in a standard Ninja installation, that I can use as a starting point?
    NT documentation says to go to the NT source editor and then click on the VS button (the last one on the right in the toolbar). That opens up Visual Studio using a solution and project that NT has provided. There is no documentation about how NT set up the solution and project, but surely your developers know that information. It does include all of the NT source for things NT wants us to have access to, such as NT indicators.

    Does that help?

    Leave a comment:


  • NinjaTrader_JessicaP
    replied
    Hello ETFVoyageur, one last question I had,

    Originally posted by ETFVoyageur View Post
    I am just using the standard solution that NT provides when I go to VS from the NT editor.
    I am unsure what the standard solution you are referring to here is. Do you have any web resources bookmarked, or file locations in a standard Ninja installation, that I can use as a starting point?

    Leave a comment:


  • ETFVoyageur
    replied
    Originally posted by NinjaTrader_JessicaP View Post
    That should be everything we need. I'll follow up with you as soon as we are able to reproduce and confirm this behavior, and again as we progress toward a solution.
    Thanks again Jessica. I appreciate your effort on this, and I am confident others also appreciate it.

    Leave a comment:


  • NinjaTrader_JessicaP
    replied
    That should be everything we need. I'll follow up with you as soon as we are able to reproduce and confirm this behavior, and again as we progress toward a solution.

    Leave a comment:


  • ETFVoyageur
    replied
    Originally posted by NinjaTrader_JessicaP View Post
    I believe it is likely something to do with the way the project is set up. It may be the case that zipping up a simple project surrounding a basic indicator or strategy, such as one of the ones NinjaTrader's wizards generate, may be the easiest solution.

    My goal is to collect enough information that our developers will be able to reproduce the same warning and error messages you are seeing, or at least most of them. This message in particular is likely due to a symbol name in one of our source files being similar to a symbol name in one of our dlls.

    If our developers can reproduce this on their end, they can resolve this query for a broad class of users, including yourself, using Visual Studio. We can not support Visual Studio directly; the NinjaTrader compiler is the only method of generating add-ons to NinjaTrader that we can fully document, that falls completely within the scope of our support. However, we do strive to make the user experience as terrific as we can for as many customers as possible.

    Any information you can give us that will lead to our developers having a complete picture, that will let them see what you are seeing, will be appreciated.
    Jessica,

    Thanks for being so helpful. I'm trying to cooperate. I am just using the standard solution that NT provides when I go to VS from the NT editor. The only change I have made is to add my own indicator and addon files. I have made no other content changes and I have made no project/solution changes of any kind. Is there some further information that would help you to help us?

    I agree that the large number of 0436 warnings is probably project setup. The 0618 warnings (only 4 of them) appear to be source file fixes needed -- the source is using obsolete functions -- scarcely a good example for developers who model after the provided indicators.
    Last edited by ETFVoyageur; 08-09-2016, 09:10 AM.

    Leave a comment:


  • NinjaTrader_JessicaP
    replied
    I believe it is likely something to do with the way the project is set up. It may be the case that zipping up a simple project surrounding a basic indicator or strategy, such as one of the ones NinjaTrader's wizards generate, may be the easiest solution.

    My goal is to collect enough information that our developers will be able to reproduce the same warning and error messages you are seeing, or at least most of them. This message in particular is likely due to a symbol name in one of our source files being similar to a symbol name in one of our dlls.

    If our developers can reproduce this on their end, they can resolve this query for a broad class of users, including yourself, using Visual Studio. We can not support Visual Studio directly; the NinjaTrader compiler is the only method of generating add-ons to NinjaTrader that we can fully document, that falls completely within the scope of our support. However, we do strive to make the user experience as terrific as we can for as many customers as possible.

    Any information you can give us that will lead to our developers having a complete picture, that will let them see what you are seeing, will be appreciated.

    Leave a comment:


  • ETFVoyageur
    replied
    Originally posted by NinjaTrader_JessicaP View Post
    Thank you very much for that information. Would it still be possible to get either a code sample, or the steps for compiling built-in NinjaScript code with Visual Studio that you are using?
    I'm not sure what you are asking for.
    • The information I gave you specifies the exact NT source file and line number causing the warning. Does that not meet your request for a source file exhibiting the issue?
    • Visual Studio -- I am using the solution provide by NT when I clicked on the "Open project in Visual Studio" button in the NT source editor. Visual studio puts up warnings and errors as I type. I can also use the standard VS build commands to be sure I generate all warnings, even though the result cannot be run by NT. Also, if I have a build error in the NT editor VS will display the errors and warnings when I move the focus back to VS.

    Leave a comment:


  • ETFVoyageur
    replied
    Here are the CS0436 warnings for @Text.cs, with duplicates removed. There are others, in other files, but far fewer than the total number of warnings would suggest -- many are duplicates that just occur in a different file. As far as I know the solution is not in the source files. Perhaps the way the project is set up?
    Warning CS0436 893 The type 'TextPosition' in 'Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs' conflicts with the imported type 'TextPosition' in 'NinjaTrader.Vendor, Version=8.0.0.12, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs'. Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs

    Warning CS0436 479 The type 'Text' in 'Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs' conflicts with the imported type 'Text' in 'NinjaTrader.Vendor, Version=8.0.0.12, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs'. Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs

    Warning CS0436 793 The type 'TextFixed' in 'Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs' conflicts with the imported type 'TextFixed' in 'NinjaTrader.Vendor, Version=8.0.0.12, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs'. Documents\NinjaTrader 8\bin\Custom\DrawingTools\@Text.cs

    Leave a comment:


  • NinjaTrader_JessicaP
    replied
    Thank you very much for that information. Would it still be possible to get either a code sample, or the steps for compiling built-in NinjaScript code with Visual Studio that you are using?

    Leave a comment:


  • ETFVoyageur
    replied
    I am using VS 2015 Community.

    All of the warnings come from NT software and/or project setup. Some are not reasonable for me to distill down. The following give the file name and line number (the number right after the warning number) which I hope is sufficient. This is everything I am seeing other than CS0436 (373 occurrences) -- let's discuss that separately.

    Warning CS0618 180 'FormattedText.FormattedText(string, CultureInfo, FlowDirection, Typeface, double, Brush)' is obsolete: 'Use the PixelsPerDip override' Documents\NinjaTrader 8\bin\Custom\SuperDomColumns\@Notes.cs

    Warning CS0618 145 'FormattedText.FormattedText(string, CultureInfo, FlowDirection, Typeface, double, Brush)' is obsolete: 'Use the PixelsPerDip override' \Documents\NinjaTrader 8\bin\Custom\SuperDomColumns\@ProfitLoss.cs

    Warning CS0618 239 'FormattedText.FormattedText(string, CultureInfo, FlowDirection, Typeface, double, Brush)' is obsolete: 'Use the PixelsPerDip override' Documents\NinjaTrader 8\bin\Custom\SuperDomColumns\@Volume.cs

    Warning CS0618 390 'FormattedText.FormattedText(string, CultureInfo, FlowDirection, Typeface, double, Brush)' is obsolete: 'Use the PixelsPerDip override' Documents\NinjaTrader 8\bin\Custom\SuperDomColumns\@APQ.cs
    Warning CS2002 1 Source file 'obj\Debug\TemporaryGeneratedFile_E7A71F73-0F8D-4B9B-B56E-8E70B10BC5D3.cs' specified multiple times Documents\NinjaTrader 8\bin\Custom\CSC

    Warning CS2002 1 Source file 'obj\Debug\TemporaryGeneratedFile_036C0B5B-1481-4323-8D20-8F5ADCB23D92.cs' specified multiple times Documents\NinjaTrader 8\bin\Custom\CSC

    Warning CS2002 1 Source file 'obj\Debug\TemporaryGeneratedFile_5937a670-0e60-4077-877b-f7221da3dda1.cs' specified multiple times Documents\NinjaTrader 8\bin\Custom\CSC
    Warning There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "PresentationCore", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.

    Warning There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "PresentationCore", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.

    Leave a comment:


  • NinjaTrader_JessicaP
    replied
    I understand and appreciate your concern. So that we may reproduce this on our end, could you provide us with some additional information?

    • Which version of Visual Studio are you using?
      • If you are using a commercial version of Visual Studio, is this reproducable with a community version?
    • Can you create a very basic "hello world" program which produces this message reliably and attach it to a reply here?
      • We would not need an entire Visual Studio project, just a file which will reproduce what you are seeing if added to a new project and any configuration details regarding the project itself needed to produce what you are seeing.

    We can then attempt to reproduce this on our end and return to you with our findings.

    Leave a comment:


  • ETFVoyageur
    replied
    Originally posted by NinjaTrader_JessicaP View Post
    Thank you for checking this log. This almost certainly means that this message is being suppressed by the NinjaTrader compiler, because it is known to be harmless. I am providing publicly available documentation on suppressing compiler warning messages distributed by MSDN so that you can configure Visual Studio to match the NinjaTrader compiler's configuration.

    https://msdn.microsoft.com/en-us/library/jj715718.aspx
    FWIW: I know how to configure VS. What would help is the list that NT thinks can be ignored.

    It would be good if NT could just fix the low-occurrence ones, such as CS0618 (4 occurrences). It warns about using an obsolete call, and I do not think developers should have to suppress that one.

    Leave a comment:

Latest Posts

Collapse

Topics Statistics Last Post
Started by kinfxhk, 07-13-2026, 10:18 AM
0 responses
26 views
0 likes
Last Post kinfxhk
by kinfxhk
 
Started by kinfxhk, 07-13-2026, 09:50 AM
0 responses
16 views
0 likes
Last Post kinfxhk
by kinfxhk
 
Started by kinfxhk, 07-13-2026, 07:21 AM
0 responses
22 views
0 likes
Last Post kinfxhk
by kinfxhk
 
Started by kinfxhk, 07-11-2026, 02:11 AM
0 responses
21 views
0 likes
Last Post kinfxhk
by kinfxhk
 
Started by SalmaTrader, 07-07-2026, 10:26 PM
0 responses
136 views
0 likes
Last Post SalmaTrader  
Working...
X