Having used Team Foundation Systems (TFS) for many years I grew accustom to having an automated build process and the ability to have the Revision number in my binary file versions. Recently I began work for a client that used SubVersion as their source control system. This removed much of the niceties I was used to having in other TFS based projects. I set out on a search of the internet and found a couple methods to provide similar functionality of tying a deployed package of code back to a revision in my source control.
Both of these methods require that you use the Tortoise SVN tool and have it installed on your local system. Since both of these methods do not require you to actually log into SVN to get the revision number, it is important to note that the…
Have you ever thought to yourself that the development experience in SharePoint is quite frankly a pain? That there are no real best practices or guidance about how to conduct application development or how to use an Application Lifecycle Management (ALM) process?
I was introduced today to the link below on msdn that offers a series of articles whose goal is to define some best practices and offer guidance on how to conduct an ALM process using tools such as Visual Studio and Team Foundation Server.
Most of the articles are still under construction, but this definitely looks like a link to keep handy.
The link is http://msdn.microsoft.com/en-us/sharepoint/cc990283.aspx.