-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Source generated documents should be opened in the real workspace instead of Miscellaneous files #50676
Comments
The core of this is done under a feature flag, moving to 16.11 for the rest of the todo items. |
The feature checkbox is there, we're targeting 17.1 for enabling it by default. |
The checkbox is there, but we've fixed enough in 17.2 that we don't want to turn it on late. It'll be turned on by default in 17.3. |
This doesn't seem to be completely fixed, I just reproed this with 17.5.3: Ended up here by F11 stepping into a method that called a generated one while debugging (after hitting a breakpoint in the manually written method that invoked the generated one). VS went into this file and let me continue debugging (eg. with F10 to go line by line), but the file was still classified as "miscellaneous", and IntelliSense was half broken (eg. CTRL + click and F12 didn't work at all and wouldn't let me jump to selected symbols, such as other generated members the code is using). |
@Sergio0694 Do you have this unchecked in Tools > Options? We've rolled out the feature flag to all users at this point (unless I broke something), but if you had manually turned it off at some point you might not see it active. |
Yup, I have that option set 🥲 |
Was this the file that the debugger opened? Can you copy/paste in the path that the file is? You can redact the filename and username, I'll be looking at exactly where under %TEMP% or similar it is. |
The file is in:
I can confirm the repro steps are pretty easy at least, if that helps:
That'll open the generated file in miscellaneous mode, from that path. Also should we reopen this, or should I open a different issue to track this? 🙂 |
Some tasks for the implementation
The text was updated successfully, but these errors were encountered: