The Welkin Suite Forum

Switch branch doesn't update Solution Explorer



Switch branch doesn't update Solution Explorer

  • Please log in to reply

#1

marco.pietersen.maandag

    Posted 31 Aug 2016

    Hello, 


    We're currently evaluating TWS for use within our organisation. 

    I'm trying to integrate with Git. The basic functionality exists in TWS, but the main issue I see is that when I switch branch the solution explorer file list doesn't update. 

    I believe its fairly new functionality, so it looks like it's not fully implemented. 

    On the short term I believe the best option would be a refresh option on project level to refresh the list with the local files. This would also make it easier to allow the usage of external source control tools like SourceTree (as I find it's gui better to work with from source control point of view). 

    Other issue's when using source control:

    - switching branch is slow and stops the GUI. It could use a spinner perhaps?

    - Switching branch when there are file changes throws error. This is not always necessary. 


    At the moment TWS is not usable for us, but I'd like to be proven wrong. 



    3 replies to this topic

    #2

    kate.dulko

      Posted 31 Aug 2016

      Hi Marco,


      Thank you for your post with the detailed information.


      The reason for your issue when the Solution Explorer file list isn't updated is the *.sfproj file inside the branches.

      This file is the same in both branches or this is missed in one of your branches.

      This file contains the list of all the files in your project and affects the updated of the list in the Solution Explorer.


      As a workaround, you follow the next steps:

      • you can check which your branch doesn't include this file or which of the *.sfproj files includes the wrong list of files;
      • after this please create a TWS project with the necessary file list;
      • please open the project folder of the newly created project and copy the *.sfproj file;
      • commit this file to the necessary branch.

      Please let us know if this workaround is acceptable for you.


      As for the other issues that you have mentioned:

      • I've added this issue to our Backlog, and our developers will solve this;
      • the error appears if you didn't save your changes before switching branches; you should save them or revert; this helps to avoid losing of your changes.

      If you have any additional question, please write us. We will be glad to help you.


      Regards,

      Kate


      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina
      e-mail: kate.dulko@welkinsuite.com

       

        


      #3

      marco.pietersen.maandag

        Posted 02 Sep 2016

        Hello, 

        Thank you for your response. Unfortunately it doesn't really help. 

        Your suggestion to put the project file under source control isn't realistic because it contains local settings, most notably the user's login details. This makes the project file unsuitable for sharing (you could work around this by adding user specific configurations, but that's a dead end street). 

        So I do think you need to look at a more elegant way to incorporate git in general. 


        I still like the tool and am looking forward to see how you combine the Git and Ant tools together. I was involved in creating tooling for my company and it's not an easy thing to do. 

        In the mean time I'll follow the progress in the Git integration. 


        Thanks



        #4

        kate.dulko

          Posted 02 Sep 2016

          Hi Marco,


          Thank you for your feedback.


          We are going to implement the Credentials Manager in The Welkin Suite in the future. The credentials will not be saved inside the project file and this will help to handle such cases.


          Currently, mechanism of changing branches inside TWS requires the presence of an *.sfproj file to refresh the list of files in the Solution Explorer.

          You can recreate your project using the OAuth authentication. In this case, your project file won't store your credentials and you will be able to share this via Git. To save your Git history you can the next way: 

          • when you create a new project please select the same list of metadata that your previous project includes;
          • please open the project folder of the previous project and copy the 'git' folder;
          • paste this folder to the project folder of the newly created project.

          Please let us know if using the OAuth authentication during a project creation will help to solve your issue.


          Thank you,

          Kate




          We are going to implement the Credentials Manager in The Welkin Suite in the future. The credentials will not be saved inside the project file and this will help to handle such cases.


          Kate Dulko
          Customer Relations

          The Welkin Suite

          twitter: @KateDulko
          skype id: d_katerina
          e-mail: kate.dulko@welkinsuite.com

           

            





          Boost Your Productivity. Get Started Today

          Try Free Trial