SSIS Expression limitation

I faced the issue of mails not getting sent from the Email module which had an SSIS Package. I imported the troubled emails to my dev machine and debugged to find out that the SSIS has a limitation with the expression. A string expression should be less than 4000 characters!
So some of my automated emails has a messagebody > 4000, hence the issue.
SSIS allows direct entry of MessageBody through variable.
So I solved the problem by making SSIS read the meesagebody from a variable.

Visual Studio schema compare Project disabled

I came across an issue in Visual Studio 2010, the Project choice became disabled in the Schema compare.
I think the reason was that Visual Studio was 'confused'
I had 2 DB projects with same name (branches in Source Control)
Solution: Go to Import and Export settings in Tools and Click Reset all Settings

Cloning the unclonable

There can and will be objects without the implementation of clone, but you have to clone it, you may not have the rights to implement clone for that object, may be its a vendor object, then what you do.
You may try copying property by property, which is laborious.
Else you can try serialize and deserialize, serialize the object to an xml and then deserialize it into another object and its cloned!