Skip to content

Conversation

@jjonescz
Copy link
Member

Fixes failures discovered when updating Roslyn in dotnet/roslyn-analyzers#7739.

@jjonescz jjonescz marked this pull request as ready for review July 24, 2025 16:31
@jjonescz jjonescz requested a review from a team as a code owner July 24, 2025 16:31
Copy link
Member

@CyrusNajmabadi CyrusNajmabadi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

c


public ITemporaryStorageStreamHandle WriteToTemporaryStorage(Stream stream, CancellationToken cancellationToken)
{
stream.Position = 0;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if there's a bug here, i'm curious how any VB to C# (or vice versa) tests pass today :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you point me to such tests? I can investigate

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure. like TestGotoDefinitionCrossLanguage. If skeletons aren't working, it's uncelar how the VB project could even know about the C# symbol in order to properly go to def to it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Debugging through the test on Linux, I can definitely see the diagnostic error BC31519: '{0}' cannot be referenced because it is not a valid assembly. being there, I guess the test just doesn't verify diagnostics. I'm not sure how the go-to-def then works, I guess it doesn't really need the metadata reference, but works differently under the hood?

@jjonescz jjonescz merged commit 4b3fd32 into dotnet:main Jul 24, 2025
26 checks passed
@jjonescz jjonescz deleted the cross-lang-ref branch July 24, 2025 17:36
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Jul 24, 2025
jjonescz added a commit to jjonescz/roslyn-analyzers that referenced this pull request Jul 25, 2025
jjonescz added a commit to dotnet/roslyn-analyzers that referenced this pull request Jul 25, 2025
* Handle extension members by 'make member static'

* Suppress warning introduced by Roslyn bump

* Suppress warning in test

* Update tests

* Update Roslyn

To bring in dotnet/roslyn#79571.

* Update Roslyn

To bring in dotnet/roslyn#79576.
ViktorHofer pushed a commit to dotnet/sdk that referenced this pull request Aug 15, 2025
* Handle extension members by 'make member static'

* Suppress warning introduced by Roslyn bump

* Suppress warning in test

* Update tests

* Update Roslyn

To bring in dotnet/roslyn#79571.

* Update Roslyn

To bring in dotnet/roslyn#79576.
@RikkiGibson RikkiGibson modified the milestones: Next, 18.0 P1 Aug 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants