when to split a library

I am continually build a class library. I include it in all the solutions I work on and anything that comes up that I write a class or function for that I think can be reused I make it reusable and section off into an apropreate Namespace. So I have a root namespace Ezekiel with namespaces Data, Web and Windows right now. There are also some c++ librays but they ae already seprate.

Anyway, what I'm wondering is should I split the web and windows namespace out into seperate projects/libraries from the root and data?

I would only if each namespace is getting pretty big or if deployment is becoming problematic otherwise I wouldn't.

If they are Windows Forms specific functions, then what purpose do they have in a Web app and vice versa? I would split them only for better code seperation. You don't need them there, so why have them.

The library isn't very large at least not compared to some of Microsoft's but I agree with Hellswraith MS Doesn't have Windows.Forms in the System Namespace or Data or Web. I think I may split it. The only reason I haven't yet is because it's easier to manage in one project, but I could just use a solution to manage it instead.....