• Restore file, folders or entire hard drive;
• Select backup files or hard drive;
• Compare original files to backup files;
• Migrate files or folders to another location;
• Create bootable CD/DVD;
• Migrate or restore file, folders or entire hard drive;
• Create CD labels;
• View computer system information and hard drive details;
• Export to CD/DVD or file;
• Set restore point;
• View screen shots, capture selected screen shots and save screen shots;
• Schedule backup;
• Export backup jobs to file;
• Test and analyze hard drive or media types;
• Select from several themes;
• Create CD labels;

Daily media news, MP3, New MP3 Players, gadgets, photo, software, cell phones and more.



PhoneGap: Think of it as a bridge between your web applications and native mobile apps (iPhone, BlackBerry, Android etc.), which will allow you to leverage your existing web application technologies and include rich mobile content. Simply put, you can build a native mobile application using technologies you already know like Java, Objective-C, HTML 5 etc. Once your application is built, you can use PhoneGap to wrap the native components, and communicate to the native components. All of this can be done in one application, without needing to build a native app for every platform.

PhoneGap consists of a JavaScript layer and an Objective-C layer, and it looks like an automated wrapper of the native API’s. The architecture looks like this:

Your application will be hosted inside a web-accessible HTML 5 document.

When a user loads your application, PhoneGap will load the native API’s. These are the three main components of PhoneGap:

The core JavaScript library to handle the native API’s, and interface with your existing web technologies.

The native API’s, which are part of the native API’s available for each platform.

The native objects you need to wrap.

But what is different in PhoneGap is that there is a native API’s API that PhoneGap supports:


Accelerometer API’s call your back-end web service when the application is running on mobile devices. You can use this API to get the devices orientation eea19f52d2


Microsoft Visual Studio Team System Database Edition GDR is a new version of the Team System Database Edition that is tailored specifically for SQL Server 2008 and its relational databases. In addition to providing support for SQL Server 2008 database projects, this release incorporates many previously released Power Tools as well as several new features. The new features include distinct Build and Deploy phases, Static Code Analysis and improved integration with SQL CLR projects.
Database Edition no longer requires a Design Database. Therefore, it is no longer necessary to install an instance of SQL Express or SQL Server prior to using Database Edition.
SQL Server Support
SQL Server 2008
All new data types:
– Intrinsic (date, datetime2, datetimeoffset, time)
– Built-in SQL CLR types (geography, geometry, hierarchyid)
– Merge, table parameters,
SQL Server Configuration Options
– Server option settings will be verified prior to deployment or set during deployment
– Additional 1st Class Object Type Support
– Rules, defaults, Asymmetric keys, symmetric keys, certificates, �
Server Projects
– Server objects and option settings may be implemented in a separate Server Project
– This enables a team to define a standard a configuration for their SQL servers and reference it from their Database Projects
Partial projects
– Allowing code sharing between projects by including files from a different project, where the code is included as-is from the originating project and the source code control ownership remains with the originating project
– This enables code reuse and single sourcing while having a single deployment unit
Composite projects
– References to other database projects or.dbschema files that contribute to the same deployment unit.
– This enables the separation of development roles and responsibilities and composition of Databases using multiple projects.
Single sourcing of external artifacts
SQL-CLR references allow the user to create a reference to a SQL-CLR project or SQL-CLR assembly. This automatically becomes an ASSEMBLY type in the Database Project
Build and Deploy
The Build process now produces a separate portable schema output that is fed in to a redistributable deployment engine
A redistributable deployment engine. For example, to implement a setup application that deploys the Database Project.
Preservation of Intent
– Enables the deployment of refactoring changes as intended by the user (renames are deployed as renames not as drop/add statements for example)
New Refactoring Operations
Wildcard Expansion
Move Sche