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

Implement DebuggerNonUserCode as an option in response to issue #106 #346

Conversation

garyhuntddn
Copy link

Introduce new property that can be used in the OutputFile derived classes to dictate whether to include the DebuggerNonUserCode attribute in generated code.

Added this to the build task and associated classes and to the documentation.

I've not implemented it in the same way as abstract was implemented it as it would have meant introducing multiple properties (in Lexer and Parser) to do the same thing. Obviously happy to change this if that is the preferred option.

Closes #106

garyhuntddn and others added 4 commits May 23, 2020 13:21
…classes to dictate whether to include the DebuggerNonUserCode attribute in generated code.

Add this to the build task and associated classes and to the documentation.
…classes to dictate whether to include the DebuggerNonUserCode attribute in generated code.

Add this to the build task and associated classes and to the documentation.
@garyhuntddn garyhuntddn deleted the use_DebuggerNonUserCode_attribute branch May 30, 2020 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add DebuggerNonUserCode to generated classes
1 participant