• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • PB 2017 R3 with TFS 2015 on Windows 10 Enterpise : checkin objects not found

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
You need to be logged in to view a user's profile.
View Replies (1)

Resolved PB 2017 R3 with TFS 2015 on Windows 10 Enterpise : checkin objects not found

  1. Issue
0
Votes
Undo
  1. Samir Kothari
    Samir Kothari
  2. PowerBuilder
  3. Monday, 11 November 2019 18:28 PM UTC

Hi All, 

Anybody no how to connect with TFS 2015. This is what I'm working with:PowerBuilder 2017 R3 with Visual Studio 2019 on Windows 10 Enterprise. All powebuilder objects already in TFS for my application.

As per the tutorial, I did install team explorer 2013 and msscci Provider 32 bit. ( https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/195-using-powerbuilder-2017-with-tfs-source-control )

When I opened PowerBuilder and connected to my TFS project, I get the message 'Source control is ready.', however when I select libraries (pbl's), and view the objects I still see the plus ( + ) symbol beside each object as opposed to the dot.

Any help appreciated

thanks

Samir

 

 

 

Populate Fields (not Bookmarks) in a WORD OLE
Data types in Pipeline between SAny 11 & PostgreSQ...
Responses (1)
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Monday, 11 November 2019 18:55 PM UTC
  2. PowerBuilder
  3. # 1

I wonder if your objects are in different relative folder compared to the  workspace file?

A I remember PB recognizes each PB source object based on its relative path to the .PBW file.

Comment
Samir Kothari
  1. Samir Kothari
  2. Monday, 11 November 2019 20:18 PM UTC
Thanks for the tip! This was exactly it.



All is good now.

  1. Helpful
Michael Kramer
  1. Michael Kramer
  2. Monday, 11 November 2019 20:28 PM UTC
Happy to help :-)
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.