Thanks for taking the time to explain. I have read and researched a lot into xaml, but as a company we have made a decision to go with the xml solution. Without going into too much detail, it is not easy to change once a process has been established and
I wonder, did you get a chance to look at the last link I pasted? (here it is just in case), Cathy Kong's answer (who apparently is a MSFT Moderator)
was to reinstall with the invitation to let her know any follow up issues. Well I did that but she didn't even have the courtesy of replying. Looking at a lot of her so-called replies, they all say that the software should be reinstalled and that they should
get back to her with any further queries that then she ignores.
Then again this seems to be the general attitude in MSFT, as soon as a question becomes difficult or complicated, it is ignored. A lot of these threads seem to end with someone from MSFT saying re-install and then not providing any real reasons or solutions.
Now there are two very real and separate issues here,
a) The original post: referring to opening a copy of DefaultTemplate.xaml - this was an out-of-the-box installation (on separate machines) and both installations were giving the same error.
b) No one had a reply/reason/solution for this. So fine I tried the xml route, even copy-pasted some source out of MSDN (see here) but the error mentioned here persists.
You see, the issue here isn't how I create a work item, the issue is why am I getting these errors? I don't even get as far as creating a work item, anything I override is ignored (see both of my xml snippets here).
Why would a default xaml template supplied with the software not work?
Why the system cannot find an assembly that is so obviously part of tfs? If I need to install additional software, why does no-one seem to know what it is?