Ignora esplorazione

Supporto della community per Azure

Poni domande, ottieni risposte ed entra in contatto con i tecnici Microsoft e gli esperti della community di Azure

Forum MSDN

Risposta di Microsoft alle domande tecniche su Azure

  1. Più recenti
  2. Popolari
  3. Tendenze
Serverfault

Risposte della community alle domande sull'amministrazione di Sys/Net

  1. Più recenti
  2. Popolari
  3. Tendenze
Commenti e suggerimenti per Azure

Hai un'idea o un suggerimento basato sulla tua esperienza con Azure?

  1. Più recenti
  2. Popolari
  3. Tendenze

Vegas Towing Service

URL: http://www.vegastowingservice.com/henderson-towing-nv.html Keywords or tags: tow truck near me, towing service henderson, emergency roadside assistance in henderson nv, flat tire service henderson nv Description: Towing people and their cars around Henderson Nevada is what we do and we are constantly looking for ways to improve our team members through extensive, customer relations focused training. We encourage all team members to participate in continued education and self-development activities. Now for the cool stuff. Our trucks are outfitted with the latest and greatest GPS technology. We can give you very accurate estimated time of arrival (ETA) for our tow truck services. Owner Name: jason Full Address: 1550 W Horizon Ridge Pkwy R unit 3 #541 Henderson, NV 89012 Phone: (702) 848-6343 Business Email: vegastowingservice@gmail.com Year Found: 2016 Number of Employee: 6 Operating Hours:

Application Insights - support for multiple environments

It would be good if I didn't have to set up application insights for each of my environments, like local, dev, test, staging, production. I want all my telemetry for my application to go into one container, and I want Application Insights to be aware of the different environments so I can quickly filter between them when using the Portal. This could be extended down to Visual Studio, where I can already see my debug telemetry separately from production, but actually, this feature will give the developer even more control and insight into application code, as it passes through the different stages of the release cycle.

Option to refresh upon closing context blade

Context blades (the skinny fly-in blade from the right) are being used more and more in designs, especially as Azure continues to transition to a fullscreen experience. One common use case is provide an intermediate UI that helps a user to perform small actions (e.g. simple add, create, edit). In these cases the user may hit a button like "Save" on the context pane which kicks off stuff on the back end and closes the context pane. However, there is no feedback on the main blade UI about the action that was performed, unless there is a notification (not applicable to all cases) or the user manually refreshes the page. It would be great if there was an option to refresh the original blade when the context blade is dismissed, so that the user can get more immediate feedback about the status of the system. Example: A settings type page - the user clicks on a link to edit a particular setting. The context pane flies in and the user makes the change, and hits save. Ideally the page they return to will refresh to have the most current information displayed to show the user that yes, the edit you just made was indeed successfully saved.

Stretch DB

MS should build these idea's into the Azure Stretch DB Product.

Non hai trovato quello che ti serve? Invia un tweet

Tweet us @AzureSupport

Aiutaci a migliorare. Questa pagina è utile?

Limite di 160 caratteri