Open the file in a text editor (VSCode)

Add a resources element with a image element as a child. The name attribute must refer to a file already in your resources.

Update the image view setting the "image" attribute on the imageview to the same name.

Still doesn't preview but it works when run.

Experimentally, in my case, I found that the property image does not work if I add a project like net.standard to the solution.

If uncheck the project reference in references, and save solution, open storyboard designer then image property will work.

When you will end work with image on storyboard and save it you can return reference to net.standard project.

Still an issue in 15.9.2

Problem still present in 15.9.3. Solution for me was to include the image by hand in the storyboard file.

Just want to build on the comment made by @Christian Moen; the simplest work-around path I've tried (and works cleanly) is:

1. Build and run your app [this is just to confirm everything is working and to make sure your .Net Standard project is built
2. Right-click on your .Net Standard project and select "Unload Project"
3. Double-click on your Storyboard file to open the designer
4. You'll find that the Asset (image) selectors are working correctly; make your changes to the storyboard
5. Because of step 1, you can still do "F5" test build/run cycles to make sure your storyboard is behaving
6. When you're done with your storyboard edits, close it
7. Right-click on the .Net Standard project and select "Reload Project"

I've broken it out in extreme detail but it comes down to 1) Unload the .Net Standard Project, 2) Load and Edit your Storyboard, 3) Reload the .Net Standard project when done with the Storyboard. Not ideal, but an easy enough work-around to manage.

Hi,

The easiest solution for me was to remove the reference of the .net standard library in the iOS project.
I close and reopen the storyboard. I can select the image and everything is fine.

Don't forger to re-register the reference to the .net standard library.

Hope this will help

Benoist

@David Ortinau [MSFT] Is anyone from Microsoft still looking into this? We haven't had any feedback about this for over a month and half

Same problem here!!!!!!!!!!!!!!!!!!! VS2017 15.8.8 Please fix this in 15.8.9

We have fixed this issue and it's available in Visual Studio 2017 15.9.4. See the release notes here: https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes#15.9.4

I'd also like to personally thank you all for your patience on this issue, and especially those who took the time to share workarounds. Thank you!

This is a problem for me, using 15.9.2

seems to work just fine if I do it on a Mac, but that's not going to fly as my team is all using Windows, hope to see Microsoft come up with a solution.