Niggles v16 (Docs) + Bugs #2358
Conversation
MrHinsh
commented
Sep 12, 2024
•
MrHinsh
commented
- Update links to "install" in Getting Started
- Update the permissions page to be more consistent and readable on permissions.
- Fix for ProcessDefinitionProcessorOptions: Source and Target need to be defined independently for parallel processing to work #2361 reported by @fgudelj1 in ProcessDefinitionProcessorOptions Source and Target #2360
…sions documentation The links to the installation and permissions documentation are updated to use absolute paths. This ensures that the links work correctly regardless of the current document's location, improving the user experience and reducing potential navigation errors.
nkdagility-actions-bot
bot
added
documentation
Corrects typos and clarifies the minimum permission requirements for source and target systems. Adds details about the use of the "Bypass Work Item rules engine" flag and the necessity of full-scoped PATs. Provides instructions for granting "Make requests on behalf of others" permission on older TFS versions. Improves clarity and accuracy of the documentation, ensuring users understand the necessary permissions and configurations for successful migrations.
Improve the readability and clarity of the permissions documentation. Ensure consistent terminology and formatting. Highlight the importance of full-scoped PATs and provide clearer instructions for setting permissions, especially for older TFS versions. This enhances user understanding and reduces potential confusion during setup.
…h and commit details ♻️ (EndpointRegistrationExtensions): set endpoint name during options instance creation ✨ (IEndpointOptions): add Name property to IEndpointOptions interface The documentation is updated to reflect the latest branch, commit, and version details, ensuring accuracy. The code is refactored to set the endpoint name during the creation of the options instance, improving clarity and maintainability. Additionally, a new `Name` property is added to the `IEndpointOptions` interface to support this change.
|
HI all, when we tried to run 16.0.3 we have experienced the following error - 16.0.2. works as expected : Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'file:///C:\Tools\MigrationTools\MigrationTools.Clients.TfsObjectModel.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515) ---> System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.GetResult() at VstsSyncMigrator.ConsoleApp.Program.(String[] args) |
