Since the old .Net 3.5 Scripting Runtime was deprecated in Unity 2018.3, it will be necessary to upgrade the Scripting Runtime of your project to use .Net 4.x when upgrading to Unity 2019.1 and to the version 2.0.0 of the TextMesh Pro package.
To switch the project to .Net 4.x, go to the menu “Edit - Project Settings” and switch the Scripting Runtime version to .Net 4.x as seen below.
Exactly what I needed. Thanks!
Any new features compare to the 1.4.1?
1.4.1 and 2.0.1 are the same with the exception of 2.0.1 having a dependency on UGUI and using .Net 4.x (mostly the syntactic sugar part of it for the time being).
UGUI was supposed to be a package for 2019.1 but didn’t make it in time. A wrapper was added to allow TMP to treat the still internal UGUI as a package so that when UGUI become a package, version 2.x of TMP will simply work.
This fixed it. THANKS 
Weird question, but we’re working on porting a game using the 2017 LTS that is written in .NET 4.6. Is it possible to get the .NET 4.x version of TextMesh Pro on this version of Unity? The Asset Store version is 1.2.2 and 2017 doesn’t have the package manager window (that we can find). We’ve run into a bug that we are 99% sure is related to the mismatch of our scripting backend and the targeted platform for managed plugins that we’re using. Thanks!
The Unity 2018.3 or newer versions of the TMP package require the new FontEngine which was introduced / included with Unity 2018.3. As such, it is not possible to use these newer versions of the package with previous versions of Unity.
That makes sense! Thanks for the quick response, we appreciate it
Thank you ! after upgrading unity, I was getting the error:
“Feature `out variable declaration’ cannot be used because it is not part of the C# 4.0 language specification”
and this fixed it !
Thank that is i want,very thanks…
When the 2.0.2 is coming out? We are having tons of issues with the current 2.0.1 version.
Next release will be 2.1.0 which I am hoping to have available next week,
Any news about the release?
Currently going through the release process. Ran into a minor issue with package release automation which should be resolved tomorrow. So unless I run into some unforeseen issue, new release should be available within a few days.
Great! Hope that the new version resolves all our issues.
Could you give an indication of the status of the new TMP package? I’m really looking forward to all the fixes in this release!
Late(r) today.
For anyone using GameSparks, note that TMPro will throw errors when you build in 2018! Amazon has no plans to support 4.x. Seems to work in 2018.
Sadly, 2018 is the end of the line for GameSparks users. I’ll poke them to open source the code if no fix is planned 
BTW: I reverted the .Net 4.x changes to the TMP package in 2.1.0. This is temporary in the sense the Unity itself will eventually deprecate .Net 3.5 but until then, TMP is back to no longer requiring .Net 4.x
Woot! No worries, the longer this can be temporarily “delayed”, the better. Reports say it’s really only TMP that has the errors (for now). Understandable when you can’t do this anymore. For now, it allows us to get another year of updates because of this.
