we are looking to migrate to TFS. I have been tasked w/ getting this whole thing up and running. Our cash cow product is a (set of) web application(s). We are unable to migrate this product to 2.0 so I'm looking to see what there is in the way of custom integration for this piece. I can see using the TFS:SCM for normal .net 1.1 projects hosted inside TFS, but because someone thought it would be a great idea to totally change projects in 2.0 for asp.net to not have a project file, and switch around the way the project is laid out end to end, its going to be really hard for us to migrate our current codebase from vs.net 2003 into TFS.
the normal processes (as far as I can see) is to either migrate the 1.1 project into the new format, and create a custom build for the 1.1 framework. this allows active development of non-asp.net projects from within 2005, were we can make use of all the team system features.
If we use TFS for our SCM on our web projects, we loose all "integration" capabiliites that 2005 provides us.
I understand the reason why you didnt make TFS compat. w/ 1.1-2003 (drive sales of 2005 product line), but because of the overhaul in the way asp.net is structured in 2005, it makes it really hard to support older projects from within that framework.
Is it possible (and I'm going way out on a limb here) to extend the TFS SCM and work items type stuff to work inside 2003? I understand this would be a major task if at all possible, and would probably cost us more than we'd be willing to spend to do so, but my interest is peeked, and I'm really wanting to be able to come back to my superiors with a feasible solution end to end, with regards to total migration to TFS.

Thanks.
--Steve