Generate an error message if LanguageTargets property is not set and cannot be inferred

[dsplaisted]

Sdk.targets will import the CSharp or VisualBasic targets files depending on whether the project file extension is .csproj or .vbproj. The LanguageTargets property can also be set to specify the targets file to import.

If LanguageTargets isn't set and the project file extension is neither .csproj nor .vbproj, then the build should fail with a helpful error. This could happen if someone didn't specify the F# SDK for an .fsproj, for example.

[enricosada]

Hi @dsplaisted i think is good to have an error there.
But how can add a remote sdk (not bundled in cli?) with Sdk attribute? i want to populate LanguageTargets BEFORE Microsoft.NET.Sdk, so f# will work using Sdk attribute style.
Atm adding anything FSharp.NET.Sdk/1.0.0-beta-1;Microsoft.NET.Sdk fail with errror because try to search FSharp.NET.Sdk in the cli subdirectory \Sdks\FSharp2.NET.Sdk\Sdk\Sdk.props. Shouldnt that work also for remote packages? or just for bundled? /cc @piotrpMSFT

[enricosada]

NVM, i see for current msbuild RC, the sdk packages are just simulated (so expected to work from sdk directory), right @dsplaisted ? If like that i'll wait for next RC2 when sdk packages can be downloaded from nuget

[rainersigwald]

@enricosada That's correct, there's no acquisition story for Sdks yet. dotnet/msbuild#1436 tracks that.