Software Grunt and Gulp Intellisense in Visual Studio 2013 – Mad Kristensen Improved TypeScript Support in ReSharper 9 – Anton Lobov (JetBrains) Information kmon! ASP.NET 5 Where are my changes? – Shayne Boyer The Lava Layer Anti-Pattern – Mike Hadlow Use of Brackets – Paulo Zemek CloudTip 15-Avoid a gotcha in naming projects with Mobile […]
Microsoft has released a new public preview of Azure Active Directory Connect, a tool for connecting Windows Server AD to Azure AD. It will replace DirSync and the standalone Azure AD Sync tools.
To help make it easier to work with “big data” in your apps, we added support for Hive queries and management of data clusters with Azure HDInsight, the Microsoft Azure Hadoop cluster solution for Visual Studio. For Visual Studio 2012 and 2013, HDInsight support comes in a Visual Studio extension in the Azure SDK, and it’s baked into Visual Studio 2015 Preview. The extension makes it easier for you to visualize your Hadoop clusters, tables, and associated storage from within Visual Studio. It also supports creating and submitting ad hoc Hive queries for HDInsight directly against a cluster
from within Visual Studio and building a Hive app that is managed like any other Visual Studio project. Download the Azure Tools 2.5 SDK now for Visual Studio 2012 | Visual Studio 2013 | Visual Studio 2015 Preview. You’ll find HDInsight support in the Visual Studio Server Explorer, alongside other cloud services under the Azure node. Open the node and you’ll find that it’s now simple to explore clusters and Hive tables and their schemas, right down to immediate queries of the first 100 rows of a table for quick preview. This immediacy of the UI helps...(Read whole news on source site)
Recent acquisition to bolster performance and monitoring of applications through Application Insights service that will be included in forthcoming Visual Studio releases.
The Thing About Git
Git is quite different in this regard. You can work on five separate
logical changes in your working copy -- without interacting with the VCS
at all -- and then build up a series of commits in one fell swoop. Or,
you can take the opposite extreme and commit really frequently and
mindlessly, returning later to rearrange commits, annotate log messages,
squash commits together, tease them apart, or rip stuff out completely.
It's up to you, really. Git doesn't have an opinion on the matter.
Subversion: You should have committed the experimental changes to a separate branch before working on the bookmark stuff....(Read whole news on source site)