Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aspect Injector processing has failed (v2.8.0), Mono.Cecil.Cil.SymbolsNotFoundException #200

Closed
minchili opened this issue Nov 3, 2022 · 9 comments
Assignees
Labels

Comments

@minchili
Copy link

minchili commented Nov 3, 2022

Environment (please complete the following information):

OS: Windows 10 64 bit
Framework: .Net Framework 4.7.2, C# 8.0
Type of application: dll / Console
Version of AspectInjector: 2.8.0

Describe the bug

When I create the project and install Aspect Injector and then build I get the following error:
(The project has not even written any code, it is just a simple build.)

Error1: Aspect Injector processing has failed. See other errors.
Error2: Processing failure: Mono.Cecil.Cil.SymbolsNotFoundException: No symbol found for file: C:\Users**\Repositories\Samples\AOP\ClassLibrary1\obj\Debug\ClassLibrary1.dll

@minchili minchili added the bug label Nov 3, 2022
@pamidur pamidur self-assigned this Nov 3, 2022
@pamidur
Copy link
Owner

pamidur commented Nov 3, 2022

Hi @minchili , thank you for the report, I'll look at it shortly.
Is there any chance you could send the project as zip?

@minchili
Copy link
Author

minchili commented Nov 4, 2022

ClassLibrary1.zip
Thanks for the reply, here is the project where the error occurred.

@pamidur
Copy link
Owner

pamidur commented Nov 6, 2022

What IDE you use? I didn't manage to reproduce it on VS2022

@minchili
Copy link
Author

minchili commented Nov 8, 2022

I use VS2022 too, this is my IDE info.
IDE Info.txt

@leandrogomes777
Copy link

leandrogomes777 commented Nov 14, 2022

Hi, we've have the same issue here.

We have a workaround to compile.
Set the DebugType on your csproj to portable (instead of full or pdbonly).
Ex:
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
<DebugSymbols>true</DebugSymbols>
<DebugType>portable</DebugType>

@pamidur could you address this issue? We have to maintain the configuration of pdb to "full" here.

@pamidur
Copy link
Owner

pamidur commented Nov 14, 2022

@leandrogomes777 thank you for the input. It is definitely an issue with PDB type and Mono.Cecil

@pamidur
Copy link
Owner

pamidur commented Nov 14, 2022

@leandrogomes777 @minchili
could you please check if 2.7.2 and 2.7.1 have the same issue?

@leandrogomes777
Copy link

Hi @pamidur, i've made tests with the 2.7.2 version and no issues.

@pamidur
Copy link
Owner

pamidur commented Nov 14, 2022

Ok so I found a root cause - over-optimization while compiling for self-contained image
Should be fixed in 2.8.1

Thank you @leandrogomes777 , @minchili

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants