forums.silverfrost.com Forum Index forums.silverfrost.com
Welcome to the Silverfrost forums
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Support for .NET-Core / .NET-Standard

 
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> Support
View previous topic :: View next topic  
Author Message
gperiskic



Joined: 18 Dec 2009
Posts: 34
Location: Stuttgart, Germany

PostPosted: Fri Feb 08, 2019 3:47 pm    Post subject: Support for .NET-Core / .NET-Standard Reply with quote

Does FTN support .NET-Core or .NET-Standard and are there any windows dependencies in the FTN redistributable dlls? We would like to deploy our with FTN compiled dlls on Amazon ECS (Elastic Container Service) for increased scalability with a microservices architecture.
It would be nice to have to possibility to target either .NET Standard (for broad compatibility) or at least .NET 4.7.2 (or higher) as recommended here https://docs.microsoft.com/en-us/dotnet/core/porting/, which ensures that API alternatives can be used for .NET Framework-specific targets when .NET Core doesn't support a particular API.
Back to top
View user's profile Send private message Visit poster's website
Robert



Joined: 29 Nov 2006
Posts: 444
Location: Manchester

PostPosted: Sat Feb 09, 2019 3:33 pm    Post subject: Reply with quote

FTN95 does not support .NET Core. It is a different format and specification.
Back to top
View user's profile Send private message Visit poster's website
gperiskic



Joined: 18 Dec 2009
Posts: 34
Location: Stuttgart, Germany

PostPosted: Sat Feb 09, 2019 5:38 pm    Post subject: Reply with quote

Hi Robert,
thanks. What about my other questions - would it be possible that the .NET compiler targets .NET Framework 4.7.2 or higher? Or maybe to directly target .NET Standard?
The way I understand this, .NET Standard is a set of basic .NET APIs whach are commeon to .NET framework, .NET Core and other .NET derivates (https://docs.microsoft.com/en-us/dotnet/api/?view=netstandard-2.0). It is a kind of .NET Framework without the support for WPF, WinForms and ASP.Net. Most of the Fortran code doesn't target these .NET Framework specific APIs anyway - hardly someone makes a GUI in Fortran nowdays. Probably 90% of Fortran is scientific code written by engineers in 80s and 90s - and .NET Standard APIs could be more than sufficaint for this.
What do You think?
Cheers,
Goran
Back to top
View user's profile Send private message Visit poster's website
John-Silver



Joined: 30 Jul 2013
Posts: 1520
Location: Aerospace Valley

PostPosted: Tue Feb 12, 2019 10:23 pm    Post subject: Reply with quote

Goran wrote:
Quote:
hardly anyone makes a GUI in Fortran nowdays.


... because they don't use FTN95 with it's clearwin+ capabilities for professional GUI interfaces, integral to Fortran !!!
if a GUIis needed then try the Clearwin+ option first .
_________________
''Computers (HAL and MARVIN excepted) are incredibly rigid. They question nothing. Especially input data.Human beings are incredibly trusting of computers and don't check input data. Together cocking up even the simplest calculation ... Smile "
Back to top
View user's profile Send private message
LitusSaxonicum



Joined: 23 Aug 2005
Posts: 2388
Location: Yateley, Hants, UK

PostPosted: Wed Feb 13, 2019 11:49 am    Post subject: Reply with quote

Well I agree. Not many people in the world of software development are creating GUI interfaces in Fortran, probably because people are (a) using other languages for the task, and (b) many Fortran-coded things probably don't need a GUI. If you do need a Windows GUI and you have to program in Fortran, then there are alternatives to FTN95 and Clearwin+, so that 'not many people' still represents a market of some size. Personally, Clearwin+ is by far the easiest way to do the job, especially as it is properly integrated in FTN95. FTN95 has, in my opinion, what the Fortran standard needs, and the biggest needs are graphics and the tools to build GUIs. FTN95 is a one-stop-shop for everything you need.

I recently asked in another post for someone to tell me what the advantages of ,NET and Visual Studio are, and all I got from the end of it was that it was a matter of personal preference.

Oh, and I forgot to say that some of that body of people programming in Fortran do it as a sideline, and are using skills largely acquired decades ago. .NET is a new trick, and they (or should I say we?) are old dogs.

Eddie
Back to top
View user's profile Send private message
anthony.sneed



Joined: 21 Feb 2019
Posts: 1

PostPosted: Tue Apr 16, 2019 5:42 pm    Post subject: Support for .NET-Standard Reply with quote

For the broadest compatibility it is recommended that class libraries should target .NET Standard (https://docs.microsoft.com/en-us/dotnet/standard/net-standard), versus a specific .NET implementation (.NET Framework, .NET Core, etc). .NET Standard, which is forward-compatible, essentially represents a more modern approach to Portable Class Libraries. For example, if you were to target .NET Standard 1.1 (https://docs.microsoft.com/en-us/dotnet/core/tutorials/libraries#how-to-target-the-net-standard), the resulting assemblies would be compatible with the full .NET Framework version 4.5 or greater (4.5.x, 4.6.x, 4.7.x, etc), as well as .NET Core version 1.0 or greater (1.x, 2.x, 3.x, etc).

Because of this broad compatibility, .NET Standard assemblies can be compiled (JIT, pre-JIT, etc) to run on various flavors of Windows (Server Core, Nano, etc) and also on Linux. This can have benefits for applications that run in Docker containers, where the platform options can affect scalability and performance.

Would you consider updating the Silverfrost compiler to target .NET Standard?
Back to top
View user's profile Send private message
alex21



Joined: 20 Apr 2011
Posts: 75
Location: Australia

PostPosted: Fri Jun 21, 2019 6:13 am    Post subject: Re: Reply with quote

gperiskic wrote:
Hi Robert,
thanks. What about my other questions - would it be possible that the .NET compiler targets .NET Framework 4.7.2 or higher? Or maybe to directly target .NET Standard?
The way I understand this, .NET Standard is a set of basic .NET APIs whach are commeon to .NET framework, .NET Core and other .NET derivates (https://docs.microsoft.com/en-us/dotnet/api/?view=netstandard-2.0). It is a kind of .NET Framework without the support for WPF, WinForms and ASP.Net. Most of the Fortran code doesn't target these .NET Framework specific APIs anyway - hardly someone makes a GUI in Fortran nowdays. Probably 90% of Fortran is scientific code written by engineers in 80s and 90s - and .NET Standard APIs could be more than sufficaint for this.
What do You think?
Cheers,
Goran


.NET Framework 4.6.2 is equivalent to .NET Standard 2.0, I am not sure the compilation works but I think it is possible to use the DLLs generated by Silverfrost FTN95 with .NET Core... but I have not tried.
Back to top
View user's profile Send private message MSN Messenger
gperiskic



Joined: 18 Dec 2009
Posts: 34
Location: Stuttgart, Germany

PostPosted: Fri Sep 06, 2019 10:27 am    Post subject: Reply with quote

Thanks alex21. Yes, it works, one needs to compile with /NO_SALFLIBC switch and remove the 32-bit flag after the compilation.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> Support All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group