Still not getting a .lib

[jpc2]

Edit: Never mind.... I found it. Now to see if I can get FORTRAN to talk to to.

Trying to get a C# project set up so I can call it from a FORTRAN program. Really!

Tried about everything I could here including installing the 8f75a86 build. Still no .lib file.
New to VS2017 so it takes a bit to figure out where things are. And last did any thing if VS years ago.

Microsoft Visual Studio Professional 2017
Version 15.2 (26430.16) Release
VisualStudio.15.Release/15.2.0+26430.16
Microsoft .NET Framework
Version 4.7.02046
Installed Version: Professional
Visual Basic 2017 00369-60000-00001-AA283
Microsoft Visual Basic 2017
Visual C# 2017 00369-60000-00001-AA283
Microsoft Visual C# 2017
Visual C++ 2017 00369-60000-00001-AA283
Microsoft Visual C++ 2017

[jpc2]

Well it worked for a bit. Then I changed something and now it doesn't. The lib.exe problem is due to not having the correct path - I know that much. I may have manually patched it before.

Unloaded the 8f75a86 build and reloaded it. Here is the config.

Builds are set for 'Any CPU', When I build I get this error.

error : Failed to define security permission set for 0x20000001 VistaTGDReader C:\TTCI_Work\Vista_TGD_dev\VistaTGDReader\packages\DllExport.1.5.2\tools\net.r_eg.DllExport.targets 47

I stopped VisualStudio and restarted after the install of DllExport.
Besides the error above, lib.exe is not being found.

Here is the diagnostic build output. Maybe it will help.
build_log.txt

[3F]

The 0x20000001 is known problem #19 (comment)
Uncheck Use our IL Assembler option (msbuild property DllExportOurILAsm = false) if you're using SecurityPermission in your assembly.

About lib.exe it's strange because I see paths to VsDevCmd & vcvarsall from your log:

1>Set Property: DllExportVsDevCmd=C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\Tools\VsDevCmd.bat
1>Set Property: DllExportVcVarsAll=C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\vcvarsall.bat;C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\Build\vcvarsall.bat

it's required by new env VS2017 to get final path like <installationPath>\<Version>\<Edition>\VC\Tools\MSVC\<Version>\bin\<HostTarget>\<Arch> - #37

Please also note, the message Cannot find lib.exe in '...' irrelevant after 8f75a86 because now it just means that we can't find it through obsolete method :) I forget about this msg, so I'll change it later.

What we to do... I can prepare later special build with markers to isolate your problem because it's not reproduced for me.

Then I changed something and now it doesn't.

It would be great to remember something :)

But if you already have configured debug of our project, you can check this place:

DllExport/RGiesecke.DllExport/Parsing/ILAsm.cs

Line 181 in 8f75a86

private int RunLibTool(CpuPlatform cpu, string fileName, string directory)

[jpc2]

@3F Thanks for the reply.
It was the ILAsm setting. I have not specifically set SecurityPermissions . And for this don't need them set. Just trying to build a simple data file reader dll for files with an XML header. Any clue on where it is being set?

I unloaded and reloaded the DllExport package and it works again. Both x64 and X86 have the .dll and .lib files now.

[3F]

@jpc2

Did you try with DllExportOurILAsm = false ?

Can you also give some trivial sample of demo project etc. to reproduce your case with 0x20000001 ? because it should be exactly here - https://github.com/3F/coreclr/blob/master/src/ilasm/assembler.cpp#L2263

I unloaded and reloaded the DllExport package and it works again. Both x64 and X86 have the .dll and .lib files now.

That is, you can't reproduce this anymore ? or it still after some time ?

[3F]

@jpc2 I need details, Please also check it with latest v1.6 beta2 release:

• Latest manager: https://3F.github.io/DllExport/releases/latest/manager/
• Please note again - you shouldn't use standard nuget clients anymore: https://www.youtube.com/watch?v=okPThdWDZMM

[3F]

I closed this, because I can't reproduce this problem and still have no any new details about this.

Reopen if it's reproduced for v1.6-beta3+ releases (together with detailed log).

Please also note: For Visual Studio 15' you should use MSBuild v15+ because the old versions can't populate all required properties because of new API. For example, v14.0.25420.1 may cause this error for VS2017 projects:

lib tool via LibToolDllPath: -1
Export warning EXP0014: RunIlAsm: An error occurred while calling lib.exe: ...

etc.

For this case I recommend to use - hMSBuild

[3F]

How to avoid EXP0014: RunIlAsm. The library manager still cannot be found.:

• This screencast illustrates my solution above - Still not getting a .lib #44 (comment)