Comments
Sort by recent activity
Thanks for helping...
• What current version of DLM Automation itself are you using?
2.0.12.371
• Which version of TFS are you using?
14.102.25423.0 (we're planning on upgrading to TFS 2017 update 1 – 15.112.26307.0 soon)
• Which TFS plugin are you using? The new VSTS-style plugin or the older TFS Build plugin with the XAML builds?
New VSTS
• If you are using VSTS, are you using a hosted build server on an on-premise build server?
On premise / comments
Thanks for helping...
• What current version of DLM Automation itself are you using?
2.0.12.371
• Which version of TFS are you using?
14.102.25423.0 (we're planning on upgrading to TFS 2017 update ...
I'll see if we can get the DLM Automation upgraded.
Yes, the filter was created using SQL source control.
Yes, the Filter.spcf is in the db\state folder in the NuGet package, and it looks as it should for the User and Role entries
<User version="1">
<Include>True</Include>
<Expression />
</User>
<Role version="1">
<Include>True</Include>
<Expression />
</Role> / comments
I'll see if we can get the DLM Automation upgraded.
Yes, the filter was created using SQL source control.
Yes, the Filter.spcf is in the db\state folder in the NuGet package, and it looks as it sho...
I think creating this PowerShell script, and passing it the correct parameters (many applications, and multiple environments) would be more complicated and be harder to maintain than simply putting the filter file location in the "Filter path" as we are now.
I really just want to know why it's not using the Filter.scpf file in the Nuget package.
If we set the "Filter path" we see this when we build:
"filter file
'C:\vNextBuildAgent\_work\36\s\[application name]\Dev\Database\Filter.scpf'
specified by the FilterPath parameter is overriding the filter in scripts folder
'C:\vNextBuildAgent\_work\36\s\[application name]\Dev\Database'
in the source."
As you can see, the file it says it's overriding is the same as the one that it's using to override (from the "Filter path"). This works correctly. However if we omit the "Filter path" it doesn't work correctly (drops the users and roles) / comments
I think creating this PowerShell script, and passing it the correct parameters (many applications, and multiple environments) would be more complicated and be harder to maintain than simply putting...
Thanks for the feedback. Hopefully someone from the dev team will be able to answer. / comments
Thanks for the feedback. Hopefully someone from the dev team will be able to answer.