I don’t believe that these warnings are an issue. Most of them are complaining
that types and interfaces under the Microsoft.Vsa namespace are obsolete. This
namespace provides functionality for compiling and running scripts (VBScript,
Javascript, …etc) at run time, which the DynamicDOM does NOT support right now.

However, you’re getting the warnings because the code that supports running
scripts in DynamicDOM does exist, but not used. Originally, I added the ability
to embed JavaScript functions inside XRules files using the <script> element to
do things that XPath doesn’t support. However, this feature is not well tested
yet, and therefore it’s disabled.

The other warnings are about using old classes for handling XML Schemas.
Again, this is not a problem (yet) because these classes still exist and work.
However, I think I should replace them before .NET 3.0 is out (just in case).

Regards,
Waleed




>
> From: "w1lls1d" <w1lls1d@...>
> Date: 2007/01/04 Thu AM 11:16:34 EST
> To: xrules@yahoogroups.com
> Subject: [xrules] Being deprecated in Visual Studio 2005
>
> To begin -- XRules is some very useful and cool stuff!
>
> I used TortoiseSVN to get the latest source from tigris.org and
> compiled (I use VS 2005 and was interested in getting the source
> formatted to that environment). Solution compiled without errors, but
> saw lots of warnings similar to -- 'Microsoft.whatever.whatever' is
> obsolete: 'Use of this type is not recommended because it is being
> deprecated in Visual Studio 2005...'
>
> Are there concerns with these?
>
>
>