Microsoft Dexterity does not check in resources "all the way" into source control repository

Just recently, we migrated to Visual Studio Team Services from Visual SourceSafe and Team Foundation Server. Our migration went very smooth, with only a couple issues to report -- you can read more about these in the 2-part series here and here.

During our testing phase, prior to the migration, we ran into an issue where resources were being checked out of the VSTS repository, but did not seem to check back into the repository all the way, requiring the developer to go to Visual Studio Source Control Explorer to complete the check in. We attributed this to a simple environmental issue as the developer also had been having other issues with his machine in general. He had already committed to reformat his machine so no further thought went into this. Also, it is probably a good time to mention that no one else was experiencing this problem so off we went into the sunset.

Fast forward a couple weeks. After completing the migration and back working on our daily development activities, the same developer reported having the same issue once more, this is, he would check out a resource from the repository, make changes to that resource, and check the resource back into the repository. However, the resource would not check all the way in, requiring to complete the check in with Visual Studio.

The next immediate step was to compare the source control settings between a working and the non-working environment. A working environment had the following settings:


Dexterity Source Control Options

Root Directory: C:\Projects\Features\Deadbolt\
Project Name: ABCD

The non-working environment had the following settings:

Dexterity Source Control Options

Root Directory: C:\Projects\Features\
Project Name: Deadbolt\ABCD

In comparing the two, it was obvious the project name in the non-working environment was preceded by the folder on the disk where the project could be located. Dexterity never barked at this during the setup, so our developer assumed it was Ok to leave it as shown above. Since resources were checking out fine and he could work, he never thought much of the setting.

Once his settings were changed to match that of all working environments, things were good again - check-in worked as expected!

In retrospect, the Apply button should validate these settings, so we will attribute this to a bug in Dexterity. Perhaps is non-consequential, but certainly a headache if you are in a pinch.

Until next post!

MG.-
Mariano Gomez, MVP

Comments

Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics
Read more

Cannot insert the value NULL into column 'CONTACT' error when clicking on Items List in Navigation Pane

Image
Moving on from my previous article on a similar subject - see Cannot insert the value NULL into column 'BASEUOFM' error when clicking on Items List in Navigation Pane , I recently came across this error,  Cannot insert the value NULL into column 'CONTACT' when clicking on the All Purchasing Transactions list under the Purchasing Navigation Pane option, after performing an upgrade from Microsoft Dynamics GP 9.0 to Microsoft Dynamics GP 2010 R2. All Purchasing Transactions list error - Purchasing Navigation List The name of the global temp table - in this case, tempdb.dbo.##2093338- varies in almost all cases, but the end result of the error is the same. The issue has been identified running Microsoft Dynamics GP 2010 RTM, SP1 or SP2. Upon further review, the issue is due to bad data in the Vendor ID (VENDORID) column in the Purchasing Receipt History table (POP30300). In summary, if you have a purchasing receipt with a blank vendor ID or a vendor ID that doe
Read more

How to uninstall Microsoft Dynamics GP 10.0 if you cannot uninstall it by using the "Add or Remove Programs" feature

INTRODUCTION This article describes how to uninstall an existing Microsoft Dynamics GP v10 system if you cannot uninstall it by using the Add or Remove Programs feature (or Programs and Features in Windows Vista) in Control Panel. It is recommended that you verify that you cannot uninstall by using Add or Remove Programs first. MORE INFORMATION First, verify that you cannot uninstall Microsoft Dynamics GP by using Add or Remove Programs (or Programs and Features) To verify that you cannot uninstall Microsoft Dynamics GP by using Add or Remove Programs (or Programs and Features in Windows Vista), follow these steps. For Windows XP or Windows Server 2003: 1. Click Start, click Run, type control appwiz.cpl in the Open box, and then press ENTER. 2. Click to select Microsoft Dynamics GP 10.0 product from the application list, and then click Remove. For Windows Vista: 1. Click Start, type Programs and Features in the Search box, and then press ENTER. 2. Click to select the product to be un
Read more