- Create an ASP.NET WebApp
- At project node, Add “New Azure WebJob Project”
- Choose project type: Continuous/OnDemand/Schedule
- A JobHost.RunAndBlock(); in void Main().
- A method for [QueueTrigger/BlobTrigger(queuename)] to dequeue message from queue
- On Demand/Schedule:
- A JobHost.Call(methodname, value) in void Main().
- A method for [Queue/Blog(queuename)] to enqueue message to the queue
- Publish WebApp and/or WebJob projects to Azure. And you will find the WebJob deployed under the WebApp App_Data folder
- Configuration: Add Azure Storage Connection String to Live Azure Web Site.
- Go to Server Explorer –> Storage to get Storage Connection String
- Go to Websites –> Settings, create 2 entries AzureWebJobsStorage & AzureWebJobsDashboard. And select Custom from the Database Type column.
- Debug Contiuous WebJob: In Server Explorer, goto your WebJob and make sure it is started.
- Attach Debugger. Set your breakpoints.
- View static Logs.
- Use View Dashboard in the context menu.
- Use Kudu
- Run OnDemand WebJob to send message to the queue which will in turn trigger any breakpoints in the continuous WebJob.
Use the certificate method
The Azure module includes cmdlets that help you download and import the certificate.
The Get-AzurePublishSettingsFile cmdlet opens a web page on the Azure Management Portal, from which you can download the subscription information. The information is contained in a .publishsettings file.
The Import-AzurePublishSettingsFile imports the .publishsettings file for use by the module. This file includes a management certificate that has security credentials.
Stop-AzureVM -ServiceName “myServiceName” -Name “myName” -StayProvisioned
Connect() – This video provides a quick overview of Azure Active Directory from a developer’s standpoint and gives a glimpse of the new identity features in Visual Studio 2015 that make it easy to secure applications with Azure AD.
Here is the instruction on using Visual Studio 2015 preview to add Azure Active Directory SSO to an existing MVC Application.
1. Create an Azure Active Directory
2. Add user(s) to directory
3. Right-click the project and click “Configure Azure AD Authentication”
4. Enter your Active Directory Domain Name e.g. yourid.onmicrosoft.com This will integrate an Application to the Active Directory
5. Click the Application Link and click the Configure Tab and change the “Reply Url” to your webiste’s Url so Azure AD know where to send the SAML authentication tokens after successfully authenticated the Users.
6. optional update the [Authorize] attribute in the controllers
7. optional add the login/logout/username html to the view. e.g. add @Html.Partial(“_LoginPartial”) to _layout.cshtml
8. Finally publish the WebApp to Azure. Right click on project and click “Publish…”
The Katana component architecture divides an application into four logical layers, as depicted below: host, server, middleware, and application. The component architecture is factored in such a way that implementations of these layers can be easily substituted, in many cases, without requiring recompilation of the application.
An example of components from different layers
- Host: IIS/ASP.NET, OwinHost.exe, Self-Host/Custom-Host(e.g. Windows Service)
- Server: SystemWeb(ASP.NET pipeline), HttpListener (OwinHost/Self-Host/Custom-Host)
- Middleware: Web API, SignalR, Nancy
- Application: Your Application.
Run your jobs on simple or complex recurring schedules
- Call services inside or outside of Azure
- Run jobs on any schedule—now, later, or recurring
- Use Azure Storage queues for long-running or offline jobs
- Management REST API
Get Started using Scheduler MSDN