Through the Interface

F# takes an important step closer to official release

, , ,

This just may be the catalyst I needed to get around to installing Visual Studio 2008: the availability of the F# September 2008 Community Technology Preview. This takes F# an important step closer to being a full .NET citizen, with the first release delivered by Microsoft's Developer Division (the previous releases having been delivered by Microsoft Research).

It's not required to use VS 2008 with this release of F#, but that's the version that's been targeted for the IDE integration, naturally enough. I've been holding off from installing VS 2008 for some time - mainly as ObjectARX applications still require VS 2005 - but if I had a crystal ball I'm sure it would show VS 2008 somewhere in my near future... 🙂

It is, of course, possible to install VS 2008 side-by-side with VS 2005, but also to use it to develop applications based on the .NET API exposed by the various shipping (& supported) versions of AutoCAD.

Now I just have to make some space on my hard-drive... <sigh>

  1. namin Avatar
    namin

    Hi Kean,

    I am also thinking of taking the jump to Visual Studio 2008, because of the new F# CTP release. Last time I tried using VS 2008 to compile some AutoCAD .NET plug-in, I would get an annoying warning when I loaded into AutoCAD. In any case, I'll experience soon if that's still the case now.

    Reply
  2. namin Avatar
    namin

    Hi Kean,

    To be more precise, the error message popping up is for C++ AutoCAD projects compiled in VS 2008. It says: "AutoCAD is attempting to load ... which is not compatible with AutoCAD. Do you still want to load the application?"

    Do you know how I can get rid of this warning?

    Thanks.

    Reply
  3. namin Avatar
    namin

    I found a solution. It's a build tool version problem, which can be fixed by using the utility the VC Build Hook utility freely available at manusoft.com/Res...

    Reply
  4. namin Avatar
    namin

    Hmm, actually, it doesn't quite work 🙁 I still get the same error...

    Reply
  5. Kean Walmsley Avatar
    Kean Walmsley

    This is how it should be: unmanaged ObjectARX modules need to be compiled with the same compiler as AutoCAD, which means VS .NET 2002 for AutoCAD 2004-2006 and VS 2005 for AutoCAD 2007-2009.

    So you will need to downgrade to build applications for these releases.

    If you want to use VS 2008 to build applications for these versions, you can always use the managed API.

    Kean

    Reply
  6. Mike Tuersley Avatar
    Mike Tuersley

    Just to add to your comment, Kean. VS2008 works fine for writing managed, COM and mixed managed/COM addins for '06 thru '09. For '06 to '08, you need to go into the compile options and set the targeted framework to use.

    Mike

    Ps - see you @ AU!

    Reply
  7. Kean Walmsley Avatar
    Kean Walmsley

    Thanks, Mike!

    Sounds good - see you at AU. 🙂

    Kean

    Reply
  8. mspan Avatar
    mspan

    For those of us, like me, that are too frugal to buy VS2008, you can use the Visual Studio Shell with f#. It becomes the equivalent of a free version of Visual Studio for learning/developing F# apps. See:
    msdn.microsoft.com/e...
    -Mike

    Reply

Leave a Reply to namin Cancel reply

Your email address will not be published. Required fields are marked *