to hack or not to hack...

Well I got some answers to using .Net Framework 2.0 on VS2003.  Aside from the great suggestions posted on my blog the other day, most people seem to have the opinion that VS2003 is not going to be forward compatible without a great deal of hacking.

So that leaves the question, to hack or not to hack.  The rest of my team seems to be ok with upgrading to VS2005 and I guess I don't have any problem with it except for one question that comes up whenver I think about it...is it wise to develop a library for use by a pretty large group with a beta development tool?  I mean it's my teams responsibility to make sure this library is stable...I guess there shouldn't be any problem with upgrading...I mean any problems that "could" happen we'll catch long before it's released to the rest of the group.  At least I don't think there's anything that could happen aside from general coding errors that could trickle down to the general users of our library...not that I can think of anyway. 

So here's to keeping the fingers crossed and hoping nothing bad happens.  ;)