Monthly Archives: November 2012
The worldwide SharePoint Conference for 2012 (SPC12) is almost upon us. We are expecting this years conference to be massive with the new Wave 15 of technology having now having been release to manufacture by Microsoft. So we go into this conference with SharePoint 2013, Office 2013, Exchange 2013, Windows 8 all ready for production. Expect plenty of awesome sessions showcasing the power and opportunities that the new wave of technology brings with it.
The OnePlaceMail Team have been incredibly busy in preparation for this event with the new OnePlaceMail product ready to go straight into SharePoint 2013 / Office 2013 / Exchange 2013 production environments. This is welcome news to our early adoptors, those of you who have been using OnePlaceMail against the Preview software and in TAP environments, and are looking to go straight into production with 2013.
You will find the OnePlaceMail Team at booth #1046 in the Exhibition Hall where we will be running live demos of OnePlaceMail on the new technology. Of course we will have giveaways and competitions so you don’t leave the conference empty handed.
I look forward to meeting new friends, talking SharePoint and enjoying a SharePint or two.
Hope to see you there.
I often have the need to distribute Visual Studio source code to external parties. Internally this source code is under source control in Team Foundation Server (TFS).
It would be nice if you could just take a copy of the source files and remove the source control binding (in Visual Studio). Unfortunately I haven’t found a way to be able to do this. Even when Visual Studio says that all bindings have been removed, if you try to open up the solution you get an error message along the lines “The solution you are opening is bound to source control on the following Team Foundation Server …”
Under earlier versions of Visual Studio I had used Visual Source Safe for source control and had used a utility called VSSBindingRemover which did the job quite effectively. It removed all source control files with the solution and project directories and modified the solution and project files themselves to remove source binding information.
The process for removing bindings is simple:
- Ensure you don’t have the solution/projects open in Visual Studio
- Copy your solution to a new directory (because the tool does modify files)
- Run the utility from the command line: VSUnbindSourceControl.exe d:\mysolution folder
Once the tool is finished, all the source control bindings have been removed from any solution and project files.