I seem to recall, that in the past, there was WASABi in Enterprise Library 5, which was used in order to scale Azure Cloud Services.
I've recently installed Enterprise Library 6 and noticed that WASABi is not a part of it.
How do I scale an Azure Cloud Service deployment nowadays?
Is it possible to set up the scaling solution locally for testing?
How do I scale an Azure Cloud Service deployment nowadays?
If you're looking to scale Azure Cloud Service in the cloud (and not on local emulator), you can make use of Azure Auto Scaling. You may find this link useful for that: http://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-scale/.
Is it possible to set up the scaling solution locally for testing?
It is not possible to do so in SDK 2.4. This is one of the breaking changes in SDK 2.4. From the SDK 2.4 release notes:
The Full Compute Emulator is deprecated- The Full Compute Emulator is
deprecated in SDK 2.4. As with SDK 2.3, all new Cloud Services
projects now use Emulator Express by default. Emulator Express allows
you to test your multi-role Cloud Services locally without requiring
administrator privileges. Unlike Full Compute Emulator, however,
Emulator Express only supports one instance per role.
Related
I am developing a C# ASP.NET Core web application for Azure. I am using the Microsoft Azure Storage Emulator for local testing: https://learn.microsoft.com/en-us/azure/storage/common/storage-use-emulator
I want to use blob versioning as described here:
https://learn.microsoft.com/da-dk/azure/storage/blobs/versioning-overview
https://learn.microsoft.com/da-dk/azure/storage/blobs/versioning-enable?tabs=azure-cli
Is this supported by the Storage Emulator? I cannot find any description of how to enable it for the emulator, at least.
Is there any convenient way to test blob-version-related code locally?
No, this feature is not enable on latest storage emulator.
Please check the latest version of Storage Emulator. This version don't have versioning feature.
The versioning feature of blob storage becomes available in August 2020.
There exists a great amount of documentation and samples on how to create build definitions for VSTS and TFS 2015+ for Service Fabric continuous integration and deployment.
What is available in terms of integration with TFS 2013 for deployment of Service Fabric applications?
How do we integrate the build and deployment of on-premises Service Fabric clusters / applications / services with TFS 2013?
Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable distributed applications. It was developed as a Microsoft-internal-only platform for over five years, which shipped publicly as a product in 2015.
The vNext build is also released on 2015 and have many benefit such as simple, deep Customization than XAML build. So most documentation is related to vNext build.
According to the build and release steps in documentation you provided above,it's general normal tasks such as build , test, copy files ,publish artifacts, it's not hard to convert to XAML build. You just need to do some build activities customization. One specific task is Azure Resource Group Deployment Task, there is no such correspondingly in XAML build. However, this task is used to create or update a resource group in Azure using the Azure Resource Manager templates. You could try to use powershell to achieve this part. The most import is using powershell script to publish to Service Fabric.
Actually, when working on TFS2013 XAML build, usually we integrate with Azure Cloud Service not service fabric. There are also related blog with detail steps show how to do it. You could take a reference: Continuous Delivery for Cloud Services in Azure
Moreover, since you are still using XAML build and stay on TFS2013. We encourage you update your TFS version to get latest technology and move to new web-based vNext build system.
On TFS2018, we even removed support for XAML Builds. For the benefit of VNext builds, you could refer to this article: Why You Should Switch to Build VNext
When going to publish my Mobile Service Backend there is supposed to be an option that says "Microsoft Azure App Service" but instead I get two other options: "Microsoft Azure Web Apps" & "Microsoft Azure API Apps (Preview)".
The Web Apps option identifies my service plan and SQL server but wants me to create a new mobile web app url which I already have.
Neither of these show my App Service I have already created. Is it because I don't have Azure SDK v2.9 or higher (as stated by the online resource I'm using)? When going into the NuGet Packages and it only has v2.0 for Microsoft.Windows.Azure.Server and no higher version
Anybody know how to get the higher SDK without going through VS 2015 or any other options?
According to your description, I suggest you could firstly check the existing of the mobile service resource in the VS2015 server explorer.
You could open it in the view --> server explorer.
Anybody know how to get the higher SDK without going through VS 2015 or any other options?
If this resource is existing, but the publish windows doesn't show this resource.
I suggest you could update your azure SDK(the newest is 3.0.1), you could install it in this link.
Besides, I suggest you could check you have created mobile service not web app service.
I looked into Azure cloud solutions and came up with below question regarding developing web app locally.
It seems like, if you develop Cloud Service, you can run locally with Azure emulator, if you develop Azure Fabric Cluster, you can run your cluster locally.
However, if you develop Wep app (part of App service) and you want to debug your app locally, you can either connect remotely your debugger to running web app or run the web app on your local iis.
Issue is, debug on azure emulator or running on local cluster seems to illustrate running the app on cloud better than develop on your local iis.
Am i missing something, or the development experience on App service lacks the option to run locally on "cloud like" environment(excluding the option of remote debug)?
Thanks a lot!
There is no emulator for App Service because at its core it is just an IIS farm (the Windows App Service at least).
We run apps locally on IIS Express + SQL Server 2016 Developer edition, and that corresponds quite well. Of course if we wanted we could set up an IIS farm locally and use that, but I think that's unnecessary.
You can get a bit closer to actual environment if you use the App Service Linux offering, as there you will run everything on Docker containers. So you debug on local Docker and then run it in prod on Docker.
I would also recommend you to check out deployment slots on App Service, as a staging deployment slot can help you find problems that occur in the cloud environment before you swap it into production.
In my personal experience developing apps for App Service, problems in the production environment were not caused because the environment was very different, but because we overlooked something with the database, made a mistake in a Web.config transform etc.
We currently have an internal WPF application that serves the business in different ways for different departments. We have a staged rollout process that takes changes through the following steps:
Development (local)
Alpha testing
Beta testing
Live
Developers need to be able to run all of these versions of the application, and some users access the Beta version to sign off new features.
Currently, this is done through a Launcher application deployed via ClickOnce, which downloads and runs the client binaries for the selected version. Each version of the application is hosted by a corresponding web service on the appropriate server (alpha, beta, live).
Does anyone know how this could be done through UWP? We want to future-proof the application and think about support for surface, windows phone etc. But in all cases, developers and users should be able to access the different versions of the application, sometimes even running them at the same time.
Is there support for this kind of concurrent deployment of multiple versions of the same UWP application?
For development these applications may be installed via powershell. From the AppStore you would only get the latest released version but locally you can do what you want.
The required powershell scripts are provided when you deploy the files to the local file system with visual studio. They will even prompt you to create a local developer key if required for your machine.