pinvoke.net: the interop wiki! Microsoft All-In-One Code Framework - a centralized code sample library Windows Phone 7 Developer Guide January 2012 This guide provides an end-to-end walkthrough of how to create an advanced Windows Phone 7.5 app that integrates with remote Windows Azure-based services. The guide can help you understand how to implement individual features for Windows Phone 7.5 and how to use them together to build an app. This guide teaches how to : Use Windows Phone 7.5 features including push notification, live and secondary tiles, and background tasks. Manage state and perform navigation. In addition to describing the client application, its integration with the web services, and the decisions made during its design and implementation, this book discusses related factors, such as the design patterns used, and the ways that the app could be extended or modified for other purposes. This guide was produced by the following individuals: We want to thank the customers, partners, and community members who have patiently reviewed our early content and drafts. Questions?
Code Sample CUDA integration with C# 1. Syntax coloring Important notes about example files: You must do this basic configuration to be able to open attached example because of custom build rule entry in project solution file. VC++ 2008 will show errors if that rule won't be accessible due to wrong paths. If this won't help then just create new project, manually add custom build rule as described before in configuration section and then copy source .cu file from the example to that new project. You need also manually copy file cutil.h from \NVIDIA GPU Computing SDK\C\common\inc\ dir to C:\CUDA\include\ (it is easiest way to fix import paths) and add cutil32.lib (or cutil64.lib for 64bit OS) to linker input additional dependencies -> should be now like this: cudart.lib cutil32.lib (already done in example projects). CUDA toolkit and SDK version 3.0 had been used to build dll part. And you need VS 2010 version for C# project part because .NET 4 features has been used. Part 2: CUDA DLL Finally example kernel function: stp.Start();
NUnitit - a Visual Studio Addin for NUnit Dynamic Data Display Advanced Unit Testing, Part I - Overview Oh dear God, anybody who votes [for unit-testing] has major problems. I hate the @#$% things. And the "Write tests first, code later" paradigm eludes me. I mean, come on, unit testing is not the end-all, be-all people! I don't care how sophisticated your tests are, a "pass/fail" grade is not sufficient to make sure you're ready for production. - David Stone, on the "do you like design or unit testing better" survey. Contents Preface This is a meandering article on the issues of unit testing and the Extreme Programming (XP) process. The four articles in this series are: Introduction As brash as the title sounds, I personally feel that the concept of unit testing has a long way to go. On the other hand, I'm realizing that unit testing has its place in the code-writing process. On the other hand, I also think unit testing is too simplistic. There is also the idea that if your unit tests pass, then your code is ready for production (or, at least, acceptance testing). What Is A Unit Test? SetUp
Console Unit Testing - ploeh blog In many scenarios, console applications are very useful, but if you have a console application of intermediate complexity, you should obviously unit test it like all the other code you write - right? If you have a console application as an administration utility for a complex piece of software you are developing, the console application should obviously just be a thin UI layer that delegates all the work to a testable library that may already exist, but even so, you may have some complex UI interaction that may benefit from testing. For once, consider the task of parsing the command line arguments. This may involve some semi-complex logic where unit testing may save you a lot of troubleshooting. You may also want to have a regression test suite to validate that console output is as expected. In any case, you need to deal with console input and output. Let's say that I want to unit test this method: public void DoWork() Console.WriteLine("Ploeh"); [TestMethod] Console.SetOut(sw); cu.DoWork();