I wonder if Briefly is handling Windows' file system properly.

It does! It creates something like C:\Users\Dorgan\AppData\Local\Temp/briefly--5764607095903232-YiSQwcVeeltDoQnC53r7/briefly-5764606969264128-2dncVrKcfGsPTZ2JmgPO

Maybe a file permission issue? I'm grasping at straws.

This PR reads solid otherwise.

Question, we don't need to namespace everytime during a normal release, correct? meaning you downloaded expert via a package manager, github releases, or are building a specific release from source.

I think in that case, we don't need to namespace every time? Only the first time.

In the case that we are working in development, we can maybe have an env var or just use mix env dev to namespace every time.

I'll still review this tho.

@mhanberg we need to do that for nightly since the engine builds are "namespaced" by the expert version(which right now is always 0.1.0)
Unless we append the nightly commit hash to the version?

Even if we do that it's still beneficial to do incremental namespacing, it cuts down iteration time while developing

Nightly should already have the commit hash appended to it.

It's locally compiled releases that only have '0.1.0'

Ah, I didn't realize we do that to version.txt for nightly, that does simplify things. Changing Expert.vsn/0 to read that file instead of the mix config does the trick for published releases