You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version Used: Visual Studio 2017 RC.3+26114.2.d15rel
Steps to Reproduce:
Create a new C# project
Add a conditional compilation symbol to your project (e.g. AWESOME)
Start typing #if and invoke IntellISense
Expected Behavior:
IntelliSense displays the list of conditional compilation symbols. Ideally, across all configurations but at least for the current project configuration (e.g. Debug|x86).
Actual Behavior:
It helpfully shows true and false. Hooray!
This is especially frustrating for projects that are cross-compiled (i.e. compile for multiple TFMs). The developer cannot easily discover the conditional compilation symbol for the TFM. I ended up running a diagnostic build to see what's passed to CSC.
The text was updated successfully, but these errors were encountered:
Thanks. Was searching, but was probably using the wrong keywords.
@srivatsn@davkean@Pilchie should we bump the priority? I expect cross compilation to become a lot more prominent, considering the improvements in our tooling. Not having IntelliSense for symbols makes this harder than it needs to be.
Version Used: Visual Studio 2017 RC.3+26114.2.d15rel
Steps to Reproduce:
AWESOME
)#if
and invoke IntellISenseExpected Behavior:
IntelliSense displays the list of conditional compilation symbols. Ideally, across all configurations but at least for the current project configuration (e.g.
Debug|x86
).Actual Behavior:
It helpfully shows
true
andfalse
. Hooray!This is especially frustrating for projects that are cross-compiled (i.e. compile for multiple TFMs). The developer cannot easily discover the conditional compilation symbol for the TFM. I ended up running a diagnostic build to see what's passed to CSC.
The text was updated successfully, but these errors were encountered: