A few weeks ago I posted a question on the MSDN forum about a rather strange bug.

Although nobody seemed to know the answer, we were able to find the problem.

When we opened the view all site content on a sharepoint website, we noticed that our custom document library showed 3 times on the screen. Each link redirected to the same list.

When we created the custom views in the schema.xml, we didn't change the DefaultView="TRUE" to FALSE.

It seems that when more than 1 view is set as DefaultView, the list is showed more than once in the view all site content page.

when we changed the DefaultView to FALSE and left only A View as default.The other 'ghost' document libraries dissapeared.

string const string SMTPADDRESS= "stp.mail.emea.microsoftonline.com";

try
{
  MailMessage mail = new MailMessage();
  mail.from = new MailAddress("from@company.be");
  mail.To.Add("customer1@company.be");
  mail.To.Add("customer2@company.be");
  mail.Subject = "Mail sent using BPOS SMTP relay";
  mail.Body= "This mail has been sent using ssl";

  SmtpClient smtpServer = new SmtpClient(SMTPADDRESS)
  smtpServer.Port = 587;
  //TODO: put these configurations in config files.
  smtpServer.Credentials = new System.Net.NetworkCredentials("from@company.be","password");
  smtpServer.EnableSsl = true;
  smtpServer.Send(mail);
  return true;
}
catch(Exception ex)
{
  return ex.ToString();
}

http://msdn.microsoft.com/en-us/library ... ssage.aspx
http://msdn.microsoft.com/en-us/library ... lient.aspx

I was chocked that I didn't knew the answer to this question immediately, offcourse we all know the result of putting someone in CC or BCC... :)

so here we go:

Cc
Cc is shorthand for Carbon copy . If you add a recipient's name to this box in an Outlook e-mail message, a copy of the message is sent to that recipient, and the recipient's name is visible to other recipients of the message.

Bcc
Bcc is shorthand for Blind carbon copy . If you add a recipient's name to this box in a mail message, a copy of the message is sent to that recipient, and the recipient's name is not visible to other recipients of the message. If the Bcc box isn't visible when you create a new message, you can add it.

When binding a replicator from within another replicator, you will discover the following behaviour:

We have 2 replicators:
ParentReplicator & ChildReplicator

We have 4 roles:
role1,role2,role3 and role4

We have 5 users:
user1,user2,user3,user4 and user 5

each user is connected to a role in a dictionnary<Role,list<User>>

role1 has 2 users: user1 & user 2
role2 has 1 user: user 3
role3 has 1 user: user 4
role4 has 1 user: user 5

We want to iterate through each role and create a task for each user in this role.

through the designer we bind the initialchilddata property to List<Roles> Roles property

using code we capture the ParentReplicator_ChildIntialized
event and execute this code:




The result is this:

Role 1
Role 2
- user 1
- user 3
Role 3
- user 2

...

SO it seems like the ChildData is only set the next iteration?...

The reason for this behaviour is because we are settings the InitialChildData on the wrong object, the object we are using is living in another context.


Use:

//use the control in this context
ReplicatorActivity rep = e.Activity.GetActivityByName(PanretReplicator.Name, true) as ReplicatorActivity;
rep.InitialChildData = users.Select(u => u.Sid).ToList();

here we go!


Conclusion: ALWAYS use the sender or e.Activity to get your childactivities to avoid these unhappy behaviour...


read more:
Pro WF: Windows Worklfow Foundation Pages
Very nice post that pushed me in the right direction

Good luck;)
</tom>

Yesterday evening I attented an interesting session, with a lot of people, from Brad Abrams (Program Manager at Microsoft and author of the book Framework Design Guidelines ).

Most of the things he told were already known in a technical point of view, but what made it so interesting is the reason why some things are built in the .NET framework.

When to use a property in stead of a method, after all... A property is a method?!

When to use an extention method combined with a namespace and add overload methods to an interface or to manage dependencies?

Why shouldn't I define extension methods on the System.Object? ;)

And my favourite:
Do as little as possible now (but no less) to ensure room for extensibility in the future

How to achive the secret of great productivity?

did I get your attention?

Brad has provided us with the slides which can be downloaded from here

always nice to learn some new things :)