The initialization process creates a database in LocalDB and reserves HTTP ports for each local storage service. The first time you run the Storage Emulator, the local storage environment is initialized for you. To bring up the Storage Emulator console window again, follow the preceding steps as if starting the Storage Emulator. When you close the Storage Emulator Command Prompt window, the Storage Emulator will continue to run.
#USE WINE EMULATOR FOR .EXE WINDOWS#
When the emulator is running, you'll see an icon in the Windows taskbar notification area. The Azure Storage Emulator may not start correctly if another storage emulator, such as Azurite, is running on the system. For more information, see the Storage Emulator command-line tool reference section later in this article. You can also clear data, get status, and initialize the emulator from the command prompt. You can use this console window to start and stop the Storage Emulator. When the Storage Emulator starts, a Command Prompt window will appear.
:max_bytes(150000):strip_icc()/wined-9dfd242d9fd44c54b6c270a07af5372d.jpg "use wine emulator for .exe")
Some differences in functionality exist between the Storage Emulator and Azure storage services. The Storage Emulator connects to SQL Server or LocalDB using Windows authentication. See the Start and initialize the Storage Emulator section later in this article to learn more. You can choose to configure the Storage Emulator to access a local instance of SQL Server instead of the LocalDB instance. The Storage Emulator uses a local Microsoft SQL Server 2012 Express LocalDB instance to emulate Azure storage services.
:max_bytes(150000):strip_icc()/wineh-45187d75d4064c458603038e7494418e.jpg "use wine emulator for .exe")
However, any version of OData supported by the storage service may be used to send requests to the emulator. Replacing the OData DLLs used by the Storage Emulator with other versions is unsupported, and may cause unexpected behavior. The Storage Emulator depends on specific versions of the OData libraries. If you need to persist your data for the long term, we recommended that you store that data in an Azure storage account, rather than in the Storage Emulator. For emulation on Linux, use the Azurite emulator.ĭata created in one version of the Storage Emulator is not guaranteed to be accessible when using a different version. The Storage Emulator currently runs only on Windows.
#USE WINE EMULATOR FOR .EXE INSTALL#
To install the Storage Emulator, you must have administrative privileges on your computer. You can also install the Storage Emulator by using the standalone installer (direct download). The Storage Emulator is available as part of the Microsoft Azure SDK. For more information, see Use the Azurite emulator for local Azure Storage development. Azurite will continue to be updated to support the latest versions of Azure Storage APIs. Azurite supersedes the Azure Storage Emulator. Microsoft recommends that you use the Azurite emulator for local development with Azure Storage. The Azure Storage Emulator is now deprecated. When you're satisfied with how your application is working in the emulator, switch to using an Azure storage account in the cloud. You can test your application against the storage services locally without creating an Azure subscription or incurring any costs. The Microsoft Azure Storage Emulator is a tool that emulates the Azure Blob, Queue, and Table services for local development purposes. Use the Azure Storage Emulator for development and testing (deprecated)
0 kommentar(er)
