Scratch that, it goes deeper than I initialy thought :). All properties, columns and some indexers named 'ContentType' are now just 'Type' and 'ScopeType' are also 'Type'. Now i see reason why they were renamed. These properties reside inside classes which are also named 'ContentType' and 'ScopeType'. Seems like VB.NET with its lack of rules and order allows it, but C# wont. Thus I believe C# version won't be compatible until VB.NET version and module developers adjust code to more compliant namings :(. Although I'm not sure how much, if at all are these Properties used outside DNN Core, for time being I'll just use my namings, with original columns so URL Master installs and see what happens in time :).

Affected files I came across:
05.03.00.SqlDataProvider, AddContentType.sql, UpdateContentType.sql, AddScopeType.sql, UpdateScopeType.sql, ContentTypes.sql, Taxonomy_ScopeTypes.sql, ContentType.cs (+ 4 other files referencing its property), ScopeType.cs (+ 7 other files referencing its property)

Has anyone tried compiling the VB core code with the CLSCompliant(true) attribute?

I cannot say for certain, but I'd hope it would flush out these inconsistencies.  If it doesn't it's not a lot of use!

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk

I did so many core changes already which I wanted to do long time ago, but couldn't since I have implicit hate for anything "basic". I found some minor issues, however its far beyond what I accomplished when I tried to convert DNN myself 2 years ago :). As far as I tested I could fix all issues myself and it looks pretty much working. I'm willing to put it into low-usage production to speedup debugging process. But you guys did pretty good job.