- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
First, let me state I know very little about Intel Visual Fortran andam fishing for some help in making a purchasing decision.
I'm a Lahey Fortran developer and a Visual Studio (VB, C+) developer and hope to be able to use the .NET Framework in Fortran programs. Does Intel Visual Fortran allow the use of .NET and COM objects within the code to access databases and other programs? If not, how well does it handle mixed language applications? Can the debugger track the code in both languages? Does it only allow mixed language useage through linking of DLLs? Thanks in advance for any help you can give me with this.
I'm a Lahey Fortran developer and a Visual Studio (VB, C+) developer and hope to be able to use the .NET Framework in Fortran programs. Does Intel Visual Fortran allow the use of .NET and COM objects within the code to access databases and other programs? If not, how well does it handle mixed language applications? Can the debugger track the code in both languages? Does it only allow mixed language useage through linking of DLLs? Thanks in advance for any help you can give me with this.
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Intel Visual Fortran does not play in the .NET framework directly the way that Lahey Fortran does, but it does support multiple ways of interacting with .NET. You can call .NET and COM objects through the use of the "Module Wizard" tool that generates Fortran jackets for .NET and COM methods. This is not something I'd suggest jumping into, but it is an option. It also supports generation of a COM Server that can be used from .NET.
.NET applications can call Intel Fortran DLLs, and yes, mixed-language debugging is supported. Just be sure to enable "Unmanaged code debugging" in the .NET project. Sample applications are provided with the product.
For database access, many people do call Access through the COM interface, or use the freeware f90SQL library to access any ODBC database.
.NET applications can call Intel Fortran DLLs, and yes, mixed-language debugging is supported. Just be sure to enable "Unmanaged code debugging" in the .NET project. Sample applications are provided with the product.
For database access, many people do call Access through the COM interface, or use the freeware f90SQL library to access any ODBC database.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Intel Visual Fortran does not play in the .NET framework directly the way that Lahey Fortran does, but it does support multiple ways of interacting with .NET. You can call .NET and COM objects through the use of the "Module Wizard" tool that generates Fortran jackets for .NET and COM methods. This is not something I'd suggest jumping into, but it is an option. It also supports generation of a COM Server that can be used from .NET.
.NET applications can call Intel Fortran DLLs, and yes, mixed-language debugging is supported. Just be sure to enable "Unmanaged code debugging" in the .NET project. Sample applications are provided with the product.
For database access, many people do call Access through the COM interface, or use the freeware f90SQL library to access any ODBC database.
.NET applications can call Intel Fortran DLLs, and yes, mixed-language debugging is supported. Just be sure to enable "Unmanaged code debugging" in the .NET project. Sample applications are provided with the product.
For database access, many people do call Access through the COM interface, or use the freeware f90SQL library to access any ODBC database.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page