Not only that, it's now the first option recommended by Microsoft. Azurite to the rescueįortunately, there's an OSS project that Microsoft/Azure supports now and that was Azurite. I surely wanted to stay in that realm which would not be doable with the Storage Emulator. In my earlier post Deploying an Azure WebJob with GitHub Actions I was able to run build and deploy using Linux runner to reduce the cost. The second issue was running my CI/CD on Windows only. That would mean increased time for the builds, which I wanted to reduce rather than expand. I wanted to run the test suite and Windows runner on GitHub would have to have both Storage Emulator and SQL Server Express installed. Until GitHub Actions knocked on the door. Requires Microsoft SQL Server 2012 Express LocalDB instanceĪnd for quite some time I was OK with these limitations. (New-Object Net.WebClient).DownloadFile('', $msiPath)Ĭmd /c start /wait msiexec /i $msiPath /quiet $msiPath = "$($env:USERPROFILE)\MicrosoftAzureStorageEmulator.msi" While it's not big of a deal, using something like PowerShell it can be download and installed swiftly. And I'd continue using it if not a few inconveniences it had. For a long time, I was using Storage Emulator to execute some verification tests for ServiceBus.AttachmentPlugin project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |