Skip to content

Azure DevOps/TFS - Handling Cache/IRIS routines with .mac file extension #134

@PaulSiml

Description

@PaulSiml

TFS 2015 treats the .mac file extension as an image file. Therefore it will not allow us to perform a code comparison on the Pull Request because if considers .mac files as images. We have found no way to alter the handling of the file extension in TFS. We are attempting to get some more information from Microsoft without success.

We suspect this is a "feature" of TFS 2015 since all other file extensions work correctly. This is where the ObjectScript extension may be able to help us. If we could have a setting in the ObjectScript extension that would allow us to use a different extension for .mac files – perhaps .tmac – this would fix the issue for us. ObjectScript would see this replacement extension .tmac and ,on the push to Cache/IRIS, convert it to a .mac extension. In this manner we would just store our Cache code in TFS (Git) with the .tmac extension. When we build an area we could flip the extension back to the normal .mac extension.

Metadata

Metadata

Assignees

No one assigned

    Labels

    reviewrequires discussionupstreamDepends on an upstream change (e.g. VS Code fix or enhancement, IRIS change)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions