StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I don't think the those tools are included by default with the F# compiler that is installed with Visual Studio and so the tasks don't exist. I did the following with a Visual Studio 2012 project, but I expect it would be similar in VS 2013. Here were the steps I had to follow:</p> <ol> <li>Install FSharp.Powerpack from nuget. This has the fslex and fsyacc tools as well as build tasks and targets. </li> <li>Unload the project and edit the .fsproj file.</li> <li><p>Add an import statement for the FSharp.Powerpack.target file. This will add the <code>CallFsLex</code> and <code>CallFsYacc</code> build targets. I added this after the import for <code>Microsoft.FSharp.targets</code>:<br> <code><Import Project="$(ProjectDir)\..\packages\FSPowerPack.Community.3.0.0.0\Tools\FSharp.PowerPack.targets" /></code></p></li> <li><p>Add these three properties to main PropertyGroup at the top of the file: <code><FsYaccToolPath>..\packages\FSPowerPack.Community.3.0.0.0\Tools</FsYaccToolPath> <FsLexToolPath>..\packages\FSPowerPack.Community.3.0.0.0\Tools</FsLexToolPath> <FsLexUnicode>true</FsLexUnicode></code> This tells the build tasks where to find the necessary tools and sets the unicode option for fslex. </p></li> <li>To use the targets we've imported, you need to define the FsLex and FsYacc item groups with the input files to use. You also need to add Compile items for the output .fs files. You end up with something like this in an ItemGroup section:<br> <code><Compile Include="Sql.fs" /><br> <FsYacc Include="SqlParser.fsp"><br> <Module>SqlParser</Module><br> </FsYacc><br> <Compile Include="SqlParser.fsi" /><br> <Compile Include="SqlParser.fs" /><br> <FsLex Include="SqlLexer.fsl" /><br> <Compile Include="SqlLexer.fs" /></code></li> </ol> <p>You might be able to use the FsLex and FsYacc build tasks directly by referencing the FSharp.Powerpack.Build.Tasks.dll, but for me this was easier to get going.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload