Apparently not. I've been working on a new project (Sonos integration with Premise) and had created a class with a property named "ID". Premise took it with no issues, but I had a catastrophic failure on both my dev and prod instances of Premise the day after Christmas. After a restart, Pemise wouldn't load complaining of a corrupt Premise XDO Schema file.
After painstakingly repairing my setup, it happened again on Saturday (yes I take regular backups of my config, but they were corrupted as well). I went through the "BAD" schema files Premise put in it's \Backup directory using Visual Studio, and noticed several "Duplicate attribute" errors. When you look at the XML file that stores the Premise Schema, you'll notice that every object has an attribute called "ID" which contains the object ID for the Premise Object. My class had a property called "ID" which showed up as a XML attribute in the schema called "ID". So, every instance of my class in my setup had an illegal XML node in the schema which I believe was causing Premise to blow-up. I renamed the property, and the problem hasn't returned.
Hopefully, this helps someone avoid what happened to me.
After painstakingly repairing my setup, it happened again on Saturday (yes I take regular backups of my config, but they were corrupted as well). I went through the "BAD" schema files Premise put in it's \Backup directory using Visual Studio, and noticed several "Duplicate attribute" errors. When you look at the XML file that stores the Premise Schema, you'll notice that every object has an attribute called "ID" which contains the object ID for the Premise Object. My class had a property called "ID" which showed up as a XML attribute in the schema called "ID". So, every instance of my class in my setup had an illegal XML node in the schema which I believe was causing Premise to blow-up. I renamed the property, and the problem hasn't returned.
Hopefully, this helps someone avoid what happened to me.