Parallel Extensions

http://channel9.msdn.com/shows/10-4/10-4-Episode-6-Parallel-Extensions/
In this episode of 10-4, we start taking a look at Parallel Extensions to the .NET Framework. We'll look at some of the surface-area of the Parallel Extensions API and provide you with enough information to start working with it yourself in the Visual Studio 2010 CTP VPC. Remember that we are running these bits within a virtual machine with a single virtual processor, so you won't be able to see the performance improvements from the library. However, you will be able to start get a feel for the API itself. In future episodes, we will dive into deeper details of the various parts of Parallel Extensions. Also, in next week's episode, Jonathan Carter will be back to talk about another new feature in ASP.NET 4.0, so make sure to stay tuned for that!For more 10-4 episodes, be sure to visit:http://channel9.msdn.com/shows/10-4
Visual Studio Topic Area on Channel 9:http://channel9.msdn.com/VisualStudio
Visual Studio 2010 CTP VPC:http://tinyurl.com/GetCTP
Visual Studio 2010 Training Kithttp://tinyurl.com/VS10KitConcurrency MSDN Dev Centerhttp://msdn.microsoft.com/concurrency10-4! Over and out!

Windows 7 recommanded developement tools.

This release of the Windows SDK does not include a .NET Framework Redistributable Package. Windows 7 Beta includes .NET Framework 3.5 SP1. Windows Vista and Windows Server 2008 include .NET Framework 3.0.
Users running Windows Server 2003 and Windows XP must install the .NET Framework 3.0 or 3.5 SP1 to run and develop .NET Framework applications. Some samples and tools included in the Windows SDK also require you to install .NET Framework 3.5 SP1.
Along with content that ships in the Windows SDK, Microsoft offers additional free developer tools and resources that you might find helpful, including:
· Debugging Tools for Windows can be used to debug drivers, applications, and services on systems running Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 as well as for debugging the operating system itself. Versions of the Debugging Tools for Windows package are available for 32-bit x86, native Intel Itanium, and native x64 platforms.
· LUA Buglight™ is a tool to help both developers and IT professionals (sysadmins) identify the specific causes of admin-permissions issues (LUA bugs) in desktop applications running on Windows XP, Windows Server 2003, or Windows Vista. Once the specific causes have been identified, the bugs can more easily be resolved by fixing the app's source code, or by making configuration changes, allowing the app to work correctly for non-admin users.
· Microsoft .NET Framework 3.0 is Microsoft's managed code programming model building applications on Windows clients, servers, and mobile or embedded devices. It combines the power of the .NET Framework 2.0 with four new technologies: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), Windows Workflow Foundation (WF), and Windows CardSpace (WCS, formerly InfoCard). The .NET Framework 3.0 ships with Windows Vista and Windows Server 2008.
· Microsoft .NET Framework 3.5 SP1 is the latest update of the .NET Framework, and contains many new features that are compatible with both .NET Framework 2.0 and .NET Framework 3.0. The .NET Framework 3.5 SP1 includes several fixes for .NET Framework 2.0 3.0, and 3.5.
· Microsoft Visual Studio Express is a set of free, lightweight and easy-to-use tools for the hobbyist, novice, and student developer.
· Microsoft Windows PowerShell™ command-line shell and scripting language helps IT Professionals achieve greater productivity. Using a new admin-focused scripting language, more than 130 standard command-line tools, and consistent syntax and utilities, Windows PowerShell allows IT professionals to more easily control system administration and accelerate automation. More information on Windows PowerShell is available from the PowerShell Team Blog and the Windows PowerShell Technology Center.
· Visual Studio 2005 extensions for .NET Framework 3.0 (Windows Workflow Foundation) provides developers with support for building workflow-enabled applications using Windows Workflow Foundation.
· Windows Server 2008 Developer Center is the official site about development and management of applications on the Windows Server 2008 platform. The Developer Center includes product information, news, tools, and code samples.
· Windows SDK Developer Center is the official site about development using the Windows SDK and provides information about the SDKs and links to the Windows SDK Blog, Forum, online release notes and other resources.

Using Post Build Step Event.

When developing with many binary objects. like a dll.

After build, we should copy these files to specify folder.

Because it'll work correctly on condition that dll's same designated position.

It's reall tedious and bothering task.

If you know a "Copy" command , you do not need to do this task.

On Visual Studio(since VS6), we can add command that copy some file to specify position,

after build.

On project property page(ALT+F7), Configuration Properties>>Build Events>>Post Build Evnet" add following lines on Command Line.

Copy "[Source]" "[Destination]"

EX>> If you want to copy "D:\test\test.dll" to "D:\BIN\test,dll", add folling lines on Command Line.

Copy "D:\test\test.dll" "D:\BIN\test,dll"

After setting applied and build, You will see a "Copy success" message on a output window.

Virtual PC error loading existing image after re - install a virtual PC

After re-install a Virtual PC, You'll be meet an error message when loading existing image.
Error message is "Your Virtual PC does not compatible with this virtual PC image."

You can solve this problem by deleting a " [VPC_Image_Name].vsv" file located in Virtual PC Image folder.

Use unary_function when delete objet in STL container.

This post copied from Effective STL.
Usually, many developer still delete object in STL container via iterating container and delete.
This method possibility makes exceptions and not effective way for STL.
From now on, use unary_function with for_each.

template <typename T>
class ContainerDeallocator : unary_function<T, void>
{
public:
void operator () (const T* ptr) const
{
delete ptr;
}
};



vector<int*> v1;
v1.resize(10);
v1[0] = new int(10);
v1[1] = new int(18);
v1[2] = new int(67);
v1[3] = new int(5);

for_each(v1.begin(), v1.end(), ContainerDeallocator<int>());

It's more pretty than using iterator.

Reference : Effective STL -Meyers-