Actually, this was something that sort of weighed on me too. I was a bit disappointed to see WinForms being used more than WPF as I am interested in a WPF + F# combo. What robert suggested is what I had planned on doing -> do all the design work for WPF in either VS or Blend, and use F# for the hard core work. I don't think it may be exaclty easy or straighforward as some have said, but it should be fun and interesting.

By on 9/3/2008 12:18 PM ()

Actually, this was something that sort of weighed on me too. I was a bit disappointed to see WinForms being used more than WPF as I am interested in a WPF + F# combo. What robert suggested is what I had planned on doing -> do all the design work for WPF in either VS or Blend, and use F# for the hard core work. I don't think it may be exaclty easy or straighforward as some have said, but it should be fun and interesting.

Hi sparky00!

I am sure that we will get both winforms and wpf project templates and full support when we reach "Productized 1.0"! [:)]
I have some questions after i read your post (and robert's too):

a. I own Visual Studio Pro, can i use it to make Blend's work or i am forced to use Blend ? Blend is beeing used for making WPF GUI screens or WinForms too ?

b. Let's say that until we get F# fully incorporated in Visual Studio, we want to painlessly create WinForm applications (forms, buttons grids litboxes etc etc).
What is the more productive way to do it, create ALL GUI stuff in F# code (rather painfull...) or create these with, let's say C# (can Blend can help here ??), put it in a .dll, reference it from out F# project and use it like this ?

Or is it a better way to do so ?

By on 9/3/2008 12:45 PM ()

Anyone ? Anyone who knows about future plans and more Visual Studio integration ??

By on 9/2/2008 4:50 AM ()

My guess is, and it is a guess as I don't work for Microsoft and have no insider information, is that the F# team will simply concentrate on polishing what you see in the september CTP for the first productized version of F#, then set there sites on designers etc for the next productized version.

Using F# you'll probably always be a step behind C# in terms of designers and project templates, but two steps ahead of C# in terms of langauge design ;)

My point for view is: Given that its now easy to use the designers in C# to produce your front end and code your back end in F# who really cares about the lack of designer support? Personally I rather see the F# team concentrate on speeding up the intellisense.

Cheers,
Rob

By on 9/2/2008 8:46 AM ()

Hey Robert, thanks for the reply!

I am asking because i work for a C# shop and it will be kind of difficult to persuade my manager to start looking more seriously on F# and writing next project(s) in it.
The designers and project templates do get managers excited, unfortunately...[:(]

Using F# you'll probably always be a step behind C# in terms of designers and project templates, but two steps ahead of C# in terms of langauge design ;)

I tend to agree on that!

My point for view is: Given that its now easy to use the designers in C# to produce your front end and code your back end in F# who really cares about the lack of designer support?

Because then i would have to maintain knowledge and expertise in two things (C# and F#) and i really want to concentrate in one. Unless if i play it this way and just waiting for the F# VS support to further mature and then do the whole switch.

By on 9/2/2008 12:45 PM ()
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