Visual Studio usage

[daqu40]

Hello Forum,

This applies to all development using Visual Studio...

Does anyone know why sometimes when using VS it provides intellesense and autocomplete of NinjaTrader methods and objects and other times VS is completely unaware of NinjaTrader?

Thanks!

[NinjaTrader_JoshG]

Hello daqu40,
Thanks for your post.

What version of NinjaTrader 8 are you using?

What version of Visual Studio?

Are you opening up Visual Studio through the NinjaScript editor?

[daqu40]

Thanks for look into this Josh,

NT8: Version 8.0.16.3 - 64 bit

VS 2017 Community: Version 15.9.3

I typically don't open VS from Ninja's editor, but I've tried both and it didn't seem to matter.

If I open outside of NT8, I then open the Ninjatrader.Custom.csproj project to start working on NT8 stuff.

[NinjaTrader_JoshG]

daqu40,

Happy to help.

Although it should not really be necessary after the first time, I typically suggest only running Visual Studio through the NinjaScript editor. This is because that is the only way that is documented in the Help Guide.

Do you find that this issue ever occurs when you open VS through the NS Editor?

[daqu40]

Thanks again Josh,

This detachment seems to have become permanent recently. It used to be sometimes VS behaved like the NT Editor (but with all the extra goodies in VS) and sometimes it didn't. I've no idea what made it work and not work.

Now I never seem to get the autocomplete or intellisense that is away of NinjaTrader classes. This is how it comes regardless of how I launch VS.

[NinjaTrader_JoshG]

daqu40,

Are you saying that intelliSense is not working in VS even when NinjaTrader.Custom is open?

Have you tried reinstalling VS?

[daqu40]

Sorry if I wasn't clear. IntelliSense works, but only for standard C# .Net classes. Nothing from NT8 is present. However, in the past it would work sometimes.

For example if type "Posito" in VS this is what its IntelliSense responds with image1. If I do the same in the NT8 Editor I get image2.

In the past there were times where I could get image2 in both NT and VS.

[NinjaTrader_JoshG]

daqu40,

I do appreciate the screenshots, but I feel that this does not directly answer either of my questions. I cannot see if you have the NinjaTrader.Custom project open and I still do not know if you have tried reinstalling VS.

If you have already done both of these things than I would suspect something is going on with the your NT installation.

[daqu40]

Thanks Josh,

I confirmed NinjaTrader.Custom is open by reopening it. Still not working.

I'll try reinstalling VS next.

[daqu40]

After reinstalling VS and opening the NinjaTrader.Custom project, still the same behavior.

Adding evidence of NT project as Image3.jpg

[daqu40]

[NinjaTrader_JoshG]

daqu40,

What specific file is open inside the solution when the IntelliSense fails to appear?

Please try opening the Visual Studio Add On Solution at the following help guide. It will be the third link from the top. Do you see IntelliSense working once you open that solution?
https://ninjatrader.com/support/help...t_overview.htm

Since we cannot directly support Visual Studio, the last thing I can suggest is reinstalling NinjaTrader through the Windows Control Center and then reinstalling. After that you would want to open VS through the NinjaScript Editor.

If that does not work I'm afraid the best thing will be to search some VS forums, as I do know this has been known to happen from time to time with non NinjaTrader items too.

[daqu40]

Yeah, Progress!

It works with the AddOn solution.

Ok so is there something missing from my solution or project file in the NT8 Custom folder?

[NinjaTrader_JoshG]

daqu40,

I suspect that something may not be getting included in the solution that you are trying to use intelliSense with.

While the file is open that does not have intellieSense, can you post a screenshot of your Solution Explorer?

[daqu40]

Will try shortly.

Now my TFS integration is giving me some errors.

Before I connect to TFS edited a few files from the Solution Explorer and IntelliSense was working.

Hopefully this remains working once I get the other issue resolved. I will report back.