provide better naming consistency. The new names are as follows: F# and C# Web App (ASP.NET, MVC 2), F# and C# Web Service (ASP.NET, WSDL), F# and C# Windows App (WPF, MVVM), F# Windows App (WPF, MVVM), F# and C# Web Application (Silverlight).
As Don Syme mentioned in a recent blog post, I've been working to get the five F# templates that have been announced on this blog up on Visual Studio Gallery. I'm happy to say that all are now available.
You can install these templates by doing the following:
1. In Visual Studio 2010, go to File -> New and select Online Templates
2. Search for Daniel Mohl or one of the following template names:
- F# ASP.NET MVC 2 Web Application
- F# Web Service (WSDL)
- F# and C# WPF Application (MVVM)
- F# WPF Application (WPF)
- F# Silverlight Application (MVVM)
Here is an idea of what it will look like if you search the online templates in Visual Studio 2010 for Daniel Mohl:
Additionally, I strongly recommend that you check out the two templates created by Jomo Fisher.
- F# Parsed Language Starter (additional information can be found here)
- F# ASP.NET OData Web Service (additional information can be found here)
I'd love to get your feedback on all of these templates. Also, let me know if there are any additional F# templates that you would like to see.
Thanks! I got them all. These will come in handy.
ReplyDeleteDude, that is awesome! Thanks for contributing to the community ;) Keep it up
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteHaven't downloaded these yet, but have you considered the following?
ReplyDeleteFor F#, "Language.vstemplate" needs the following line at the end of the <TemplateData> section:
<PromptForSaveOnCreation>true</PromptForSaveOnCreation>
This allows the template to work when the user has unchecked "Save new projects when created" via "Tools|Options".
Also, make sure you don't hard code the path to "Program Files", since it won't work if the root drive is not C: and won't work on an x64 install (e.g., PowerPack is installed into "Program Files(x86)") Instead, referencing files relative off of $(MSBuildExtensionsPath32) worked just fine for me.
Thanks for the feedback James.
ReplyDeleteThanks for the feedback James.
ReplyDeleteThanks! I got them all. These will come in handy.
ReplyDelete