It really doesn't matter; its all about how you like to work. For example, I like to create a library of C# GUI elements (Forms,Controls,etc.), and treat that as just another (logical) resource assembly to leverage from my F# executable. But it works equally well to put all the GUI stuff (including main()) in a C# executable and just reference you business logic through F# assemblies. What I would advise against, however, is generating the UI in C# and then converting the code-behinds to F#. Its brittle and just plain unnecessary.

By on 1/17/2010 8:22 AM ()

I expressed myself a bit vague, but somehow the answers you gave me were spot on anyway - just the ones I was looking for, including the one about the 'home' of the message loop [:)].

By on 1/21/2010 3:44 AM ()

I don't think it really matters, it just depends what you want to be EXE, and what are DLLs.

I like to write GUI and DB code in C# (because of designer support) and then make the F# code the "engine" code or logic of the application. I usually put the main in C#, but I don't think it makes a difference where the message loop starts from.

By on 1/17/2010 8:08 AM ()

I tried using the same with vs 2010 beta 2 and realised that the add reference from c sharp console application to the dll created in f# never worked. Surprisingly

By on 1/17/2010 8:24 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper