Types inside the renamed file are seen as duplicate

[tugberkugurlu]

Environment data

dotnet --info output:

 Version:            1.0.0-preview2-003121
 Commit SHA-1 hash:  1e9d529bc5

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64

VS Code version:

Version 1.7.2 (1.7.2)
7ba55c5860b152d999dda59393ca3ebeb1b5c85f

C# Extension version:

1.5.3

Steps to reproduce

Load a project, rename a file which has a class in it.

Expected behavior

Should work as it has been before.

Actual behavior

It doesn't unload the type inside the deleted file and see the type inside new file as a duplicate:

[matthamil]

This is the same bug in #785 and #803

[tugberkugurlu]

In addition to this one, there is also another bug which is related to file delete. If you delete a file, the members inside that file still seems valid (e.g. shows up on IntelliSense list, etc.). Should I open a separate issue for this?

[matthamil]

@tugberkugurlu I'm able to recreate that bug too. I think it's related. The Intellisense seems to not update its knowledge of the current project when any existing files are renamed or deleted; however, it works fine when you're adding new files that didn't previously exist. Hoping this gets fixed, it's been a reported issue since September (#785).

[filipw]

The problem is that at the moment, upon rename, the Workspace only raises a DocumentAdded event for the renamed doc, but never raises DocumentRemoved for the old one.

If you continue renaming 10 times, you end up with 10 copies of the same document in the workspace.

[DustinCampbell]

Yeah, we need to fix that.

[DustinCampbell]

OK. We're going to use #785 to track fixing this issue.