speckleworks / speckleui Goto Github PK

The valid use case is: internal deployments à la localhost:xxxx will not have, or need a TLS cert. We need to look at what's needed to enable this from cefsharp.

Hi @didimitrie and @teocomi ,

We are writing a Microstation plugin (will hopefully be open sourced once it reached MVP) and have encountered a problem: Microstation supports dotNet 4.6.1 and will not be adding support for later versions...

Two questions:

1. Do you have any overaching concerns with downgrading the target framework?
2. Do you have any suggestions about how the downgrade could be tested? The solution builds with dotNet 4.6.1, is that enough?

Specifically, add a Browser.IsIntialized check in:

and

Trawled from MSTeams:

[09/01 05:56] Nic Burgers
I was trying to launch the SpeckleUiWindow from within the ETABS plugin code and kept finding that the window appeared but there was no content. There were no calls at all to to the SpeckleUiApp at localhost:8080

Yamin and I spent several hours trying to work out what was going on and although we didn't definitively work out the issue, we followed our noses after reading a CefSharp exception pointing us to cefsharp/CefSharp#1714
Feature Request - Add AnyCPU Support · Issue #1714 · cefsharp/CefSharpDoing some research on another topic I believe I've come up with a method of making AnyCPU a reality without introducing maintainable code to the framework. With 60a1e61 it's now po...github.com​[09/01 05:59] Nic Burgers

I saw that this issue seemed to have been fixed in a newer version (the one you have points to version 57). We found other issues when we tried to link the most recent stable version, but version 71.0.2 works well and only needs a couple of one-liner changes

ping @nic-burgers-arup - let's take the discussion further here :)

Summary: is how do we make it possible to build the UiBase with two cef sharp versions - one latest, that we can use in Rhino, ETABS, etc. - and v.57, which we need to stick to because of Revit.

@teocomi can guide the stupid @didimitrie to make a cool nuget package out of this, for easier and smoother implementation.
We have the required info, need to actually do it