Hey @Carter702 , this sounds similar to baileys question above. It’s not supported, as i expected devs to use a storage account per instance, since they are costed per use and not by instance. I did have a look at adding the feature but it’s non trivial to support it with backwards compat. I’ll look into it tho as it seems there’s some interest in it.
For now you’d have to implement the changes yourself based on our source.
IUploadedFile, as I asked before, please post an issue with detailed information (the answer can then be found by others). I have created an issue for you and answered here: cofoundry-cms/cofoundry#471
@HeyJoel I'm wondering if the answer is I was using version 0.9.0 with SkiaSharp v0.3.0. I installed versions 0.10.0 and 0.4.0 into a new VS solution and now see what you describe. Thank you.
I've looked at the GitHub Docs and Issues page and here in Gitter but have not found anything to explain the proper way to copy an existing site to a new site, in other words to replicate an existing site into a new Visual Studio Solution. Is it a matter of scripting the original db into a new db and setting the new VS project's appsettings connectionstring to the new db?