- Self organized, not unorganized
- People biased, not process biased
- Results driven
- Deliver working software
- Trust the individual
- Respond to change
- Satisfy customers
If you’re like me one email account just isn’t enough. I’ve got several, most gmail, that I use on a regular basis. However, since I got my iPhone in the fall of last year I’ve been a little annoyed with the way I’ve had to interact with one of my accounts.
I like to be able to send mail from multiple accounts on my iPhone. This requires me setting them up individually. No big deal. I also like to see all of my email in one big in box. Again, no big deal, the iPhone handles this with ease.
However, I like to also be able to work with my mail on my PC. Here’s the problem. Until recently the only way to interact with all of my accounts was to set them up on my primary gmail account and have it check all my mail. If I didn’t do this I would have to log out of gmail and log in with my alternate account to check my mail.
The problem is that because I have my primary gmail account checking my email and I have that account and my secondary account setup on my iPhone I get two copies of every message on my iPhone.
I know, I know, it’s a first world problem at its best but it annoys the crap out of me.
Imagine my happiness today when I attempted to log into my secondary account on my laptop and discovered that Google Chrome now allows me to be logged in simultaneously to BOTH of my gmail accounts. This means I can switch between the two in gmail without having to log out.
MSBuild is a powerful tool right out of the box. With the ability to manipulate files and execute external commands there is a lot of mileage a creative Build Team can squeeze from it. However, this barely scratches the surface of what it can do. When you add on the MSBuild Extensions Pack you open up a whole new world of tasks that improve the capabilities of the Build Team.
One of the simplest, most useful, tasks available in the Extension Pack is the SqlCmd task. This simple task does an amazing thing. It allows you to execute SQL commands either directly or via script files directly in your build execution. This opens up several possibilities for complementing the build process. From actions such as deploying new data structures to support the build to cleaning up data or reshaping it to meet new requirements.
The example that follows is basic in nature but describes the steps necessary to use the SqlCmd task to execute SQL Scripts against your database.
1. Create an empty solution in Visual Studio and add a scripts directory to house your sql scripts.
2. Add a text file to the scripts folder with a .sql extension.
3. Modify the script to perform a basic select operation
4. Save the script.
5. Right click on the project in Studio and select “Unload Project”.
6. Right click on the project placeholder and chose “Edit <Project>.csproj” where <Project> is the name of your project.
7. Edit the csproj file to import the Extension Packs tasks file
<Import Project="$(TPAth)" />
9. Reference the script files
<InputFile Include="$(SolutionDir)Scripts\**\*.sql" />
10. Add the SqlCmd task to call the script to the BeforeBuild target.
<MSBuild.ExtensionPack.SqlServer.SqlCmd TaskAction="Execute" Server="MySQLServer\SqlExpress" Database="MSBuildDemo" InputFiles="@(InputFile)" LogOn="BuildUser" Password="password" />
11. Save the csproj file.
12. Right click on the project place holder and click the “Reload Project” option.
13. Rebuild the solution.
14. The SQL Commands will execute as part of the build process.
Work item queries in Team Foundation Server allow simplified management views of those items. However, the default view splits the results from the details of the work item in a horizontal split. This makes it somewhat difficult to view the full detail of the work item.
A better view is to use the vertical split. You can then see the full details of the work item while scrolling through the query results.
This is an affiliated link.
One of the most essential steps in managing web application updates is the ability to recover to a point in time prior to the update should the deployment of updates be unsuccessful. MSDeploy simplifies this step and can even be incorporated into build definitions to create automated backups when a deployment build is executed.
To create a backup of a site from an existing site simply execute the following command:
msdeploy -verb:sync -source:iisapp=”Default Web Site” -dest:package=c:\defaultsite.zip
This will create a deployment package of the iis application running as “Default Web Site” on the machine where the msdeploy command was executed. If you want to remotely administer a web server ensure Web Deploy 2.0 is installed on the target machine and modify the command as follows:
msdeploy -verb:sync -source:iisapp=”Default Web Site”,computername=MyServer -dest:package=c:\defaultsite.zip
You must have administrative privileges on the server you are trying to sync from in order for this command to be successful.
Restoring the backup is as simple as running the command below:
msdeploy -verb:sync -source:package=c:\defaultsite.zip -dest:iisapp=”Default Web Site”,computername=MyServer
Again, you will need administrative privileges on the target server for this command to succeed.
Finding the Google+ profile button generator took far longer than I expected. Apparently my Google Fu was weak this morning. I finally found it though and now my site sports a snazzy new social media badge.
Thanks to Sarah Gooding and her post “How to Display a Link to Your Google+ Profile on Your WordPress Site” for finally making this click for me.