- Support for .NET 2.0 and Visual Studio 2005 was added to FTN95 at version 5.00.
- Support Visual Studio 2008 support was added at version 5.20.
- Support for .NET 4.0 and Visual Studio 2010 was added at version 6.00
- Support for Visual Studio 2012 and .NET 4.5 was added at version 7.00
- Support for Visual Studio 2013 was added at version 7.10
- Support for Visual Studio 2015 was added at version 8.10
- Support for Visual Studio 2017 was added at version 8.50
- Support for Visual Studio 2019 is available on request
Although '.NET' and Visual Studio are closely related the support for them in FTN95 is separate:
- You can produce .NET code with FTN95 without using Visual Studio.
- You can produce and debug Win32 code with or without Visual Studio.
- You cannot debug 64-bit code directly in Visual Studio.
FTN95 can produce code that is compatible with all versions of .NET that runs on Microsoft Windows (note that .NET 1.1 code is also .NET 2.0 compatible and .NET 2.0 code is.NET 4.0 compatible) via Visual Studio.
The target framework can be selected from the project properties.
If you use the command line then you will have to set a switch to target a particular framework:
| Framework || Compiler Switch || Linker |
|.NET 2.0||/CLR /CLR_VER 2||dbk_link2|
|.NET 3.0||/CLR /CLR_VER 2||dbk_link2|
|.NET 3.5||/CLR /CLR_VER 2||dbk_link2|
|.NET 4.0||/CLR /CLR_VER 4||dbk_link4|
|.NET 4.5||/CLR /CLR_VER 4||dbk_link4|
The reason you have to specify the .NET framework is that many people have multiple versions on their machine, probably without realising.
In addition, you need to use a different linker for .NET 2.0 (dbk_link2) and .NET 4.0 (dbk_link4) because the linker runs under the destination framework to produce the
.NET 3.0 and .NET 3.5 is .NET 2.0 with extra libraries -- hence you just use the .NET 2.0 support for those version.
To debug .NET 4.0 code you will require Visual Studio 2010, 2012, 2013, 2015, 2017 or 2019.
To use any framework, that version's directory must be on the path.
More to Explore