SDK and Tools

How can we improve the Azure SDK and Tools?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Add F# documentation for Azure SDK

    Add documentation for the Azure services from F#, particularly documenting

    (a) how to use basic services like blob and table storage from the F# Interactive REPL, to allow F# scripting to be used to script Azure

    (b) showing how to develop and use F# type providers for Azure

    All the documentation should be cross-platform so that F# users on Mac, Linux and mobile can also learn how to use Azure services.

    The current documentation for C# is very difficult to follow for F# programmers since it depends on specific Visual Studio tooling.

    237 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      2 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
    • Azure SDK for .net core

      So, we released .net core 2 months ago. It's new, fast, cool, cloud ready and etc.

      But Cloud is not ready to .net core, because we have no .net core SDK!

      Please, refactor and publish .net core compatible version of sdk.

      18 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        1 comment  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
      • BUG: Can't access Azure Subscription via Visual Studio Server Explorer when using RBAC

        Our dev's access is configured via RBAC in Azure. Now they can't use Visual Studio Server Explorer to access the Azure Subscription.

        6 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
        • Support PS Cmdlets in Azure Web Apps

          Would be nice to run PowerShell Cmdlets in Azure Web Apps

          3 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
          • Unable to mock MessageSizeExceededException, et al. due to sealed/internal constructors

            Many of the .Net Standard (Microsoft.Azure.EventHubs namespace) classes, particularly exceptions, are sealed with internal constructors making unit testing of our error and retry handling impossible or very difficult using hacky workarounds. There should be a way to replicate these exceptions.

            1 vote
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
            • BugFix: ARM Deployment project deployment.targets sets ArtifactStagingDirectory to null

              There seems to be a minor bug in the Deployment.targets file in Azure Resource Group deployment projects (VS 2015 in my case). When we upgraded our TFS servers to TFS 2015, the staging folders created during the builds disappeared from the drop folder. When we looked for them, we found they were getting copied to the root of the C: drive on the build agents.

              The bug is in the _CalculateArtifactStagingDirectory target in the deployment.targets file (line 89 in my case).

              This line:
              <artifactstagingdirectory condition=" '$(TF_Build)' == 'True' ">$(Build_StagingDirectory)</artifactstagingdirectory>

              Should read:
              <artifactstagingdirectory condition=" '$(Build_StagingDirectory)' != '' AND '$(TF_Build)' == 'True'…

              1 vote
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                1 comment  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
              • Docker support is greyd out for my web service

                Docker support is grayed out when I right click my web service. What is the problem and what do I need to do to get docker support?

                1 vote
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
                • Don't see your idea?

                SDK and Tools

                Feedback and Knowledge Base