Cannot use reference

[stef-pellegrino]

Steps to reproduce:

Create C# DLL within a folder TestDll

[DllExport]
public int test() {
  return 0;
}

• Open VS2019 and Test solution
• Put"DllExport.bat" in same directory than Test.sln
• Double click on DllExport.bat
• Select [Apply]
• Focus on VS + reload all
  rebuild gives me :
  error CS0246: The type or namespace name 'DllExport' could not be found (are you missing a using directive or an assembly reference?)

Click on reference gives me "The proejct cannot be viewed in the object browser because it is not available or not yet build" !??

• DllExport -version: 1.7.4
• Used Visual Studio / MSBuild / VS 2019 (Windows 10)

[3F]

@stef-pellegrino Please copy everything from the Data tab for the selected project in which it was installed.

[zuoyi1025]

Same Problem here...has anyone any hint?

[3F]

@zuoyi1025
Please follow the issue template to provide a minimal case info. Log / demo projects are better in a quick inspections. But I didn't even see the requested info from the Data tab.

Note the build must be with diagnostic level. For msbuild, /v:diag or better /bl. Also note the /bl by default collects the source text of project files. See Doc. When configuring use the -debug key.

[leculver]

Same problem. The issue seems to be that RichCodeNav.EnvVarDump is missing? Here's what the package manager output looks like when attempting to add the "DllExport" nuget package:

  GET https://api.nuget.org/v3-flatcontainer/richcodenav.envvardump/index.json
  NotFound https://api.nuget.org/v3-flatcontainer/richcodenav.envvardump/index.json 129ms
NU1101: Unable to find package RichCodeNav.EnvVarDump. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages, nuget.org
Package restore failed. Rolling back package changes for 'TestPlugin'.
Time Elapsed: 00:00:00.4875334

[3F]

NU1101: Unable to find package RichCodeNav.EnvVarDump.

We do not use RichCodeNav.EnvVarDump. Some of the dependencies in your project requires this. You obviously need configuring package sources, for example via NuGet.config

Please also note we don't provide an official NuGet support for this tool
(if something is working, it's working, but for other case please use our official way. Briefly, just click this inside folder where .sln)

[T35R6braPwgDJKq]

Installed: True; 1.7.4+c1cc52f; invoked: 1.7.4
Project type: Cs
Storage: ProjectFiles
Compiler.Platform: Auto
Compiler.ordinalsBase: 1
Compiler.rSysObj: False
Compiler.ourILAsm: False
Compiler.customILAsm: 
Compiler.genExpLib: False
Compiler.peCheck: PeIl
Compiler.patches: None
PreProc.Type: None
PreProc.Cmd: 
PostProc.Type: None
PostProc.ProcEnv: $(SolutionPath);$(MSBuildThisFileFullPath)
PostProc.Cmd: 
SignAssembly: 
Identifier: FEDE8CF5-44B7-41A2-88A4-2D50ED26DE2C
Instance: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\amd64\MSBuild.exe
Project path: C:\Users\test\source\repos\testdll\testdll\testdll.csproj
Action: Configure
PlatformTarget: AnyCPU
TargetFramework: 
TargetFrameworks: 
TargetFrameworkVersion: v4.5
RootNamespace: testdll
AssemblyName: testdll
MgrArgs: 
MetaLib: tools\raw\lib\net20\DllExport.dll
MetaCor: tools\raw\lib\netstd\DllExport.dll
Proxy: 
StoragePath: .net.dllexport.targets
ddNS: testdll
ddNS max buffer: 500
UseCecil: True
intermediateFiles: False
timeout: 30000
Options: None
RootPath: C:\Users\test\source\repos\testdll\
PkgPath: C:\Users\test\source\repos\testdll\packages\\DllExport.1.7.4\
SlnFile: 
SlnDir: C:\Users\test\source\repos\testdll\
DxpTarget: tools\net.r_eg.DllExport.targets
MsgGuiLevel: -1
LockIfError: 

[3F]

@T35R6braPwgDJKq
Please attach at least the log when configuring and/or build log with diagnostic level to inspect the current problem.

C:\Users\test\source\repos\testdll\testdll\testdll.csproj

Attach everything if this is a really empty test project for better help to reproduce the problem locally.
Thanks.

[Miedziaq]

Hi in connecting to our other thread, I prepared some logs.
You should get it from wetransfer.com to ****@outlook.com

[3F]

I prepared some logs.

@Miedziaq There is no MSB3245: Could not resolve this reference as you mentioned in #196 (comment)

At least this is what I see in your build log.

There is single Error : Invalid Option: /PVP but this is absolutely another problem. Rather because of your mixed incorrect things in .csproj as I said earlier, for example, due to:

<TargetExt>.pvp</TargetExt>

<Target Name="PublishPVP" AfterTargets="RGieseckeDllExport" Condition="Exists($(PdfXEditorPluginDir))">
  <Message Text="=== Publish PVP ... ====================================================" />
  <CreateItem Include="$(OutputPath)$(AssemblyName)$(TargetExt)">
    <Output TaskParameter="Include" ItemName="PvpFilesToCopy" />
  </CreateItem>
  <!--<Copy SourceFiles="@(PvpFilesToCopy)" DestinationFolder="$(PdfXEditorPluginDir)" />-->
  <Message Text="=== Publish PVP ... done ===============================================" />
</Target>

In any case we support only .DLL and .EXE modules. Just consider using our Pre/Post-processing if you need some actions/packing/etc:

• https://github.com/3F/DllExport/wiki/PreProc
• https://github.com/3F/DllExport/wiki/PostProc

To all,

Guys! I cannot personally resolve the unknown issues until I receive the minimal info requested earlier. Please also don't fragment information because this could aggregate various unrelated issues between the different stages as you can see above. Also do not distort info as much as possible (please only remove any confidential data).

[3F]

If I understood (for all that) the problem correctly,

error CS0246: The type or namespace name 'DllExport' could not be found (are you missing a using directive or an assembly reference?

For some cases we need to regenerate missed meta. This can be done manually using the following command:

DllExport -action Restore

If so, 7ee50d0 will fix the current problem. You can check it using related CI build until the new version.

I close the issue. If the fix doesn't help, please open it again or create a new one.