Visual studio feeds

All Visual Studio blogs in one place

Subscribe

Enter your email address:

Delivered by FeedBurner

Increase your website traffic with Attracta.com

Google+

Contact

Email:
Subject:
Message:
Anti-spam: How many eyes has a typical person?

Follow us on FB

Search

Automating your Azure infrastructure with Runbook management

AddThis Social Bookmark Button
With Azure automation, it’s now very easy to automate all your long running manual tasks that are repetitively executed in the Azure infrastructure with the help of PowerShell workflows that results in less errors in a better managed way. You can automate the creation, monitoring, deployment, and maintenance of resources in your Azure environment using the Azure Automation solution for Azure.

After creating the
automation account, click on the account and select Runbook from the dashboard
Click New and create a runbook with a title and description as given below
This will open the runbook edit workspace on the portal.
Automation runbooks are implemented as Windows PowerShell workflows. As you can see from the editor window, the workflow starts with a workflow keyword followed by the name of the workflow. You can add parameters...(Read whole news on source site)

Entity Framework Pitfalls: Command Interceptors and Identity Keys

AddThis Social Bookmark Button
The IDbCommandInterceptor (sorry, no official documentation) interface was introduced in Entity Framework 6 as part of the new interception and logging API, and allows the interception of the SQL and its parameters that are sent to the database as the result of DbContext CRUD operations.It offers two methods for each of the basic ADO.NET operations, those defined in DbCommand, one called before the operation is executed, and the other called afterwards:
ExecuteNonQuery (UPDATEs, INSERTs, DELETEs) –> NonQueryExecuting, NonQueryExecuted;
ExecuteScalar (SELECTs returning a single value) –> ScalarExecuting,
ScalarExecuted;
ExecuteReader (SELECTs returning rows) –> ReaderExecuting, ReaderExecuted.

As usual, the methods ending with “ing” are executed before and those ending with “ed” are executed afterwards, always synchronously.One might naively assume that INSERTs would always trigger a NonQueryExecuting/NonQueryExecuted call, and indeed it is so, unless we have an IDENTITY primary key, in which case, Entity Framework will instead call ReaderExecuting/ReaderExecuted. It’s easy to understand why: when we use an IDENTITY, we need to retrieve the generated value immediately after the INSERT, hence Entity Framework will generate code like:

Managing your Azure VM’s with your Phone

AddThis Social Bookmark Button
I have been doing quite a bit of ALM Training recently and have been trying to figure out how best to manage my training VM’s. In the last few months I have taught both the Managing Projects with Microsoft Visual Studio Team Foundation Server 2013 and TFS 2013 Developer Fundamentals a number of times and [...] The post Managing your Azure VM’s with your Phone appeared first on naked ALM - Experts in ALM, TFS & lean-agile with Scrum.

The Morning Brew #1787

AddThis Social Bookmark Button
Software OneGet (it’s in the Windows 10 Preview!) – Garrett Serack Announcing PostSharp 4.1 Preview 4: Xamarin Support, and More – Gael Fraiteur Modern.IE Chrome Extension – Leon Liang Updates for the F12 developer tools in the Windows 10 January Technical Preview – Ruben Rios Information Azure WebJobs are awesome and you should start using […]

Home