Can we still have System.ComponentModel.Components in the design surface of ASP.NET? I have a bit of code that makes sense to encapsulate into a Component that doesn't rely on Windows or ASP.NET, but requires designer support. Basically I want to persist view configuration in a user-friendly way at compile-time (leaving no potential to bloat ViewState) and make my design Component portable across platforms (Windows/Web).

The problem is that the Component I made doesn't show up in the toolbox when I add it there, and I'm worried that Component support in ASP.NET 2.0 got yanked out.

Say it ain't so!

Bump!

Anyone know what's going on with this? I still don't know if it's the new IDE or if I'm just missing something.

In googling related info, I happened on the debate over whether or not the xxDataSource controls should have been implemented as Components (which would make sense to me since a proper implementation could allow them to be used with Windows code).