locked
Azure Batch 6.0.0 SDK RRS feed

  • Question

  • In Microsoft Azure Batch 6.0.0 I just downloaded from NuGet, I do not see Azure.Batch.FileStaging.SequentialFileStagingArtifact class. Is it missing or something was changed?

    https://www.nuget.org/packages/Azure.Batch

    Monday, February 27, 2017 5:59 PM

All replies

  • Hi Risheng,

    That class was moved to the Microsoft.Azure.Batch.FileStaging nuget package, to more clearly separate the storage helpers from the Azure.Batch core functionality. It had the additional benefit of removing the storage dependency entirely from the Azure.Batch package by itself.

    You should be able pull down https://www.nuget.org/packages/Azure.Batch.FileStaging/ and everything should compile.

    Let us know if you have any trouble with that.

    Thanks,

    -Matt

    • Proposed as answer by DarylMsft Friday, March 3, 2017 9:53 PM
    Monday, February 27, 2017 6:19 PM
  • Thanks Matt.  That works.

    Another question:

    In 6.0.0, Microsoft.Azure.Batch.StartTask class does not contain the property 'RunElevated'? It used to be something like:

                    StartTask startTask = new StartTask
                    {
                        CommandLine = ...,
                        RunElevated = true,
                        WaitForSuccess = true
                    };

    Now it throws compilation error:

    Error CS0117 'StartTask' does not contain a definition for 'RunElevated'.

    ---

    Another change is the new SubTaskState, it used to be:

    subtask.State == TaskState.Completed

    now:

    subtask.State == SubtaskState.Completed



    Monday, February 27, 2017 6:52 PM
  • The user security context for tasks has become richer and the RunElevated is now part of the UserIdentity.

    From the changelog:  https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/src/Batch/Client/changelog.md

    To translate existing code, change RunElevated = true to UserIdentity = new UserIdentity(new AutoUserSpecification(elevationLevel: ElevationLevel.Admin))

    The enum change seems to be around the set of viable states not being exactly identical (ie: active or not).

    d

    Monday, February 27, 2017 7:25 PM
  • It is working now. Thanks Daryl for the prompt reply and the info.
    Monday, February 27, 2017 8:53 PM