Back to Questions
3.6k
views2
comments
F# editor under VS
f#pluginscheme

First off, as has been noted previously by others, this overly-fancy forum doesn't work with late-model SeaMonkey browsers (or Firefox for that matter) - it just freezes as soon as I shifyt the focus to the message composition text box... what happened to just being able to enter *text* with perhaps the odd smiley or two? In any case, I dusted off my rarely-used IE and logged back into the forum. ;)

On to the business at hand - on my VS 2005 with F# 1.9.1.18, there are syntax colored elements (namespaces, modules, properties, etc) that seem to have no corresponding entries under the Tools>Options>Environment>Fonts and Colors settings. As these "rogue" elements use the color scheme *I* prefer to use for numeric, string and character literals, it would be nice if I could somehow alter these unasked-for assignments... *is* there a way (including if necessary config files or registry entries)?

I *hope* the answer is not "we're rewriting the F# plugin for VS later this year", as that started getting used about a year ago already(*)... I note that the plugin does not seem to be in the portion of the F# sources that are visible?

Finally, as a long-time C++/MFC/ATL/STL programmer, and a more casual OCaml user for the past 2-3 years, I really am ready to jump in and take F# seriously for a project or two, but niceties like *native* F# support for resource editing and integration of resources and WF would help make this a more credible option.

(*) - I am not suggesting that these statements are being made insincerely, merely that the realities of project scheduling, priorities, and available manpower can [and often do] triumph over the best of intentions. :)

.

This forum is based on community server ([link:communityserver.org]) and thier appear to be many known issues between FireFox and CS. There appears to be a work around for the particular issue you are referring to, maybe this would fix the SeaMonkey problems too:
[link:communityserver.org]
[link:communityserver.org]

However I'm not too sure who is administring this server, as it was founded by optionsScaler, who appears to be busy with other things at the moment.

I can't say when the F# team will rebuild the VS intergration - I know they want to, but as you say manpower is somewhat limited for the moment. If you posting a polite message to offical Micosoft forums, such as MSDN or Channel9, asking for better support for F# in visual studio you'd be doing your bit in helping the F# team get the resources they require to complete a better version of the VS intergration.

Not exactly sure what you mean by "*native* support for resource editing", clearly this doesn't exist in the visual studio intergration but the ablitity to add resources to an F# assembly has existed in the compiler for ages. Win32 resources are supported via the switch --win32res and .NET resources are supported via the switch --resource.

By on 7/16/2007 3:21 AM ()

Thanks for the considered reply - I know my post[ing] comes off a bit negative... having a site as important as this only work properly with MS browsers seems a bit unfortunate.

Since I had already digested a number of other threads here, my "*native*" support mention was a perhaps not-well-expressed attempt to forestall the C# "surrogate" or "build your UI in C# and hack it back into F#" responses... ;)

Part of my frustration is that these days, when one is impatient with progress or support issues, it is often possible to be able to jump in and actually *do* something - but not with the F# IDE.

By on 7/16/2007 10:40 AM ()

    Topic tags

    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