Andy Ward

Sorry I think 5.1.390 of Geometry from our master myget feed is a bit broken. (We are sorting out some build server issues). Can you try 5.1.387-develop from the develop...

Weird. I'll take a look...

OK. It's fine in Develop -as long as you use the latest Myget develop dependencies. But don't mix and match develop and master (or nuget) dependencies There's been a breaking...

For the very latest I would use: Essentials : 5.1.312-develop Geometry: 5.1.387-develop If you still have the SEHException with that we'll have to investigate

The move to net472 in geometry is also very recent - Our CI build server started failing on the Geometry builds (we surmise because of an update to the VC...

That's an old v4 version of explorer. You can easily build the very latest from https://github.com/xBimTeam/XbimWindowsUI

This seems to be OK in the very latest 5.1 Geometry (in the develop branch). 

Shouldn't be long before Steve pushes to master,and we can make a nuget release. If urgent you can get a build from the develop myget at https://www.myget.org/F/xbim-develop/api/v3/index.json

Doesn't the runtime stack need to be .NET Framework? I'm not familiar with the VS Publish Function dialog, but it's possible you're targeting .netcore3.1 which won't work for xbim Geometry....

For clarification this is not specific to the _ifcrail_ branch. Unfortunately we're not currently supporting handling IFCSURFACESTYLEWITHTEXTURES . I'm not sure many tools actually output textures, as it's logistically hard...