| Reporter |
Werner Strydom (bloudraak)
|
|---|---|
| Created | Apr 14, 2012 1:07:06 AM |
| Updated | Apr 16, 2012 9:12:08 PM |
| Priority | Major |
| Type | Bug |
| Fix versions | No Fix versions |
| State | Submitted |
| Assignee | Sergey Coox (coox) |
| Subsystem | Code Analysis |
| Affected versions | 6.1.1 |
| Fixed in build | No Fixed in build |
Consider an application that exposes or consumes WCF services. Many times, the configuration files define the services and their configuration, including authorization and other extension points. ReSharper does not recognize, nor suggest any corrections types defined the WCF configuration. This poses a challenge when one wants to navigate to the WCF service, rename a type or have a typo.
The WCF configuration is well defined at MSDN. It would be advantagous if ReSharper can detect types that cannot be found in WCF configuration, as well as apply refactoring to it and or allow someone to navigate to the type from the configuration.
The WCF configuration is well defined at MSDN. It would be advantagous if ReSharper can detect types that cannot be found in WCF configuration, as well as apply refactoring to it and or allow someone to navigate to the type from the configuration.