After I published my recent blog posting about the keynote here,  I started to get questions on the blog and on Twitter to hear more about the Visual Studio one-click debug, deployment, activation, and installation. So, I have decided to do a follow-up blog with a little more information.

I have answered this question in two parts: What this means to the Developer and What does this mean to the Business/Agency/Organization

What this means to the Developer

With VS2010, you have the ability to add SharePoint Connections to a VS Project and see it in the Solution Explorer.

Once you have used that approach to establish a connection to a Dev Server, local Dev running on Windows7/Vista, or other SharePoint 2010 Server, VS2010 will automatically do a one-click install and debug during compile.

Some of the things it will do is:

• Uninstall old solution/web parts
• Unregister old solution in web.config
• Package the solution
• Push out the solution
• Activate the feature
• And allow you to set a breakpoint in code in VS that is automatically attached to the right process after one-click deploy.

It is estimated that the new approach saves 20 actions that are common in testing and deploying a solution or component.

Not only will you get VS debug capabilities, but you will get a Developer Dashboard in the resulting web page to help with optimization of your code.

What does this mean to the Business/Agency/Organization

So, cutting through all the semi-technical descriptions above, what does this mean to your organization for SharePoint 2010?

This means that the speed to create solutions, custom code reliability, custom code performance, and ability to formalize your SharePoint 2010 development through Team Foundation Server (TFS) will be dramatically improved!

These new tool improvements will allow you to share that custom code with the organization, community, or partner organizations more easily.

I hope this added a little more clarity and I will look for more information to share while at SPC09.