| Reporter |
Aleksey Syryh (Ender)
|
|---|---|
| Created | Apr 26, 2018 2:32:52 PM |
| Updated | Apr 26, 2018 2:38:23 PM |
| Subsystem | Code Analysis |
| Assignee | Ivan Serduk (IvanSerduk) |
| Priority | Normal |
| State | Submitted |
| Type | Bug |
| Fix version | No Fix versions |
| Affected versions | No Affected versions |
| Fixed In Version ReSharper | Undefined |
| VsVersion | All Versions |
I will describe my user experience. See attached example project.
It is sample WCF Client-Server application. Client have file reference.cs generated by VS. Also it have HelloServiceClient.cs file to implement some logic, which should not be overwriten when reference.cs generated will be generated again.
Everything are workiung, but HelloClient\Program.cs have wrong namespace. I want to fix that issue, and all issues of that type, so I am using "Move to 'HelloClient' namespace -> Adjust namespaces in project/solution" option, and I receive the project which can not be compiled.
What's wrong? ReSharper moves content of Reference.cs from namespace "HelloClient.HelloService" to "HelloClient.Connected_Services.HelloService". It fixes all references but does not find my partial implementation.
But even if I did not have a partial implementation, this behavior is still not the right thing - after all, after the re-generation of the reference.cs file, there will be a compliation error (because it will be generated in "HelloClient.HelloService" namespace).
In my opinion, such "fixes" should not affect autogenerated files. I'm sure that you already have such a check (after all, Resharper does not offer to correct that "issue" if you open the reference.сs in the editor), but it looks like that check are not used in that case.