-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Getting started" steps fail with "FS0810: Property 'CultureName' cannot be set" #353
Comments
To be specific, the following lines are invalid on FSharp.TypeProviders.SDK/src/ProvidedTypes.fs Line 2090 in 1584152
FSharp.TypeProviders.SDK/src/ProvidedTypes.fs Line 3162 in 1584152
|
I was able to work around the issue by targeting |
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 |
I’m having the same issue. So you are saying that this issue has been fixed but the template hasn’t been updated yet? |
Correct. |
I removed the 45s from netfx and changed net45 to 461 in project files, (just as in the instruction above) but it now gives me this error: C:\Users\user\source\repos\HelloWorldProvider\paket-files\fsprojects\FSharp.TypeProviders.SDK\src\ProvidedTypes.fs(55,9): error FS0074: The type referenced through 'System.String' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard'. [C:\Users\user\source\repos\HelloWorldProvider\src\HelloWorldProvider.DesignTime\HelloWorldProvider.DesignTime.fsproj] |
This is fixed now in master |
Description
When following the "Getting started" steps in the readme, the
dotnet build
step fails.Repro steps
Expected behavior
The build succeeds.
Actual behavior
The build fails with the following errors:
Known workarounds
Change minimum target to
net461
. Replace all instances ofnet45
withnet461
, except for innetfx.props
, where you can just delete the lines referencingnet45*
frameworks (I suspect the removal of those lines isn't strictly speaking necessary).The text was updated successfully, but these errors were encountered: