Reputation: 5476
If I use the TFS process editor from within Visual Studio 2017: Menu: Tools->Process Editor->Work Item Types->Open WIT from Server. I get the error "the given path's format is not supported".
I can use witadmin to export to and xml file, but the import does not give an error and appears to work - but does not as the changes do not appear within the TFS workitems.
What is the path format that it is referring to and how can I correct it?
Upvotes: 0
Views: 1131
Reputation: 1
In our case ssl was not used for configuration, I faced the same problem.
Update of VS etc, didn't work, I have not reinstalled the feature.
Resolution in my case: TFS 2018 is configured to use public URL (not fqdn of vm). Adding TFS by public url faced the problem. Using an additional hosts entry for public IP + internal VM Name solved the problem in my case.
Upvotes: 0
Reputation: 5476
I found the cause. This is a bug when you try to use process editor with SSL. When I use it over http it works fine. [Using VS 2017 & TFS2017]
Upvotes: 0
Reputation: 4129
Do you see .wit
files sitting beside the XML versions of the work items on the file system? Those would get generated if you opened the WITs in the old versions of TFS Power Tools and need to be deleted so the new editor can generate them again. This used to happen switched between version of Visual Studio/Power Tools before the new Extension was released.
Upvotes: 0
Reputation: 30362
Please try below items to narrow down the issue:
Tools > Extensions And Updates
select the extension to uninstall.%USERPROFILE%\AppData\Local\Microsoft\VisualStudio\15.0\ComponentModelCache
If that still not work, just try to reset the user data, then try it again:
cd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE
devenv.exe /resetuserdata
Upvotes: 1