Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (10)

Resolved TFS - Working With PB

  1. Advice
0
Votes
Undo
  1. John Valentin
    John Valentin
  2. PowerBuilder
  3. Monday, 16 September 2024 12:44 PM UTC

So I have a new laptop. It seems that Visual Explorer 2013 couldn't be installed so we have a purchased Visual Studio 2013. We do have a licesnse for it but when I try to register it, I get an invalid key. I believe Microsoft will not support this anymore. I installed Visual Studio Explorer 2017 to check in/out non-PB files (works fine) However, I cannot compare the differences in my PB file that checked out from withing PowerBuilder (it tries to start Visual Studio 2013 which will not run). Does anyone know a workaround for this?

  1. PowerBuilder (Appeon)
  2. TFS
New improvement for the PDFDocument object
NSSM parameter to invoke PB application as service...
Responses (10)
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 18 September 2024 13:44 PM UTC
  2. PowerBuilder
  3. # 1

Sorry for the delay.

Here's the setup that we use: https://drive.google.com/drive/folders/1E-i-pNWQ5ybGjyif8yPiNO08SgFVJV14?usp=sharing

I'd follow Nasir's advice to first uninstall your VS 2013, to see if things work.

Before doing a compare, open the VS Explorer.

VS 2017 won't work.

regards.

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 17 September 2024 17:23 PM UTC
  2. PowerBuilder
  3. # 2

Could it be that you have the VS 2013 (licensed) installed on more than one machine? I'm not sure if that could be the problem.

Later I'll post a link to what we use on my Google Drive. We use the Express version.

Comment
There are no comments made yet.
Nasir Ahmad
Nasir Ahmad Accepted Answer Pending Moderation
  1. Tuesday, 17 September 2024 15:27 PM UTC
  2. PowerBuilder
  3. # 3

 

VS studio 2013 is just required for installation and not to be used for the TFS tasks. Make VS studio 2017 the default.

 

Open VS studio 2017, go to Team and configure your TFS connection there. Hopefully it will solve your issue. 

Comment
John Valentin
  1. John Valentin
  2. Tuesday, 17 September 2024 15:48 PM UTC
Thank you Nasir but that's not the problem.



TFS Works fine.

I can check items in and out, no problem.

The problem is the using Show Differences when right clicking on a checked out item brings up Visual Studio 2013 (which will not let me continue because it has a trial license and you cannot register it because Microsoft took down the registration verification). I'd like it to bring up Visual Studio 2017 Explorer when I select Show Differnces from the popup menu.



  1. Helpful
Nasir Ahmad
  1. Nasir Ahmad
  2. Tuesday, 17 September 2024 16:08 PM UTC


Thank you for the explanation John.

After having a look at my environment it looks like there is just VS 2013 shell installed and not the complete VS 2013. It says Microsoft Team Explorer for Visual Studio 2013 and that does not require login to work.

Maybe try to uninstall VS 2013 complete and just install the VS 2013 Team explorer.

Hope it helps.
  1. Helpful
John Valentin
  1. John Valentin
  2. Tuesday, 17 September 2024 17:27 PM UTC
Thanks you Nasir but you can no longer install Team Explorer 2013. The files that this pulls from the internet (Microsoft's files) have been taken down. I don't know exactly when this happened, but it happened. THat's what stinks....
  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 17 September 2024 14:03 PM UTC
  2. PowerBuilder
  3. # 4

The TFS repository server can use native TFS or GIT for the data store. If it is using GIT, you can use the built in GIT support from the PB IDE. If you are using native TFS, you should be able to do a conversion.

Comment
John Valentin
  1. John Valentin
  2. Tuesday, 17 September 2024 14:13 PM UTC
Thank you Roland but we're not doing a conversion. I want to know how either how I can trick PowerBuilder to user the Visual Studio 2017 Source Code Explorer app instead of calling Visual Studio 2013 or trick Visual Studio 2013 into thinking I have a registered copy (we have the software and license but Microsoft's online services for verification are gone, so Visual Studio 2013 thinks it's a trial version and won't continue after 30 days unless it's registered, which I cannot do because the Microsoft services no longer seem to be available).
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 16 September 2024 13:05 PM UTC
  2. PowerBuilder
  3. # 5

Have you tried all of the options?

Sign in.

Check for an updated license.

etc.

 Maybe this is more of a question to ask to Microsoft.

Comment
John Valentin
  1. John Valentin
  2. Monday, 16 September 2024 16:39 PM UTC
I've tried all options.



Visual Studio 2013 is no longer supported....
  1. Helpful
There are no comments made yet.
John Valentin
John Valentin Accepted Answer Pending Moderation
  1. Monday, 16 September 2024 13:05 PM UTC
  2. PowerBuilder
  3. # 6

 

We do have a valid license!

Comment
There are no comments made yet.
John Valentin
John Valentin Accepted Answer Pending Moderation
  1. Monday, 16 September 2024 13:02 PM UTC
  2. PowerBuilder
  3. # 7

when attempting to sign in.

 

Comment
There are no comments made yet.
John Valentin
John Valentin Accepted Answer Pending Moderation
  1. Monday, 16 September 2024 13:01 PM UTC
  2. PowerBuilder
  3. # 8

Comment
There are no comments made yet.
John Valentin
John Valentin Accepted Answer Pending Moderation
  1. Monday, 16 September 2024 13:00 PM UTC
  2. PowerBuilder
  3. # 9

I'll better explain my situation. I do have Visual Studio 2013 installed with the MSCCI driver. I am able to check items in and out of TFS without issue, even though I cannot run Visual Studio 2013. (It runs but asks me for a license, which we have but cannot be verified; I believe the online verifier for the VS 2013 has been taken down/is no longer in service).

The issue is with right clicking on a checked out object in PB and select "Compare differences". This attempts to start Visual Studio 2013 with the diff tool displayed. It does open up and appear but then the licensing window opens up and asks me for a valid license. (Any attempt to sign into Visual Studio or enter the valid license key is met with the error "The online service is not available" or "Invalid license key" and we do have a valid license key). Is there a way to trick PB to use Visual Studio 2015 to compare differences?

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 16 September 2024 13:03 PM UTC
I'm not sure what we are using. Most likely some "community" version. That should take out the licensing question. When I have some time I'll look it up.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 16 September 2024 12:53 PM UTC
  2. PowerBuilder
  3. # 10

Hi,

"It seems that Visual Explorer 2013 couldn't be installed". Give a bit more explanation here please. Have you tried the 2015 version?

Do you have the MSSCC (or whatever it's called) installed?

Try to open the Visual Studio before you try to do a diff from within powerbuilder. Many times it's the only way I can do a compare.

regards.

Comment
John Valentin
  1. John Valentin
  2. Monday, 16 September 2024 13:23 PM UTC
I have not tried the 2015 version.



MSSCC is installed.
  1. Helpful
John Valentin
  1. John Valentin
  2. Monday, 16 September 2024 13:31 PM UTC
Visual 2013 IS installed. It just thinks it's a trial version and is asking me to register it, which always fails.
  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.