All migrations should begin by performing the following steps:<\/p>\n\n\n\n
- \n
- De-reference the TT API DLL and reference the TT .NET SDK DLL.<\/li>\n\n\n\n
- Replace any \u2018using\u2019 directives that reference any TT API namespaces with references to the TT .NET SDK namespace.TT API<\/strong>
using TradingTechnologies.TTAPI; <\/code>TT .NET SDK<\/strong>using tt_net_sdk;<\/code><\/li>\n\n\n\n- Replace any fully qualified TT API namespace reference to use TT .NET SDK Client Side references. For example:TT API<\/strong>
TradingTechnologies.TTAPI.UniversalLoginTTAPI m_api = null; <\/code>TT .NET SDK<\/strong>tt_net_sdk.TTAPI m_api = null;<\/code><\/li>\n\n\n\n- Update the initialization code to reflect that an application key \/ secret are required in TT .NET SDK applications instead of username \/ password. Complete details are provided for both\u00a0Console<\/a>\u00a0and\u00a0UI<\/a>\u00a0applications.Notes:<\/strong>\n
- \n
- \u201cFollow X_TRADER\u201d login mode has been deprecated.<\/li>\n\n\n\n
- You need not enable \/ disable implieds anymore using the\u00a0XTraderModeTTAPIOptions.EnableImplieds<\/strong>\u00a0property since implieds are calculated on a separate TT server and always available.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
<\/a>Deprecated properties and methods<\/h2>\n\n\n\n
You may encounter some properties and methods that will show up in Visual Studio as deprecated. These properties and methods will still work. However, the deprecation message will indicate that a new, more efficient implementation has been provided.<\/p>\n\n\n\n
![\"\"\/](\"https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/09\/editor-1.png\")
<\/figure>\n\n\n\nTT strongly advises that you update your code such that deprecated properties and methods are not used since they will be removed from the API in a future release.<\/p>\n\n\n\n
<\/a>Enumerations<\/h2>\n\n\n\n
While some enumerations were easily migrated from TT API to TT .NET SDK, others had no corollary in the TT platform. Developers are advised to review the enumerated values being used to ensure that there are no compilation issues.<\/p>\n\n\n\n
<\/a>OrderProfile<\/h2>\n\n\n\n
Many exchange-specific fields, as well as MiFID II fields, which were previously configured in 7.x TT API OrderProfile<\/strong> can no longer be set in the TT .NET SDK OrderProfile<\/a> class and are now configured in Setup<\/strong>. Configurable fields can be found in the Task<\/strong> article sections for [each exchange]|(https:\/\/library.tradingtechnologies.com\/user-setup\/index.html#tt-exchanges-eu<\/a>) within the Setup<\/strong> documentation.<\/p>\n\n\n\n
In addition, the 7x TT API free form text fields (FFT2<\/strong>, FFT3<\/strong>, FFT4<\/strong>, FFT5<\/strong>, FFT6<\/strong>) have been replaced with the new TextA<\/strong>, TextB<\/strong>, TextC<\/strong>, and TextTT<\/strong> fields. Character limitations and exchange tag mappings are summarized [here]|(https:\/\/library.tradingtechnologies.com\/trade\/ot-reference.html#fft-table<\/a>). Full documentation can be found in each of the \u201cConfiguring User Access\u201d Task<\/strong> articles linked above.<\/p>\n","protected":false},"excerpt":{"rendered":"
The TT .NET SDK interface was designed to duplicate that of of the X_TRADER platform\u2019s TT API to minimize migr […]<\/p>\n","protected":false},"author":2,"template":"wp-custom-template-single-doc-tt-net-sdk","meta":{"_acf_changed":true,"footnotes":""},"docs-category":[769],"class_list":["post-8022","doc","type-doc","status-publish","hentry","docs-category-getting-started-with-tt-net-sdk"],"acf":[],"_links":{"self":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/8022","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc"}],"about":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/types\/doc"}],"author":[{"embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/users\/2"}],"version-history":[{"count":0,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/8022\/revisions"}],"wp:attachment":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/media?parent=8022"}],"wp:term":[{"taxonomy":"docs-category","embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/docs-category?post=8022"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Replace any fully qualified TT API namespace reference to use TT .NET SDK Client Side references. For example:TT API<\/strong>