-
Notifications
You must be signed in to change notification settings - Fork 31
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
Referencing netstandard2.0 library projects. #29
Comments
Hi @IceReaper - do you think you can share with me the code so I can debug locally? |
Got any contact information for me, to provide you a code share? |
you can reach me at rafael (at) curiosity . ai
…On Mon, Oct 26, 2020, 2:54 PM Andre Mohren ***@***.***> wrote:
Got any contact information for me, to provide you a code share?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACDCOA6UCB5VKKAHU5I23K3SMV5QNANCNFSM4SZPJXQA>
.
|
I managed to reproduce it on a small scale test project: Both Windows 10 and Ubuntu 20.10 produce the same error. |
Thanks! I'm going to be off next week but will take a look as soon as I'm back! |
Ongoing from #25: Above error is gone, but now the following error occurs:
|
Strange - this last error was supposed to be gone with the update to the h5 SDK target that you've already applied. By the way, I didn't know referencing libraries that are compiled against the normal C# SDK was supported by Bridge before - I'll take a look on the zip file you shared here |
So tested here, the issue seems to be referencing a standard csproj: <Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>netstandard2.0</TargetFramework>
</PropertyGroup>
</Project> If you change the Library.csproj to be a h5 project: <Project Sdk="h5.Target/0.0.13615">
<PropertyGroup>
<TargetFramework>netstandard2.0</TargetFramework>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="h5" Version="0.0.13619" />
</ItemGroup>
</Project> Then it compiles fine. Is this possible on your case? If this is code that is shared on your code-base outside of h5, I would recommend having 2 csproj files, one using the standard SDK and one with the h5 SDK. |
What i have written against bridge originally is the following setup:
If i change the Ui.Core project to use the h5 target, i cant build it with Ui.Desktop anymore. Using bridge this setup worked perfectly. Ill test the 2 csproj files approach for now, if that works out i can go with that solution for now. But on the long term i would love to see the feature back (as this will cause a mess if we add more and more libraries) :) EDIT: The additional csproj approach works as a workaround for now. |
I am working on an opengl/webgl based ui rendering library. The project is setup as follows:
Using Bridge.net it was possible to reference one of the implementation projects, and compile the whole application into either an desktop or webgl powered application. Using H5 however, compiling the Html5 projects results in:
The text was updated successfully, but these errors were encountered: