forums.silverfrost.com

Yes, it was the full version.

No, it was an upgrade version.

We upgraded to 2013 Community edition. I then reinstalled the latest version to get the plug in. It works just fine.

In C# you can do it by just checking it for null:
using System;
public static boolean IsNull(System.Object object)
{
return (object == null);
}

Since every object i ...

I would change your fortran to this:
C*************************************************************
SUBROUTINE SPINIT(irrc,scr,stitle1,stitle2,sversion,syear)
implicit DOUBLE PRECISION ...

I think it was a 77 construct. I did a quick search and found this link An automatic object can appear in a character declaration. The object cannot be a dummy argument, and its length must be declare ...

They are just strings. Here's a the basic code.

using System;
using System.Text;

namespace MyNamespace
{
public static class MyClass
{
public static short CSharpFactor&# ...

We are calling a fortran dll from a C# program, and pass in a object we've defined and a boolean. However, we do call a lot of C# methods in the fortran. The fortran was converted from F77, so we are ...

In your fortran code, add this line after the function statement:
ASSEMBLY_INTERFACE(NAME="SPINIT")

Also, make sure that the fortran dll is included in your C# references.

Jil ...

Well, I had the same problem again today. I had split another function out into it's own source file for a total of 197 files in my .NET Fortran project.

Debug linked just fine. However, release bl ...

We have played with this some more.

The problem seems to be the optimization flag. If I turned that off, the project will compile for RELEASE.

Now, the project is large. I have been moving indi ...

I have a Fortran project that is compiled into a dll to be accessed from C#. It compiles fine in debug mode, but I get the error "Internal Linker Error" when compiling it in release.

I h ...

I found a problem with the Visual Studio plug in.

When the FTN plugin to Visual Studio 2008 accesses a dll that is stored outside of the solution, it locks the dll.

I have a solution with a FT ...

We are converting a FTN77 program to .NET in Visual Studio 2008. I am getting a memory overwrite somewhere in the code, so I am trying to use CheckMate instead of Debug as my complier configuration t ...