Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

guid specified for parameter projectid must not be guid.empty #178

Closed
fromthewoods opened this issue Apr 14, 2017 · 6 comments
Closed

guid specified for parameter projectid must not be guid.empty #178

fromthewoods opened this issue Apr 14, 2017 · 6 comments
Labels

Comments

@fromthewoods
Copy link

fromthewoods commented Apr 14, 2017

Trying to use VScode instead of Visual Studio for my DevOps work since I'm mainly writing PowerShell. I have an existing folder inside a huge project shared by many people. I've configured
"tfvc.location": "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\TF.exe"
and I can connect to TFS but something still isn't working.

I can see my modified files in the Source Control panel once I switch SCM to TFVC, but the icons at the bottom of VScode aren't working.
image
When I click on the build icon, I get a popup window that says "Windows cannot find 'undefined/_build'. Make sure you typed the name correctly, and then try again."
image
when I click on the work item icon I get this message:
image
I'm sure my project needs to additional items, I'm just not sure what. Forgive me, I'm not a TFS/Visual Studio expert.

Windows 7
Visual Studio 2015 Update 3
TFS 2015 Update 3 (on prem)
VSCode 1.11.2

@jeffyoung
Copy link
Contributor

On first glance, I was thinking that perhaps TFS prior to 2015 U2 was being used (as those errors are usually symptomatic of an earlier version of TFS). With a bit closer inspection, it appears that we don't have the proper team project URL. Ignoring those errors for a minute, can you successfully edit your files and get the expected results in the TFVC viewlet?

Also, would you be willing to turn on logging and provide that information (you may want to remove some PII beforehand)?

@fromthewoods
Copy link
Author

I can see see files in the Source Viewlet.
image
Attached is the debug log.
team-extension.1.log.txt

@jeffyoung
Copy link
Contributor

Thanks for the screenshot and the log @fromthewoods. The log was really helpful.

It looks like you're running into #175 since we can't determine the team project from the output of the workfold command. That thread has some ideas about how we could address it (but it requires changes to the extension).

That said, can you describe your workspace mappings (how you typically work)? My expectation is that most folks would map at least one team project root (but I'm finding out a bit differently).

@fromthewoods
Copy link
Author

I'm no expert, but I believe I have one workspace and my "projects" are just folders under this huge shared workspace. Does that help?

@jeffyoung
Copy link
Contributor

Yes. That indicates that what you're seeing is the same as @175 (with the side-effect of what you're seeing in the status bar since we can't determine the team project).

@jeffyoung jeffyoung added the bug label Apr 22, 2017
jeffyoung pushed a commit that referenced this issue Apr 22, 2017
If the project is TFVC and we can't determine the team project, don't display the team project, build and work items status bar items (don't even initalize them).  Instead, set a message that the functionality is explicitly disabled.  #178
jeffyoung pushed a commit that referenced this issue Apr 23, 2017
If the project is TFVC and we can't determine the team project, don't display the team project, build and work items status bar items (don't even initalize them).  Instead, set a message that the functionality is explicitly disabled.  #178
@jeffyoung
Copy link
Contributor

Merged PR should prevent these errors from displaying (although a message to that effect will be displayed in the status bar). Other issues are tracked in #175.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants