"Getting started" steps fail with "FS0810: Property 'CultureName' cannot be set"
See original GitHub issueDescription
When following the “Getting started” steps in the readme, the dotnet build
step fails.
Repro steps
dotnet new -i FSharp.TypeProviders.Templates
dotnet new typeprovider -n LemonadeProvider -lang F#
cd LemonadeProvider
dotnet tool restore
dotnet paket update
dotnet build -c release
Expected behavior
The build succeeds.
Actual behavior
The build fails with the following errors:
D:\Source\Repos\LemonadeProvider\paket-files\fsprojects\FSharp.TypeProviders.SDK\src\ProvidedTypes.fs(2090,13): error FS0810: Property 'CultureName' cannot be set [D:\Source\Repos\LemonadeProvider\src\LemonadeProvider.DesignTime\LemonadeProvider.DesignTime.fsproj]
D:\Source\Repos\LemonadeProvider\paket-files\fsprojects\FSharp.TypeProviders.SDK\src\ProvidedTypes.fs(3162,13): error FS0810: Property 'CultureName' cannot be set [D:\Source\Repos\LemonadeProvider\src\LemonadeProvider.DesignTime\LemonadeProvider.DesignTime.fsproj]
Known workarounds
Change minimum target to net461
. Replace all instances of net45
with net461
, except for in netfx.props
, where you can just delete the lines referencing net45*
frameworks (I suspect the removal of those lines isn’t strictly speaking necessary).
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Not being able to build F# type provider SDK
As soon as I build the solution I get the error: "FS0810, Property 'CultureName' cannot be set, \LemonadeProvider\paket-files\fsprojects\FSharp.
Read more >.NET 5 update? · Issue #356 · fsprojects/FSharp. ...
Repro steps I followed the steps of the Getting Started: ❯ dotnet new -i FSharp. ... error FS0810: Property 'CultureName' cannot be set...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I see that #339 was merged some weeks ago, so I tried with the contents of this folder on master and it works fine. I suggest the
dotnet new
template is updated. I’ll leave this for you to close.I was able to work around the issue by targeting
net461
instead ofnet45
. I simply replaced all instances ofnet45
withnet461
, except for innetfx.props
, where I just deleted the lines referencingnet45*
frameworks.