F# kit

Thanks, glad that you like it!

 

Hi! Thank you for the kit!
Xamarin Studio announced - 6.3 is the final release and recommend that developers now use Visual Studio on both Windows and Mac. Why kit requires xamarin?

 

For the F# compiler mostly.

 

Can we use compiler from Visual Studio?

 

Possibly, haven't tried it yet

 

The problem is that Visual Studio replace and remove Xamarin Studio during installation

 

I'm use Unity latest version and F# kit.
I wrote the following code.

Code (csharp):

1.  
2. namespace FSharp
3. open UnityEngine
4. open UnityEngine.UI
5. …
6.  

But this compiling error appeared.
error FS0039: The namespace 'UI' is not defined. Maybe you want one of the following: AI

How can I use UnityEngine.UI module?

 

Would have to add the UnityEngine.UI import to the F# project files yourself, sorry.
F# kit will never be 100% native support, we are all hoping for Unity to do that some day. F# kit allows you to play around with F# in Unity and learn a lot though.

 

Awesome work! I was wondering if this kit supports Linux.

 

Not yet, sorry

 

How do I use a type that is defined in an another file?
I defined a GameDirector type in GameDirector.fs file.
I want to use the GameDirector type in FooController.fs file.
Compiler said 'The type 'GameDirector' is not defined'.

 

Did you try the 'open' keyword? Like C#'s 'using'.
Could be that we need to add files to the solution too, which would be a bit more tedious.

 

> Did you try the 'open' keyword? Like C#'s 'using'.

Yes, I tried 'open' keyword. But undefined error occurred.

 

I am not a F# expert by any means. I just doubled checked, all the .fs files are definitely added to the .fsproj file.
I vaguely remember someone else having a similar problem a year ago. Could it be file/compilation order dependent?

 

Oh, yes. I can open by following files order.
Must I rename files if I want to change order?

 

I had to modify FSharpBuildOSX.cs.

Code (CSharp):

1.  
2. using System.Linq;
3.  

Code (CSharp):

1.  
2. var scripts = Directory.GetFiles("Assets", "*.fs", SearchOption.AllDirectories).OrderBy(f => f).ToArray();
3.  

On another note, I modified FSharpBuildOSX.cs to use UnityEngine.UI.

Code (CSharp):

1.  
2. #if UNITY_5_4_OR_NEWER
3. public static string unityenginedllPath = EditorApplication.applicationPath + "/Contents/Managed/UnityEngine.dll";
4. public static string unityengineuidllPath = EditorApplication.applicationPath + "/Contents/UnityExtensions/Unity/GUISystem/UnityEngine.UI.dll";
5. #else
6. public static string unityenginedllPath = EditorApplication.applicationPath + "/Contents/Frameworks/Managed/UnityEngine.dll";
7. public static string unityengineuidllPath = EditorApplication.applicationPath + "/Contents/UnityExtensions/Unity/GUISystem/UnityEngine.UI.dll";
8. #endif
9.  

Code (CSharp):

1.  
2. <Reference Include=""UnityEngine"">
3. <HintPath>";
4. content += unityenginedllPath;
5. content += @"</HintPath>
6. <Private>False</Private>
7. </Reference>
8. <Reference Include=""UnityEngine.UI"">
9. <HintPath>";
10. content += unityengineuidllPath;
11. content += @"</HintPath>
12. <Private>False</Private>
13. </Reference>
14.  

Is this way correct?

 

Thanks for sharing. Looks fine so far. Will test it myself and push out an update!

 

Thanks for making this!

Point of interest: it looks like you can use VS for Mac as the command line build tool by changing the mdtool path to

Code (CSharp):

1. "/Applications/Visual Studio.app/Contents/MacOS/vstool"

. If I'm not mistaken, this would make Xamarin Studio unnecessary?