Yup, doesn't work either. I think I found the answer and it's "You Can't."
Here is what I found
SYMPTOMS
When performing a full-text search on SQL Server character data, or when using a SQL distributed query with the Microsoft Index Server OLE DB provider (MSDIXS) and a prefix expansion search for a compound word that contains a hyphen (for example, "XYZ-A*"), the results produced may not be as expected.
Back to the top
CAUSE
A full-text search considers a word to be a string of characters without spaces or punctuation. The occurrence of a non-alphanumeric character can "break" a word during a search. Because the SQL Server full-text search is a word-based engine, punctuation generally is not considered and is ignored when searching the index. Therefore, a CONTAINS clause like 'CONTAINS(testing, "computer failure")' would match a row with the value, "The failure to find my computer would be expensive.".
Back to the top
WORKAROUND
To work around this problem, try the following: • Only use alphanumeric characters when using the SQL Server full-text index facilities.
-or-
• Where non-alphanumeric character must be used in the search critera (primarily the dash '-' character), use the Transact-SQL LIKE clause instead of the FULLTEXT or CONTAINS predicates.