Why does IronPython not follow the standard C# naming conventions, why so many FxCop errors?
We have fixed all FxCop errors in the IronPython.Hosting namespace which is the main public API exposed by IronPython. However, there are other public types that are marked public either because the generated IL code needs them or because of historical reasons. While we would like to fix all FxCop issues for all public types, those remaining do not affect users of IronPython. We want to release IronPython 2.0 under the principles of “release early, release often”. We thought that it was unnecessary to delay the release to take the time to do this work first. These kinds of issues will be resolved as we work on future releases.
Related Questions
- The Standard for Geospatial Dataset File Naming has some different file naming conventions that those outlined in the Manual for Managing Geospatial Datasets in Service Centers. Will the Standard for Geospatial Dataset File Naming be updated to match the other manual?
- Why does IronPython not follow the standard C# naming conventions, why so many FxCop errors?
- What conventions should I follow in naming my devices using FCode proms?
