tk2dExternal does not exist

[unikronsoftware]

Vico92's problem was in Monodevelop only, because of a Unity issue that doesn't generate the solution files correctly. If that is the case, you'll need to file a bug with the Unity guys. In the mean time you can manually add the dll to the solution but thats not a great solution.

[yo_milo]

The thing is, the DLL is there.

But for some reason Mono does gives me the "Does not exist in the current context" error in tk2dEditorSkin line 14, 20, 24, and 46.

So, do you recommend me deleting and adding the DLL?

Sorry if this problem is not really 2D toolkit. I love your tools, but this bug has totally disrupted my rhythm today... I have not been able to work...

[unikronsoftware]

Is the DLL in the external assemblies in the relevant monodevelop project? Thats what it wasn't doing correctly last time I looked.

[yo_milo]

I reinstalled Monodevelop. It fixed my problem.

[Vico92]

.cs FILES are into the project but DLL REFERENCES are missing.

To add the missing references :
1-right-clic the References folder in Assembly-CSharp-Editor to edit references.
2-Select .NET Assembly tab, then go to the TK2DROOT.tk2d/Editor folder
3-Select both tk2dExternal.dll and tk2dSkin.dll and clic "Add" then "OK"

You will have to repeat the process when solution is regenerated.

[thiagodeserto]

Same problem here, but with unity cloud only.

Locally builds perfectly, but in the cloud cannot build iOS, Android or Web.
Both unity versions are the same: 5.0.1f1.

This is happening with a brand new project and last 2d toolkit version.
2.5.1

Code: [Select]

1: [Unity] Initialize engine version: 5.0.1f1 (5a2e8fe35a68)
2: [Unity] -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Assembly-CSharp-Editor.dll
3: [Unity] Compilation failed: 4 error(s), 0 warnings
4: [Unity] Assets/TK2DROOT/tk2d/Editor/tk2dEditorSkin.cs(14,25): error CS0103: The name `tk2dExternal' does not exist in the current context
5: [Unity] Assets/TK2DROOT/tk2d/Editor/tk2dEditorSkin.cs(20,24): error CS0103: The name `tk2dExternal' does not exist in the current context
6: [Unity] Assets/TK2DROOT/tk2d/Editor/tk2dEditorSkin.cs(24,24): error CS0103: The name `tk2dExternal' does not exist in the current context
7: [Unity] Assets/TK2DROOT/tk2d/Editor/tk2dEditorSkin.cs(46,17): error CS0103: The name `tk2dExternal' does not exist in the current context
8: [Unity] Assets/TK2DROOT/tk2d/Editor/tk2dEditorSkin.cs(14,25): error CS0103: The name `tk2dExternal' does not exist in the current context
9: [Unity] Assets/TK2DROOT/tk2d/Editor/tk2dEditorSkin.cs(20,24): error CS0103: The name `tk2dExternal' does not exist in the current context
10: [Unity] Assets/TK2DROOT/tk2d/Editor/tk2dEditorSkin.cs(24,24): error CS0103: The name `tk2dExternal' does not exist in the current context
11: [Unity] Assets/TK2DROOT/tk2d/Editor/tk2dEditorSkin.cs(46,17): error CS0103: The name `tk2dExternal' does not exist in the current context
12: [Unity] -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Assembly-CSharp-Editor.dll


[unikronsoftware]

Is tk2dEditor.dll in version control?

I have no idea why its trying to build an Editor folder, or even the Editor assembly for an iOS build. You will need to ask the Unity guys about this. The reason its happening is -
1. Its building an editor assembly when trying to build an iOS / Android / Web deployment for some reason.
2. Its not finding the dll file that is in the editor folder, but it does when building locally. It should at least be consistent with the editor.

[VeTaLkO]

Hi, i have the same issue.

// Is tk2dEditor.dll in version control?
Should it be? I cant find it in solution itself.
Also, if to open asset store page and check package content from there (just in case i had removed it accidentally), there are only 2 dlls: tk2dExternal and tk2dSkin

[unikronsoftware]

Sorry, I meant tk2dExternal.dll
Its complaining about a missing tk2dExternal dll - that is an editor DLL, no idea why its trying to build it for a cloud build, as is Assembly-CSharp-Editor. This sounds like a bug in the cloud build