Hmmmm. I tried on the review site here and the focus mode isn't working. I don't know if that's a resource issue or not.

@BillWagner I tried it as well see the issue.

I can't remember if it was doing that before I added the second commit. Let me do a different change on a separate API to test.

So the new example built and it makes no difference.
https://review.docs.microsoft.com/en-us/dotnet/api/system.math.round?view=netframework-4.8&branch=pr-en-us-3769

The first interactive sample uses the old syntax and runs fine.

The other one uses the new syntax and the issue happens again.

@rloutlaw here are my findings with my latest tests:

• Using just the ID number instead of whole snippet name doesn't work. It just loads the entire file.
  Change: 6146276
  Review URL
• Same happens if I put a bad snippet ID. Expected: ideally I'd get a warning or a missing snippet (current behavior with the other syntax I believe)
  Change: 5f452e2
  Review URL
• snippet tag with inner snippet tags - inner tags are shown
  Review URL
• Can we use the # syntax like we used to for source paths? Or is that not supported in the new syntax?

Changing the interactive type made the sample load and run.
https://review.docs.microsoft.com/en-us/dotnet/api/system.collections.generic.list-1?branch=pr-en-us-3769&view=netframework-4.8#code-try-1

However, we still need to clear the snippets comments from the resulting code.

Works now, hooray! I ran it on Chrome and Edge.
C# and C++ compile, run and exit. (Run not available VB and F#.)

You scared for a second @wadepickett 😄 There's no C++ code running, It's just missing so it displays C# code as a fallback.

@mairaw , yes, sorry, no C++ code running of course!
The language drop down does stick and show C++ even though the page is C#, which it also does on the live site. Is that an issue already filed by chance?

I think the behavior you're seeing @wadepickett is by design. When you select C++, if there are no C++ samples available, it will show an example from a fallback language. In this case, C#.
Are you seeing anything different?

Checking if bad ID will be caught by build now

Snippet comments stripping was deployed to production. Testing.

Status update:

• Build warnings are still not reported for bad snippet IDs
• Snippet comments are being stripped but not totally. If you reference the entire file, the most external comments are still rendering

Status update:

• Build warnings are still not reported for bad snippet IDs (and now the sample is simply not loaded and is loading a different language sample instead)
• Snippet comments are being stripped but not totally. If you reference the entire file, the most external comments are still rendering but the workaround is to reference that snippet ID surrounding the snippet, unless you want to update the sample.

This should be good to merge once we confirm that my latest change works for the system.object page

/cc @tdykstra Here are try.net examples using the new syntax. It might help on your project.