>Because of the implicit project file, other files in the target directory or its subdirectories are included in the compilation.
Errm, so how is this different from a folder with a project file?
>Because of the implicit project file, other files in the target directory or its subdirectories are included in the compilation.
Errm, so how is this different from a folder with a project file?
> Errm, so how is this different from a folder with a project file?
It requires neither a folder nor a project file. Just pass the source file as the argument and you have everything up and running.
If you don't put it in a folder, then entire folder tree is compiled into your script.
That doesn't seem true based on the introduction. Where are you seeing that info?
In the end the post links to spec.
>By default, file-based apps use the Microsoft.NET.Sdk SDK.
This behavior is default provided by sdk to keep project files small.
Probably, you can have multiple scripts in one folder. Eg script1.cs, script2.cs...
That's it, and they are all compiled into one executable as implicit items, and everything in subfolders.