News
Stay informed about the latest enterprise technology news and product updates.
Build and unit test Windows Azure projects from TFS Team Build
Windows Azure Storage a fast, scalable, and reliable storage solution for your Windows Azure applications. With the Windows Azure SDK, you get a version of Azure's cloud server and cloud storage that run on your desktop – DevFabric.exe and DevelopmentStorage.exe, respectively.
Download: The Developer's Guide to IoT
The IoT world may be exciting, but there are serious technical challenges that need to be addressed, especially by developers. In this handbook, learn how to meet the security, analytics, and testing requirements for IoT applications.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.
- Configure an interactive-mode TFS Server.
- Log in to your build server.
- Start TFSBuildService.exe
- Create a Team Build that compiles your Windows Azure project and runs your unit tests.
- Customize the Team Build BeforeTest "Target" to start DevelopmentStorage.exe.
- Run the build.
Figure 1. To start editing your build script, right-click the build and choose View Configuration Folder
You should now be in Source Control Explorer and you should see the two files that define for Team Build – TFSBuild.proj and TFSBuild.rsp. Double-click TFSBuild.proj to start editing the build script.
Figure 2. The build definition files. Double-click TFSBuild.proj to edit the build script.
Figure 3. The Team Build script.
In order to make our unit tests run against Windows Azure Storage, we need to make sure that Development Storage is running and that the tables it will be using have been initialized before the unit tests start executing. To do this, we'll hook in to the BeforeTest MSBuild target. A target in MSBuild is roughly the same as method in C#. It defines a series of tasks that should happen when the target is executed. Team Build gives us a handful of targets that we can hook in to various events in the build process. Not surprisingly, the BeforeTest target runs after the code has been compiled and just before the unit tests are executed.
Figure 4. An empty BeforeTest MSBuild target
Windows Azure Storage is essentially just a handful of REST service endpoints. In production, these REST endpoints are the front end of a massive number of servers that are ready to store your data. In development, Development Storage (DevelopmentStorage.exe) exposes the same REST service endpoints but uses SQL Express as its backend. When you're running in development, you first have to execute a utility called DevTableGen to initialize SQL Express with the tables required to run your application. When you call DevTableGen, you'll send it the database name you want to use and a list of DLLs in your application. It will look for any property of type System.Linq.IQueryable
Figure 5. Use an MSBuild ItemGroup to get the list of all the DLLs
To get the list of DLLs, we'll use an MSBuild ItemGroup inside of the BeforeTest target. ItemGroups as similar to array variables and are particularly good at storing arrays of file names. In figure 5, we declare an item group named TableAssemblies that "includes" any file ending in *.dll in the compilation output directory.
Figure 6. Properties required to run DevTableGen.exe and DevelopmentStorage.exe
Next we'll need to set up the configuration values that are required to run DevTableGen.exe and DevelopmentStorage.exe. We'll do this with an MSBuild PropertyGroup and MSBuild Properties. Properties MSBuild's equivalent of variables. In figure 6, we set up the connection info for the database we want to use and the path to the Azure SDK binaries.
Now that we have all our configuration values set up, we need to start the EXE's. For this, we'll use the MSBuild Exec task. Exec essentially issues a command line call from our MSBuild script and waits until the program exits before moving on to the next task.
Figure 7. The Exec task to run DevTableGen.exe
Figure 7 shows you the Exec call for DevTableGen. Please note that the value for the Command attribute has been formatted for readability and should actually be all on a single line.
Figure 8. The Exec task for starting DevelopmentStorage.exe
And finally, now that everything is initialized, we make the call to start DevelopmentStorage.exe as seen in Figure 8. Since the Exec task waits for the command it calls to exit and since we need DevelopmentStorage to keep running while we run our unit tests, we need to do a workaround so that the build doesn't hang on this Exec statement. To do this, we specify IgnoreExitCode='true' and Timeout='10000'. IgnoreExitCode tells the Exec task that we don't care what the return code was from whatever it just called and Timeout says to wait 10 seconds before moving on to the next line in the build script. This 10 second delay is helpful because it gives Development Storage a chance to initialize before the unit tests start running.
So, once you have made all these changes to your TFSBuild.proj build script, check it in to TFS source control, make sure that TFSBuildService.exe is running in interactive mode, and kick off a build. If you watch the screen on the build server, after a few seconds you'll see Development Storage start up as your unit tests start to execute (Figure 9).
Figure 9. Development Storage is starting.
You've successfully made Windows Azure storage start as part of your build and your Azure unit tests can run.
Start the conversation
0 comments