Error: The target "Build" does not exist in the project #349
Comments
|
To found the issue, you can created your own Build-target to the fsproj-file first: <Target Name="Build">
<Message Text="Ext = $(MSBuildExtensionsPath)" />
<Message Text="Tools = $(MSBuildToolsVersion)" />
<Message Text="msb32 = $(MSBuildExtensionsPath32)" />
<Message Text="targ = $(TargetFrameworkIdentifier)" />
<Message Text="fs = $(FSharpTargetsPath)" />
<Message Text="vs = $(VisualStudioVersion)" />
</Target> The issue is probably that there is a condition saying something like <PropertyGroup Condition="'$(VisualStudioVersion)' != '11.0'">
<FSharpTargetsPath>$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\FSharp\Microsoft.FSharp.Targets</FSharpTargetsPath>
</PropertyGroup>but with recent Visual Studio the condition is not met or the path is actually somewhere else, <PropertyGroup Condition="'$(VisualStudioVersion)' != '11.0' And Exists('$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\FSharp\')">
<FSharpTargetsPath>$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\FSharp\Microsoft.FSharp.Targets</FSharpTargetsPath>
</PropertyGroup>
<PropertyGroup Condition="'$(VisualStudioVersion)' != '11.0' And Exists('$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(MSBuildToolsVersion)\FSharp\')">
<FSharpTargetsPath>$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(MSBuildToolsVersion)\FSharp\Microsoft.FSharp.Targets</FSharpTargetsPath>
</PropertyGroup> |
|
Second this - a fresh pull of the project, ran once to enter project details and then ./build.sh (windows, git) gives output below RUnning |
|
As a workaround, there is commented out section of the build target in the generated template. If you uncomment that, and comment out the active portion like so, it seems to work. Suggest fixing the template to use the commented out version? Not sure why it's like that. Happy to send a PR if people agree that's preferable? Looking at it, it seems like the |
|
I don't think this project is maintained any more - I'd recommend using https://github.com/TheAngryByrd/MiniScaffold or https://github.com/ionide/Waypoint instead. Hey, @forki maybe we should somehow formalize that by putting huge info in the readme? |
|
That's too bad - was trying to upgrade an old project based on this and hoping I could drop a fresh checkout onto the old one. That's part of the problem with using scaffolds etc - it's a fast way to get started but you kind of get locked in to the infrastructure. Right now the project and tests themselves build with just vanilla dotnet tooling but all the other housekeeping like release notes, and packaging and docs depend on getting some now spider web encrusted scripts updated. |
|
Or perhaps revamp this project? |
|
fWiw I moved ahead with mini scaffold and it was fairly painless and nicely built into dotnet template system. Would recommend trying that. I’m all for maintaining fewer better pieces of code (this was great but some benefit to focusing on a few things and mini scaffold seems better set for dotnet core)
Von meinem iPhone gesendet
… Am 16.05.2020 um 9:45 AM schrieb Oskar Gewalli ***@***.***>:
Or perhaps revamp this project?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Looks like there hasn't been any accepted pull requests in a while, so let's ask about in the f# projects channel. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On MacOS the initial
build.shfails with this:The text was updated successfully, but these errors were encountered: