Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.fake directory #871

Closed
mynkow opened this issue Jul 20, 2015 · 9 comments
Closed

.fake directory #871

mynkow opened this issue Jul 20, 2015 · 9 comments

Comments

@mynkow
Copy link

mynkow commented Jul 20, 2015

Today I got this directory to the root of my project.

  1. What is the purpose?
  2. Please remove it!

http://gyazo.com/0587baf1c80534875f15a551496d13eb

@forki
Copy link
Member

forki commented Jul 20, 2015

so you are using the 4.0 alpha!? ;-)

the purpose is to cache the compiled build script and therefor speed up FAKE startup time.
You can just add it to your .gitignore file and everything should be fine.

@mynkow
Copy link
Author

mynkow commented Jul 20, 2015

I think I am not using the alpha. Probably there is a problem with the nuget package and how it is built.

echo Downloading latest version of Fake.exe...
%NUGET% "install" "FAKE" "-OutputDirectory" "%TOOLS_PATH%" "-ExcludeVersion" "-Prerelease"

@forki
Copy link
Member

forki commented Jul 20, 2015

-Prerelease instructs NuGet to download the latest version including alpha and beta versions.

@mynkow
Copy link
Author

mynkow commented Jul 20, 2015

Omg, it really installs the alpha

http://gyazo.com/baae4dfc7f5bbfda9a329258298b7aec

Probably -ExcludeVersion is not working for some reason?

@forki
Copy link
Member

forki commented Jul 20, 2015

no, it's the -prerelease. just remove that and you get latest 3.x

@mynkow
Copy link
Author

mynkow commented Jul 20, 2015

You are right. 10x.

Can you please explain how the cache works in 4.0 and what is included?

@forki
Copy link
Member

forki commented Jul 20, 2015

see #859

@forki forki closed this as completed Jul 20, 2015
@xavierzwirtz
Copy link
Contributor

It takes the dynamic assembly generated by FSI and saves it into the .fake directory. Also saves a list of all loaded dlls and their path so that they can be loaded on next run.

@xavierzwirtz
Copy link
Contributor

@mynkow see here for a detailed explanation of the caching mechanism.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants