How to debug?
See original GitHub issueHello
Apologies for yet another issue, I did search first but didn’t see this one yet. Closest I found was https://github.com/3F/DllExport/issues/164 but it’s not my problem Maybe related to https://github.com/3F/coreclr/issues/3? . . .
The question is related to:
DllExport -version
:1.7.4- Copy-paste from
Data
tab:
Installed: True; 1.7.4+c1cc52f; invoked: 1.7.4
Project type: CsSdk
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: 9CDCCAD3-44FB-4AB5-89DD-73FF014FFD47
Instance: C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\MSBuild.exe
Project path: C:\Users\asdf\Documents\Projects\asdf\asdf\Installer\Dotnet\Dotnet\Dotnet.csproj
Action: Configure
PlatformTarget: x86
TargetFramework: net472
TargetFrameworks:
TargetFrameworkVersion:
RootNamespace: Installer.Dotnet
AssemblyName:
MgrArgs:
MetaLib: tools\raw\lib\net20\DllExport.dll
MetaCor: tools\raw\lib\netstd\DllExport.dll
Proxy:
StoragePath: .net.dllexport.targets
ddNS: Installer.Dotnet
ddNS max buffer: 500
UseCecil: True
intermediateFiles: True
timeout: 30000
Options: None
RootPath: C:\Users\asdf\Documents\Projects\asdf\asdf\Installer\Dotnet\
PkgPath: C:\Users\asdfDocuments\Projects\asdf\asdf\Installer\Dotnet\packages\\DllExport.1.7.4\
SlnFile:
SlnDir: C:\Users\asdfDocuments\Projects\asdf\asdf\Installer\Dotnet\
DxpTarget: tools\net.r_eg.DllExport.targets
MsgGuiLevel: -1
LockIfError:
Hi
When I try to debug my project with DLLExport
function from a unit-test, Visual Studio asks me to locate the {projectName}.il
file?
Any idea how I can resolve this?
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
What is Debugging? How to Debug Your Code for Beginners
Debugging can be defined as the process of finding the root of a problem in a code base and fixing it. Usually we'll...
Read more >How to Debug Your Code
The best way to learn code debugging is by writing code. If you are interested in building web applications, check out either our...
Read more >Debugging for absolute beginners - Visual Studio
Debugging means to run your code step by step in a debugging tool like Visual Studio, to find the exact point where you...
Read more >JavaScript Debugging
The debugger keyword stops the execution of JavaScript, and calls (if available) the debugging function. This has the same function as setting a...
Read more >Debugging in Visual Studio Code
To bring up the Run and Debug view, select the Run and Debug icon in the Activity Bar on the side of VS...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No. It will just produce both x86 and x64 modules in individual folders (i.e. $(TargetDir)\x86 and $(TargetDir)\x64). There is nothing incompatible for your task. You need only select “x86+x64” when configuring, then Apply. It should help until fix.
InnoSetupExample.zip
ClassLibrary1\bin\Debug\net472\win-x86\x86\CodeDll.iss
Hi, I think the easiest way to reproduce is to run it from InnoSetup
I made a minimal example, just run the script from InnoSetup and it will automatically launch the debugger and give the
.il
error