SDK and Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  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.

    243 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  3. Improve error reporting when hitting the Azure API limit

    We have been working with Microsoft Support to identify an issue where we were intermittently encountering exception "A task was canceled" when calling the list methods from Microsoft.Azure.Management.Compute.SnapshotsOperationsExtensions.

    We narrowed this down to the Azure API limit being reached, which from our understanding is a maximum of 240 request / 3 minutes.

    It appears that currently the only way to confirm that this is the issue is to check "x-ms-ratelimit-remaining-resource" in the header details.

    It would be good if the Azure .NET SDK could report an exception that indicates the API limit has been exceeded, rather than "A task has…

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  5. Support PS Cmdlets in Azure Web Apps

    Would be nice to run PowerShell Cmdlets in Azure Web Apps

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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=" '$(TFBuild)' == 'True' ">$(BuildStagingDirectory)</artifactstagingdirectory>

    Should read:
    <artifactstagingdirectory condition=" '$(BuildStagingDirectory)' != '' AND

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  8. Need

    Need the following implementation to be present in the IDocumentClient interface for easier compliance of SOLID principles and not having to use dynamic to read the result. Currently it is present only in the concrete class and it is a bad practice to inject concrete dependencies into my repository class.

    public Task<DocumentResponse<T>> ReadDocumentAsync<T>(string documentLink, RequestOptions options = null)

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  9. Sharepoint Connector for .Net Core

    Currenlty we are not able to connect sharepoint online site through .NET core based WebAPI/ASP.NET web application. This would help to do administrative operations using web api developed using .NET core and hosted in Azure.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  10. 'ExceptionTelemetry.HandledAt' is obsolete

    it would be nice to have an example on how to change this.

    when I compile some code that is using ExceptionTelementry.HandledAt I get the following compiler warning:

    'ExceptionTelemetry.HandledAt' is obsolete: 'Use custom properties to report exception handling layer'

    but I haven't found any examples for using "custom properties to report exception handling"

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  12. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  13. We need .Net RTC

    We need .net RTC for P2P realtime. WebRTC is not documented well, their TURN servers are horrible and don't integrate with business easily, and can't scale easily. WebRTC itself is bad Javascript tightly coupled to browser camera while it should take streams from independent resources. The .net RTC with supporting could relay services (TURN) will do good for both Azure and us.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    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

Categories

Feedback and Knowledge Base