Announcement
Collapse
No announcement yet.
Partner 728x90
Collapse
NinjaTrader
.NET Classes
Collapse
X
-
Hi bertrand.
If I add a line - using System.Windows.Input; to the Using Declarations region I get the error "The type or namespace name 'Input' does not exist in the namespace 'System.Windows' (are you missing an assembly reference?) Error CS0234
On typing 'System.', possible choices are offered in a list, one item of which is Windows{}, So choosing that and adding the dot - using System.Windows. the only iem offered in the list is Forms{} but if you look at
Most of the types in this namespace support the Windows Presentation Foundation (WPF) input system. This includes device abstraction classes for mouse, keyboard, and stylus devices, a common input manager class, support for commanding and custom commands, and various utility classes. However, some of the types are applicable beyond WPF.
you will see the System.Windows.Input namespace.
Am I wrong to add this to the using declarations if I want to use classes within it?
Comment
-
Is there any documentation on this, It's new to me. When I do Add References I get a 'Select Assembly' window which invites me to look for Files of Type Assembly in a subfolder called Custom. There are a load of proprietary dll's in there along with some folders and -
NinjaTrader.Custom.dll and NinjaTrader.Vendor.dll
Not sure what to do next and don't want to experiment with it.
Comment
-
You need to add the DLL to the System.Windows.Input one you want. Browse to C:\Windows\Microsoft.NET\Framework\v2.0.50727 and select the correct DLL.
Edit: In fact, the DLL you are looking for is not available for .NET 2.0 which is what NT6.5 uses. You will not be able to use System.Windows.Input as the MSDN article states it is for .NET 3.5 only.Josh P.NinjaTrader Customer Service
Comment
-
From what I've read Ninja v7.0 supports .NET 3.5. Perhaps you could get on the Beta & target your App for that.
Dave
PS:
Be interesting to see what ships first. Ninja Trader 7.0 or Microsoft .NET 4.0.
TIP: if you are coding anything really ambitious in .NET, try loading up the Visual Studio 2008 Development environment & see if you can get your code to work there, You can get the express version for free http://www.microsoft.com/downloads/d...displaylang=en
Clearly what you can test is limited, but you can sort out the references, mousemove & other .NET logic bits. And it is a much richer diagnostic environment. You can also load the Ninja DLL's. You just can run it.
Comment
-
Thanks for your suggestions David. In fact I just wanted to try to get round NT6.5's lack of access to the keyboard in strategies. As you say, NT7 will use .NET 3.5, but that may mean that NT will provide methods that do the job anyway. I can wait for NT7 and I think they are not looking for beta testers at the moment. I am an ancient programer, more at home with languages from the 1970's than C#. I think that fighting C# and trying to handle a load of bugs at the same time might finish me off!
Comment
Latest Posts
Collapse
| Topics | Statistics | Last Post | ||
|---|---|---|---|---|
|
Started by Geovanny Suaza, 02-11-2026, 06:32 PM
|
0 responses
571 views
0 likes
|
Last Post
|
||
|
Started by Geovanny Suaza, 02-11-2026, 05:51 PM
|
0 responses
330 views
1 like
|
Last Post
|
||
|
Started by Mindset, 02-09-2026, 11:44 AM
|
0 responses
101 views
0 likes
|
Last Post
by Mindset
02-09-2026, 11:44 AM
|
||
|
Started by Geovanny Suaza, 02-02-2026, 12:30 PM
|
0 responses
549 views
1 like
|
Last Post
|
||
|
Started by RFrosty, 01-28-2026, 06:49 PM
|
0 responses
549 views
1 like
|
Last Post
by RFrosty
01-28-2026, 06:49 PM
|

Comment