Visual studio feeds

All Visual Studio blogs in one place


Enter your email address:

Delivered by FeedBurner

Increase your website traffic with



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

Follow us on FB


Visual Studio Toolbox: Azure SDK 2.7

AddThis Social Bookmark Button
In this episode, I am joined by Brady Gaster and Mike Morton, who show us what Visual Studio developers get when they install the Azure SDK 2.7. Among the many enhancements they show are: Visual Studio provides the ability to sign in with multiple Azure accounts simultaneously [02:15] Cloud Explorer, a new tool window which will soon replace the Azure node in Server Explorer [05:23] New templates for creating Azure API apps and Azure App Service tooling improvements, including improvements to the Swagger generation process  [23:00] Improvements in how you work with multiple resources and resource groups
href="">[38:45] For more information on the Azure SDK 2.7, read the Azure team blog post here.
...(Read whole news on source site)

Top Azure News for Visual Studio Developers – August 2015

AddThis Social Bookmark Button
A lot has happened on the Azure side of the house in the last couple of months. We wanted to give you some of the highlights in case you aren’t already following the Azure blog, focusing especially on items that are most relevant to developers using Visual Studio. Using App Service Web Apps Continuous Deployment with GitHub Organizations. You might have already enjoyed the continuous deployment feature of Azure App Service when a web app is tied to a GitHub account. I know it came in very handy for the Visual Studio 2015 Product Guide, because it meant
never having to think about deployment again. We’re delighted that this feature is now also available with organization repositories on GitHub! Dependency call stack and Application Insights SDK labs. .NET developers already enjoy the capabilities provided in the Azure SDK 2.7 for .NET, which allows you to track calls from your app to external dependencies such as databases or REST APIs. The Application Insights SDK Labs is an experimental package that also lets you see where those calls originate in your apps, something that’s difficult with the current SDK.   Update on .NET Framework 4.6 and Azure. Speaking...(Read whole news on source site)

Building A Component-Based Web UI With Modern JavaScript Frameworks

AddThis Social Bookmark Button
Most modern front-end JavaScript frameworks provide some sort of support for component based development. This is an incredibly important step in the direction of development for the web. Components provide a way to write small parts with a consistent API that can easily be orchestrated as part of a larger screen, application or system. Component based development isn't just the future of the web, though. It's what you should be doing now, in any modern UI / application framework on the web.

The Rise of JavaScript Frameworks – Part 2: Tomorrow

AddThis Social Bookmark Button
  In Part 1 of this series I talked about the current state of JavaScript frameworks and how in many ways JavaScript frameworks have become the new baseline for developing client centric Web applications or Single Page Applications. Due to the complexities involved in building complex client side applications using JavaScript and HTML, frameworks have just about become a necessity to effectively building any non-trivial application. Frameworks are a huge help with organizing code, providing easy ways to bind data from models rather than binding data to the DOM manually with imperative code, providing tons of helper functionality
for operations most applications need like view and nested view routing, form validation, http request management and tons of other features that every application needs but isn’t immediately obvious as a bullet point feature. Version 1 of the major frameworks came about later than I would have expected them to, as there was a lot of pent up need to address the missing pieces. When these frameworks finally did arrive on the scene and got to a reasonably stable point, public interest took off like wild fire and adoption rates have gone through the roof since then. It’s not surprising...(Read whole news on source site)

Optimizing I/O throughput

AddThis Social Bookmark Button
We got a customer request about performance issues they were seeing on startup on a particular set of machines. Those machine run in a cloud environment, and they have… peculiar, one might say deviant, I/O characteristics. In particular, the I/O pipeline on those machines is wide, but very slow. What do I mean by that? I meant that any particular I/O operation on those is likely to be slow, but the idea is that you can get much better performance if you issue concurrent I/O. The system is supposed to be able to handle that much better, and overall you’ll
see the same relative performance as elsewhere. This is pretty big issue for us, because for many things, we really do care about serial I/O performance. For example, if we are committing a transaction, we really have no other way to handle it except to wait until the I/O is fully completed. That said, the particular scenario where we had the problem was startup. If the database was under heavy load at the time it shut down, the recovery logs would be full, and the database would need to replay the recent actions that happened. Note that shutdown performance is...(Read whole news on source site)

The Morning Brew #1933

AddThis Social Bookmark Button
Software Download Visual Studio 2012 Update 5 – Microsoft Downloads An open-source full-fidelity XML parser – Kirill Osenkov RazorPub is live – Al Nyveldt Information AntiPattern – Martin Fowler TypeScript and JavaScript in ReSharper 9.2 – Anton Lobov Web API 2 – don’t get caught with your parameters down – Tahir Khalid #VS2015 – Delete […]

Why Is The First Start Of An Application Slow?

AddThis Social Bookmark Button
Originally posted on: of us have experienced it but very few of us have gone into the details to really find the reasons for it. First of all why should I care? After the first time the application starts much faster. Well you should care if you want to give your customer not only a good second startup time but also a decent first startup experience. To do that you need to do repeated tests. The first startup is commonly referred to cold startup and all subsequent runs are warm startup scenarios. To test a cold startup scenario
you need to reboot your computer every time and start your application. Not very practical and I have no one ever seen going down that road. The difference between warm and cold startup time is that the first time the dlls and data of the application need to be loaded from disc which can take quite some time. All subsequent runs can read the data not from disk but from the in memory file system cache which is managed by the operating system. What Is The File System Cache? Windows uses the memory of your system in...(Read whole news on source site)

Version Control, Git, and your Enterprise

AddThis Social Bookmark Button
Version Control, Git, and your Enterprise

article is about understanding Git – both its benefits and limits
– and deciding if it’s right for your enterprise. It is
intended to highlight some of the key advantages and disadvantages
typically experienced by enterprises and presents the key questions to be
contemplated by your enterprise in determining whether Git is right for you
and what you need to consider in moving to Git.

A Day in the Life of Visual Studio Send a Smile Feedback

AddThis Social Bookmark Button
Last time we talked about the Feedback Tools in Visual Studio 2015 RTM and I shared how you can send us feedback. In this post, I am going to share what happens to the feedback after you send it to us. There are two key goals that we have for the feedback that you share: Look at it as quickly as possible Act on it as quickly as possible The action taken could be any of these listed below (and I will elaborate on these in the post below): Determine the problem and fix Contact you to get more information, if required Communicate a solution
or work around to you Flag it to fix in an upcoming release Determine that it’s not something we will fix, and communicate the reason back to you Or acknowledge that you like the product or a feature (or don’t), but haven’t filed a bug We get a LOT of feedback on Visual Studio. To give you some idea of the volume, we have already received over 10,000 Send a Smile feedback items for VS2015 alone since we released on July 20! To ensure your feedback doesn’t get lost in this volume, we do a lot to get it to the right folks quickly! We...(Read whole news on source site)