search

fsprojects / ExcelProvider

This library is for the .NET platform implementing a Excel type provider.
http://fsprojects.github.io/ExcelProvider/
The Unlicense
141 stars 51 forks source link

cannot find designtime dll #66

Closed dgrimmin closed 4 months ago

dgrimmin commented 5 years ago

Description

With the change to version 1.0.x the F# interactive is not able to find the designtime dll. It searches in the lib directory while it should be looking in the typeproviders directory,

Repro steps

Reference the runtime dll and open FSharp.Interop.Excel . The fsi will be complaining about the TypeProviderAssembly attribute refering to a designtime dll.

Expected behavior

Automatic resolving of path to designtime dll

Actual behavior

Cannot find designtime dll.

Known workarounds

Copy content of typeproviders directory to lib directory.

Related

Maybe is possible to amend the [<TypeProviderAssembly("ExcelProvider.DesignTime.dll")>] statement in ExcelProvider.Runtime.fs

dgrimmin commented 5 years ago

https://github.com/fsharp/fslang-design/blob/master/tooling/FST-1003-loading-type-provider-design-time-components.md

Supposedly it has to do with this.

dgrimmin commented 5 years ago

Upgrading to F#4.5 solved the issue. Issue is closed.

natsukagami commented 5 years ago

I'm still having this issue. On linux, with F# 4.5

error FS3031 : The type provider '/home/user/.nuget/packages/excelprovider/1.0.1/lib/netstandard2.0/ExcelProvider.Runtime.dll' reported an error : Assembly attribute 'TypeProviderAssemblyAttribute' refers to a designer assembly 'ExcelProvider.DesignTime.dll' which cannot be loaded or doesn't exist. Could not load file or assembly 'FSharp.Core, Version=4.4.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified. [/home/user/project/src/App/App.fsproj]
quintusm commented 3 years ago

With the release of v2.0.0 this issue should be resolved. Please comment if anybody still encounters the issue with version 2.0

quintusm commented 4 months ago

I am closing this issue as it no longer seems to be a problem. @natsukagami if you still experience this issue let me know and I will look at it again