Many of our clients are adopting Team Foundation Server(TFS) as an ALM solution from Microsoft. With the cloud adoption and new business strategies, clients’ ask for a TFS in cloud. When we recommend Visual Studio Online (VSO) to address the client needs, most of the clients turn back and tell us; ” No, we don’t want Visual Studio in browser, we will use the IDE from our desktop. But, we want TFS access through cloud based services”.
The confusion created by the name Visual Studio Online is there in every end user. People are reluctant to accept the fact that VSO is a SaaS offering from Microsoft for TFS services. They always think, there is some relation with VSO and Visual Studio; not with TFS.
Microsoft addressed all these confusions yesterday in Connect event, by announcing the new name for VSO – Visual Studio Team Services; better than the previous name. Hope, now I will be able to convince the clients that VSTS is the SaaS offering of TFS. Oh! sorry, we should not use that short form, which will make more confusion. Those who remember Visual Studio 2005 and 2008, we used to have special editions of Visual Studio called Visual Studio Team System(VSTS) targeting different groups.
Now, what will be the short form of the new Visual Studio Team Services ?
You are reading the first version of this book, i.e., first three chapters are completed and available in LeanPub. This work in progress version is available at a reduced prize of $9.99. Once bought, customers will receive any future updates to the book for free. Expected final prize will be $16.99. Unconditional 45 days money back guarantee. Moreover, you can suggest the topics you would like to see in the final version.
For more details https://beginningwebapplicationdevelopmentwithnode.wordpress.com
Recently I have come across a question about the HTML5 feature support by different browsers. How you make sure that the application render properly in non-supporting browsers?
Answer for above question is the proper usage of Modernizr and Polyfilling.
Polifill is a code block that mimics the functionality of an API by providing fallback functionality to older browsers. For example, LocalStorage introduced in HTML5 is not supported in IE7; but we can use a Polifill to implement the LocalStorage support in IE7.
Modernizr along with Polyfill help the UI developer to address the non-supporting browsers.
Live Code Analyzers provide live errors and warnings depends on the code analysis rule in the editor itself. It is integrated with NuGet packages, where we can add new rules using NuGet. When we type our code, analyzers start providing recommendations and warning on the code we typed.
We can enable and disable the rule sets and also can set the action for each of the Ruleset. When we create any project using Visual Studio 2015, default Analyzers will get added to the project.
Right click on the Analyzer and select ‘Open Active Rule Set’ to change the rule set settings.
We can activate and deactivate the rules and also set the actions as Warning, Error, Info and so on.
Start typing on the editor and observe the error messages and warning appearing on the Error window.
I have been working with various clients on Team Foundation Server implementations, for a long time. Implementation varies from Version Management to complete DevOps. I have faced many hurdles in my journey; resulted new learning and experience. I have already published an article on the work item customization in Simple-Talk.
TFS Administration involves various facts from installation and configuration till access management and integrations. I have been working on listing down the topics for my new book since few weeks. I have published the topics and the unedited version of the first chapter in LeanPub.
I will be adding more and more chapters to make the TFS Administration book to a complete guide for the TFS Administrators.
Share your thoughts and the topics you are interested to see as part of this book.
Posted in Book, General
Tagged Book, TFS