You are a Dynamics 365 Finance developer.
You make changes to an existing custom class.
The code comparison tool shows version conflicts between your version and the latest checked-in version of the custom class.
In Visual Studio, you open the Source Control Explorer.
You locate the latest changeset for the class and you open the changeset in Team Explorer.
You need to compare the latest code that is in source control with the code that you created.
Which option should you use?
Click on the arrows to vote for the correct answer
A. B. C. D.D.
https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/compare-files?view=azure-devopsWhen making changes to an existing custom class in Dynamics 365 Finance, it is important to ensure that the changes do not conflict with the latest checked-in version of the custom class. In this scenario, the code comparison tool is showing version conflicts between the developer's version and the latest checked-in version of the custom class.
To compare the latest code that is in source control with the code that the developer created, the developer needs to open the changeset in Team Explorer. Team Explorer is a tool in Visual Studio that allows developers to manage their source control repositories, including checking in and checking out code, comparing code versions, and viewing the history of changes.
Once the developer has located the latest changeset for the class and opened it in Team Explorer, there are several options available for comparing the code versions:
A. Compare with Workspace Version: This option allows the developer to compare the code in the changeset with the version of the code that is currently in their workspace. This is useful if the developer has made changes to the code since the last check-in and wants to see how those changes compare to the latest checked-in version.
B. Compare with Previous Version: This option allows the developer to compare the code in the changeset with the version of the code that was checked in immediately before the changeset. This is useful if the developer wants to see what changes were made in the latest check-in compared to the previous check-in.
C. View History: This option allows the developer to view the history of changes to the file, including all previous versions and who made the changes. This is useful if the developer wants to see a complete history of changes to the file.
D. Compare with Latest Version: This option allows the developer to compare the code in the changeset with the latest checked-in version of the file. This is the option that the developer should choose in this scenario, as it will show the differences between the latest checked-in version of the file and the changes that the developer has made.
In summary, when comparing the latest code that is in source control with the code that a developer created in Dynamics 365 Finance, the developer should open the changeset in Team Explorer and choose the option to compare with the latest version.