shankargv87
shankargv87
@GeorgeS2019 After building, it created DLLs for each dependency. I'm expecting a single fop.dll with all the dependencies included, so I don't need to refer to all the dependency DLLs...
@GeorgeS2019 I attached my sample project. [IkvmFop.zip](https://github.com/ikvmnet/ikvm/files/14543629/IkvmFop.zip)
@GeorgeS2019 I attached my csproj file [IkvmFop.csproj.zip](https://github.com/ikvmnet/ikvm/files/14543659/IkvmFop.csproj.zip)
I removed the dependency IkvmReference elements and kept only the IkvmReference for fop-2.9.jar and included the dependency jars in Compile element. Now I'm getting the dependencies combined into one assembly....
> @shankargv87 > > > AssemblyName is largely irrelevent to the question asked, though might be relevant later if you want to customize the produced assembly name. > > Have...
> @shankargv87 > > Now you have one FOP.dll, do you still need ikvm.maven? @GeorgeS2019 No, but I'm going to try ikvm.maven to see how it works.
I faced the same issue. It is working now after installed this version. https://github.com/SpecFlowOSS/SpecFlow.VS/releases/tag/v2022.1.93-net8