Thursday, March 13, 2014

Misleading Visual Studio Online Name


With recent release of Visual Studio 2013 and the related Visual Studio Online Cloud Service, I took look at what is Visual Studio Online.


What is Visual Studio Online?

  • Visual Studio Online is really a hosted source control, work item tracking, collaboration and a build service. 
  • Visual Studio Online is free for teams up to 5 users
  • Visual Studio Online is also included as part of MSDN subscriptions. 

What is Not Visual Studio Online?

Like the name suggest, Visual Studio Online is not an online version of Visual Studio IDE. In order to use the Visual Studio Online you will still need Visual Studio IDE installed on your development environment.


What Source Control Options are available?

If you have used the TFS, the same features are available online like below, alternatively you can use GIT as source control provider. You can choose Process templates to manage your work items.




Lightweight Development capabilities via Monaco.

However, there are lightweight development capabilities within the Visual Studio Online server. Below are the quote from ""

Visual Studio Online “Monaco” is a coding environment for the cloud, in the cloud.  It complements the desktop IDE as a low friction experience that will help you get started, or make quick changes, to an existing cloud service.  And it is integrated with Visual Studio Online.

“Monaco” is already being used as the technology behind other cloud-based developer experience, from Office 365 “Napa” development to SkyDrive file editing.



As developer when we use Visual Studio, it is all the capabilities of developing various software components using variety of support languages, deploy and debug and test. Just with the lightweight Monoao capability (No Server side coding). the name Visual Studio "Online" is misleading!.

Sunday, February 23, 2014

My Certifications


  • Microsoft Certified Application Developer
    • Microsoft Office SharePoint Server 2007, Application Development
      Microsoft Windows SharePoint Services 3.0, Application Development
    • Microsoft Office SharePoint Server 2007,Configuration
    • Microsoft Windows SharePoint Services 3.0,Configuration


  • .NET and the Microsoft .NET Framework
    • Developing XML Web Services and Server Components with Microsoft Visual C#
    • Developing and Implementing Web Applications with Microsoft Visual Basic .NET
      and Microsoft Visual Studio .NET
    • Designing and Implementing Databases with Microsoft SQL Server’ 2000
      Enterprise Edition
    • Designing and Implementing Desktop Applications with Microsoft Visual Basic 6.0
    • Microsoft Visual Basic 5.0 Programming



Friday, August 16, 2013

My Speaking Engagements


Monday, August 5, 2013

My Conclusions on Installation and Configuration of SharePoint 2013 Farm (& Related) and Development Efforts


This blog is part of Series : Comprehensive SharePoint 2013 Development Environment Installation and Configuration


With the past several weeks of (Retries over Months) effort on trying to establish an orderly process for Installing and Configuring SharePoint 2013 Farm for the purpose of Development (Equally applies to most QA/Stage/Production environments as well), I wanted to capture some of my conclusions on the overall process and the effort involved.


  • The overall SharePoint install involves several downloads (depending on other sub components you choose to install more software to be downloaded)
  • Other than basic SharePoint Install, typical farm installation process is very comprehensive (like this main series blog itemized)
  • Certain installations and configurations can be done only with a PowerShell Scripts and as you can experience following this blog series, there are several of them.
  • I have gone through several installation missteps  before I got it right (some of feature to work properly). So the sequence of installation and configuration is important to get it right.
  • Weather you are following the installation and configuration wizard or combination of PowerShell scripts, it it very critical to ensure appropriate configuration parameters are used. 
  • So by the time you had completed the baseline install and configurations, you would probably start jumping in to to start your development.
  • During this initial development effort uncover several security and further configuration requirements.
  • So what is the outcome: “Inefficiencies in starting an effective development”

Now having said that, don’t get me wrong, I am hardcore developer, but this “Time To Build” is too tedious. By the time IT learns all the details and get their environment ready for developers it will be a while!

Thursday, July 18, 2013

How to Configure UAG 2010 for SharePoint 2013


This blog is part of Series : Comprehensive SharePoint 2013 Development Environment Installation and Configuration


This blog article discusses how to configure UAG 2010 for exposing your SharePoint 2013 Site(s). Assuming you have followed the previous blog on how to install UAG.



From the Program Menu, run Forefront UAG Management





Assign your external and internal NIC cards accordingly
















Now create an UAG Trunk



Provide appropriate Public Host name for your UAG Trunk, this should be other than your Extranet URL.

Something like Provide your Public IP (I have a dummy IP below)


Add and select appropriate authentication providers below and I have left short of this here.



Follow next to Create and configure an Extranet…(Coming soon…)