Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Platform: TradeLink, OpenQuant, considering anything that works...
Trading: if it trades...
Posts: 94 since Oct 2010
Thanks Given: 24
Thanks Received: 39
Is anyone have challenges when they add the partial classes (e.g. UserDefinedMethod) they are having problems in VS2010? I’m getting errors about some of the inbuild variables (e.g. AccountSize) not being defined.
Cheers,
drolles
Can you help answer these questions from other members on NexusFi?
After upgrading to VS2012 one of the things that frustrated me was lack of macros - which I used to create shortcut for attaching to NinjaTrader process.
After some time I found VS plugin that does just that and saves me about 6 clicks when debugging NinjaScript in VS2012.
Hi everyone. I've been doing a lot of debugging successfully with Visual Studio 2012. I just recently have been trying out Visual Studio 2013 for development but it seems that Debugging NinjaTrader with it is broken as no exceptions thrown in NinjaTrader are caught by Visual Studio, and no breakpoints are hit. Anyone else run into this?
I had the same thing with VS 2013 : when you're are in the debugging session, NinjaTrader.exe attached to VS 2013, try to recompile your indicator/strategy, it will then become "debuggable".