Skip to content

Defining Symbols for Pre-Processor Directives #1581

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

Closed
dazinator opened this issue Jun 17, 2016 · 1 comment
Closed

Defining Symbols for Pre-Processor Directives #1581

dazinator opened this issue Jun 17, 2016 · 1 comment

Comments

@dazinator
Copy link

dazinator commented Jun 17, 2016

I'm using VS with preview 1 release of tooling, working on an RC2 based application.

I'm looking at code like this:


#if !DNXCORE50
        [XmlAttribute]
#endif

That directive seems to work - but where does it come from and is there a standard list somewhere for each of the frameworks?

What i'd like to know is:

  1. What is the compilation directive for NETSTANDARD1.5 (I have tried NETSTANDARD1_5 and NETSTANDARD15
  2. How do I configure my own.

I tried doing this in project.json but it didn't work:

"frameworks": {
  "netstandard1.5": {
      "define": [ "NETSTANDARD", "NETSTANDARD1_5", "MYOWN" ],
}
@dazinator dazinator changed the title Compilation Directives Defining Symbols for Pre-Processor Directives Jun 17, 2016
@dazinator
Copy link
Author

dazinator commented Jun 17, 2016

I'm an idiot. I should have used intellisense within the project.json

"netstandard1.5": {
"buildOptions": { "define": [ "NETSTANDARD", "NETSTANDARD1_5", "MYOWN" ] },

ryanbrandenburg pushed a commit that referenced this issue Nov 22, 2018
…d tests.

#1443 Block unsolicited wsfed logins by default.
#1520 Update WsFed to use the 2.0 event structure
#1425 Implement WsFed remote signout cleanup
Rework WsFed RemoteSignOutPath logic to work with ADFS #1581
Update versions, dependencies.
ryanbrandenburg pushed a commit that referenced this issue Nov 27, 2018
Corrects the README sample in @aspnet/signalr-protocol-msgpack to use the proper UMD module name.
natemcmaster pushed a commit that referenced this issue Dec 1, 2018
* Switch from using the embedded file provider for the precompiled views
  for actual razor precompilation.
* Add MSBuild props and targets file to include additional assembly
  attributes on the generated precompiled views.
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant