Create new XmlnsDefinition standard about prism HOT 10 CLOSED

I like it. My vote/preference would be without the www (seems sort of old skool and not as concise). I also like the domain in general, as it leads towards a (wicked-short) suggested candidate "pl" prefix. :)

from prism.

Well since we don't have any components in the VS toolbox, we don't have to specify a default prefix. If we did have a default prefix, say in our project and item templates I'll be creating, I would probably go with "prism".

from prism.

Why not use its actual new home at github.com/prismlibrary?

from prism.

Well, do we want to tie the name to a source control vendor? Even if we didn't own the actual domain name, http://prismlibrary.com/ would be specific to prism and not imply a method of source control. What happens when the next great source control solution CleanSource is released?

from prism.

I'm up for using the domain name as the new definition.

from prism.

Fair point, since we own the domain and since it would make intellisense selection quicker, I vote for http://prismlibrary.com

from prism.

Why not .net or .org, Prism is not commercial right?

from prism.

This has been complete. I left the XmlnsDefinition("http://www.codeplex.com/prism", "namespace") definition in there for backwards compatibility.

from prism.

Having a .com doesn't mean it's a commercial product. Lots of open source projects the use the .com domain alias (GitHub) since it is the most widely used and it's usually the first thing someone types when looking for a website.

from prism.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from prism.