4 ms·
Can anyone clarify - does this support any .NET language (C#, F#, mixed language)? In the 'fabulous' example, I can't see where the source code for "Hello World
by pedrow 11y ago
Can anyone clarify - does this support any .NET language (C#, F#, mixed language)? In the 'fabulous' example, I can't see where the source code for "Hello World" actually is.
- bjg 11y agoLooks like they have compiler support for only C# (csc), and F# (fsc) right now. https://github.com/dotnet/cli/tree/master/src/Microsoft.DotNet.Tools.Compiler.Csc https://github.com/dotnet/cli/tree/master/src/Microsoft.DotN... https://github.com/dotnet/cli/tree/master/src/Microsoft.DotNet.Tools.Compiler.Fsc https://github.com/dotnet/cli/tree/master/src/Microsoft.DotN...
- enricosada 11y agodotnet cli is a new project. It use some good ideas from aspnet/dnx like project.json, but it's more easy to work with, less magic, more language agnostic. c# is used to bootstrap all tools, so it's the first supported language and the default. Nightly, dev build have f# support, but it's a beta ( merged last week, but it's ok ). f# dotnet cli (the wrapper for f# compiler) is a beta, but moving fast, not much todo. For example the f# support in dotnet new is in a pull request. The F# compiler built for coreclr ( bundled with dotnet cli, so ready to go ) is working pretty much, some stuff missing ( portable pdb for example ), f# coreclr is open source https://github.com/Microsoft/visualfsharp https://github.com/Microsoft/visualfsharp
- enricosada 11y agomixed in same project ( project.json ), no you cannot do that (i mean c# source and f# source in same project ). You can have multiple project (same repo, different directories ) and reference one from another you can have each project.json use a different compiler setting the compilerName property ( csc for c#, or fsc for f# ) . A project can reference another project, so you can reference a F# project in a c# project, or the other way around. like now in .net with msbuild or other tools
- tracker1 11y agoHopefully the interaction works a little better now than the last multi-language project I worked on... wanted to do XML processing in VB because of the native syntax support, but interacting with the rest of the codebase in C# became such of a disconnect (changes in VB weren't seen in C# until rebuild), it was all converted to C#.