Please make Snapshots available to non-Enterprise versions of Visual Studio.3 votes
When you debug against multiple processes, ApplicationInsights picks a random one to show in the window and shows a yellow dialog "Multiple processes have been debugged. This window only shows data for XXXX"
Allow the user to select which process the chart displays for. don't need history just the ability to change the chart from the selection point onwards3 votes
The option to show the live Telemetry Data from the current or last debug session in Visual Studio is currently explicitly restricted so that it only works for ASP.NET project types with direct AI configuration.
It should be made possible to manually enable this VS integration feature for any Visual Studio solution or startable project type that is known to emit AI telemetry events.3 votes
It's great you can log a work item in Azure Dev Ops from App Insights but would be even better if you could link the bug to the error.2 votes
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature
I am new at Azure with VS (I am still using VS2015). I cannot seem to execute my data factory locally. In order to test I still have to publish to the cloud? If I am correct that this is a missing feature then it would be very useful to be able to run locally. Thanks.2 votes
I usually have multiple publish profiles defined for my projects. It would be great if at minimum the profile name was added as a property of the Release Annotation. But, it would be even better if the were an element I could add to the pubxml file to set various properties add perhaps even specify an ITelemetryInitializer that can add others or extract Assembly properties generated during build.2 votes
Use the PerformanceHat plug-in from Eclipse as inspiration, as well as Adrian Colyer's blog post discussing it2 votes
Exception stack trace deep links in log entries to open solution & focus on referenced lines of code
While logging exception stack traces with line numbers (for debug builds), include deep links to each of the referenced lines of code. The deep link should open Visual Studio (or VS Code), open the appropriate solution, open the file containing the referenced line, and set focus to that line. Display the exception stack trace where appropriate in VS.
These links should appear in Live Metrics, in the Sample Telemetry panel.1 vote
Thanks for your feedback and its now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
Make upgrades of the Nuget packages for AI in Visual Studio non destructive to the current configuration
Today, when you upgrade AI in VS, the new packages completely over writes whatever config you currently have.
Make the upgrade smother and provide a GUI for configuring AI in Visual Studio1 vote
Increase the number of exceptions that appear in the VS Code Lens. Limiting to the top 15 exceptions is too small for large code bases.
Increase the number of exceptions that appear in the VS Code Lens. Limiting to the top 15 exceptions is too small for large code bases. Perhaps top 100 exceptions or more would be much better.1 vote
- Don't see your idea?