VS.Net Search & Replace

time to read 1 min | 84 words

Can someone explain to me why the VS.Net S&R doesn't use the standard regular expressions library that ships with .Net? I can understand the need to create one when it didn't exist, but why force us to learn both how VS.Net S&R regex engine works, and the standard .Net one. There are some very cool stuff there that I use all the time (:i, for instance), but it would be easy to add it the the engine just for this, why fork it? Historical reasons?