fsprojects-archive / zzarchive-FSharp.Data.DbPedia

[ARCHIVED] An F# type provider for DBpedia
The Unlicense
13 stars 9 forks source link

Support targeting PCLs #9

Open mooreniemi opened 8 years ago

mooreniemi commented 8 years ago

https://github.com/fsprojects/FSharp.Data.DbPedia/blob/master/nuget/FSharp.Data.DbPedia.nuspec

  <files>
    <file src="..\bin\RestSharp.dll" target="lib/net40" />
    <file src="..\bin\FSharp.Data.DbPedia.dll" target="lib/net40" />
    <file src="..\bin\FSharp.Data.DbPedia.xml" target="lib/net40" />
    <file src="..\bin\FSharp.Data.DbPedia.pdb" target="lib/net40" />
    <file src="..\bin\FSharp.Core.dll" target="lib/net40" />
  </files>

means this project can't work in net45 right? i'd like to use it in such a project.

for posterity, this is the error i see on attempting install

Severity    Code    Description Project File    Line
Error       Could not install package 'FSharp.Data.DbPedia 0.0.2'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile7', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.            0
dsyme commented 8 years ago

I think the problem is that you're trying to add the nuget package to a Portable library - you need to make a .NET 4.x library instead.

dsyme commented 8 years ago

See this bit

...a project that targets '.NETPortable,Version=v4.5,Profile=Profile7', 
mooreniemi commented 8 years ago

I don't quite understand the difference. When it comes to developing Xamarin.Forms it asks to use a PCL. Why can't that be supported by this lib?

dsyme commented 8 years ago

Hmmm... I see. Could you send a link to how that guidance is worded?

PCLs will be needed if you are building an XF component to be used across multiple platforms. That's a fine thing to want to do. However currently this type provider doesn't support creating PCLs - in theory it can be enabled but it is work. I'll adjust the title.

On any specific Xamarin platform you should be able to still use the type provider I think.