Deployment on .Net platforms

Hello,

I have to deploy an application on several computers where only .Net managed libraries are authorized.

I was wondering about salflibc.dll : it seems that it is not a managed library. Do you confirm ? And Does exist an IL compiled version ?

Moreover, is it mandatory to use it in order to run ftn95 executables compiled for .Net ?

It is said in the documentation that for a next release salflibc won't be necessary. Is there an approximative forecasting date ?

Thanks a lot for your precisions.

salflibc.dll is not a managed library and you will need it for FTN95 .NET both for development and deployment.

Please let me know where in the documentation you have seen the reference to a future release for .NET without salflibc.dll.

Thanks Paul.

'A copy of salflibc.dll must be shipped when using the current release of FTN95 .NET (a future release of FTN95 .NET will not require this DLL for .NET).'

http://www.silverfrost.com/ftn95-help/netprog/redistributing.aspx

Should I understand you infirm this ?

There is a mistake in this documentation. There are currently no plans to remove the dependence on salflibc.dll.

There is an option on the DBK_LINK command line, namely /no_salflibc but, I think that you will find that this severely limits what you can do.

Thanks a lot for these precisions, Paul. I tried to compile my project with this option (/no_salflibc) -i precise that it was compiling without-: 1/ the linker told me that some depending systems function (time, etc) was not allowed without salflibc. I took it into account and the linkage succeeded. 2/ But at the execution I have some Memory errors and I can't know from where comes the problem.

i don't have very big needs and maybe I can squeeze the problematic part if I know where it comes from. Do you have in mind the restrictions due to this libraryr or how to know what they are?

Thanks a lot.

Memory restrictions will probably depend only on the amount of RAM and virtual memory on your computer. I do not know of any other limits arising from the use of FTN95 .NET.

Hello, I am able to precise the problem : even when i compile & link with the flag no_salflibc, my library always depends on salflibc.dll

If i remove the salflibc.dll, I have this error during the execution at this place :

Exception non gérée : System.DllNotFoundException: Impossible de charger la DLL 'SALFLIBC.dll': Le module spécifié est introuvable. (Exception de HRESULT : 0x80 07007E) à Salford.Fortran.RTLibrary.__display_personal_banner() à Salford.Fortran.RTLibrary.DisplayPersonalBanner()

If i keep the salflibc.dll, a memory error occurs at the same place ( Salford.Fortran.RTLibrary.DisplayPersonalBanner ).

I suppose it is a reference to the white window which appears in the personal version. Do you agree ? Does it mean that if i buy the licence, it will work ? (At this time I use the personal version but of course want to buy the licence ... if it works!) Thanks a lot Christophe

Thanks a lot

I cannot guarantee that it will work if you get a licence. You should email Silverfrost to see if they can help.

Silverfrost proposed to me a trial version without the banner and it works !

Now i have an other problem : I would need to add to my MSIL assembly obtained by ftn95 some attributes: for instance, this one : AllowPartiallyTrustedCallers .

In C#, we obtain this attribute adding this in the code : [assembly:System.Security.AllowPartiallyTrustedCallers]

Is it possible in fortran with ftn95 ? I suppose that ASSEMBLY_INTERFACE could/should do this kind of things, but I do not know the syntax.

Thanks again for your help !

The latest release of FTN95 contains the linker DBK_LINK2/4 that allows .cs files to be added to the command line. The result is that some attributes are copied from the .cs file into the resulting assembly but I don't know if the one you mention will be copied. (See the latest Announcement on this forum)

If it doesn't work then I might be able to add this feature for you.

Thanks Paul, I am trying your solution and I have 2 problems :

If i use this command :

dbk_link2  libst.dll  AVCORR.dbk AssemblyInfo.cs

Some attributes are added effectively, bur not : [assembly: System.Security.AllowPartiallyTrustedCallers] (as you seem to anticipate). It would help me greatly if you could add this feature ! But :

My second problem : I want to have an assembly with strong name, so I use : http://www.silverfrost.com/ftn95-help/netprog/signing.aspx So my dbk_link2 command generates a module (mdl) :

dbk_link2  libst.mdl  AVCORR.dbk AssemblyInfo.cs

In this case, it seems that no attribute is attributed to the final assembly.

Thanks again !

Do you have any news for my problem ? Thanks Christophe

I have added your request about an extra attribute to the wish list but I don't know when I will get time to look at this.

Regarding the lack of attributes when using a strong name, at the moment I have no idea what to do with that one. I see no reason for that and it seems unlikely that DBK_LINK would have such an effect. All I can do is look at the issue with the one above.

I suggest that you check your conclusion and if possible see if you get the same effect another language such as C#.