Also, note that the existing CodeDom provider for F# doesn't support parsing of F# source code - it can be used only for generating code from CodeDom tree. This is useful for things like WSDL, XSD, ASP.NET and LINQ to SQL (although it doesn't quite work in all these scenarios). However you cannot use existing CodeDom provider to parse F# source code (and highlight the F# souce code using this information)

By on 4/3/2010 6:26 PM ()

Ok. Can I use FSharp.LanguageService.* and FSharp.ProjectSystem.*?

It seems that they will be released 12 April together with VS 2010, but I need to know before 9 April, as it is the last day applications would be accepted.

By on 4/5/2010 5:44 AM ()

What do you want to use these DLLs for?

I don't think there are any reusable components for e.g. syntax highlighting that you can lift out of the existing codebase. But that's ok, syntax highlighting is not a huge task, I imagine you can write it from scratch in a weekend.

For F# itself, you might publish a script that downloads the F# ZIP, unzips it, and builds a local package for the local user. That would avoid potential redistribution issues of the licensing (IANAL).

By on 4/5/2010 7:31 AM ()

Thank you, Brian. It seems my development can be started from existing parser code.

By on 4/5/2010 8:50 AM ()

To be clear, if you just want syntax highlighting, you don't need a parser. Just a lexer is nearly sufficient; so long as you know how to tokenize the source code, and parse enough to deal with #if, (* *) comments, and string literals, you can get enough information to colorize, I believe.

By on 4/5/2010 9:49 AM ()

Hi Lost,

This may give you some idea:

[link:stackoverflow.com]

According to one of the posts it's licensed under the Microsoft Research Shared Source License; I'm not sure if that would be enough for the purpose you're proposing.

By on 4/1/2010 5:12 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