Hi and welcome to Spine!
Very sorry to hear you are experiencing troubles and having a rough start! Unfortunately we could not reproduce this problem, the namespace was resolved properly in our test when adding the latest spine-unity unitypackage to a new empty Unity project.
Are you using the most recent 4.0 versions of Spine and of the spine-unity runtimes from the spine-unity download page?
Which version of Unity are you using?
Which version of Visual Studio?
Did you create a new empty Unity project or add the unitypackage to an existing one? Did you unpack the spine-unity package normally via Unity's unitypackage loading mechanisms? Unity should generate and adjust the Visual Studio project and solution files automatically after importing the spine-unity unitypackage.
dkoelsch schriebI do not like wasting my money and currently, Spine is just that.
Sorry to hear that your first experience was bad, even more so after you've decided to purchase Spine ESS already. We are providing the evaluation version of Spine free of charge and all runtimes and examples open-source to allow for evaluation before purchase.
In case you are unhappy with Spine, please just write an email to contact@esotericsoftware.com to receive a refund.
I just found a potential reason for this type of problem: when using an older Visual Studio Editor package in the Unity Package Manager, an issue as described by your posting can be reproduced. Could you please have a try upgrading the Visual Studio Editor package via the Unity Package Manager and then hit Assets - Open C# Project?
