-
-
Notifications
You must be signed in to change notification settings - Fork 54
forge new project
#18
Comments
Due to the globbing pattern, FAKE tries to build the templates, which get cloned to a sibling directory of the directory, where So you either have to put Forge to another directory, use the Homebrew formula like described in the README, or we change the target directory, where the templates get cloned to. |
I can't use the homebrew formula because I'm writing a linux tutorial. So what's the invocation I should perform to have it just work? |
For now, I probably would just download and unzip Forge.zip to |
Yes, idea is to have "global" / added to I don't have too much experience with packaging systems for linux so I have no idea what would be good way of providing same deployment for Forge on linux as we currently have for Windows and Mac. Maybe we should suggest in documentation using something like http://linuxbrew.sh/ and using same |
Another thing is way we fail in such case - we clearly should have some better error handling for this case, instead of some random XML exception. |
That exception comes from xbuild, I don't know how Forge could react to that, because there is also FAKE involved. I think the only thing to prevent this, would be not to build the template project files. |
Oh, my bad. I think error comes up when user tries to build project (run default I don't think we can do anything about it. Installing Forge "globally" and running it in solution / repository root of new project should work. |
when creating a new Suave project with
forge.sh
. (which also needs+x
set)Expected Behavior
No warnings on the console.
Current Behavior
Warnings seem to indicate faulty fsproj files.
Steps to Reproduce (for bugs)
Your Environment
The text was updated successfully, but these errors were encountered: