Deserialization failed: File or assembly name Microsoft.ReportingServices.Interfaces not f

Hello,
I just installed Vault Source Control on my machine. I then opened a
Reporting Services project with rdl's in it. Every RDL that is currently in
source control opens with this error
"Deserialization failed: File or assembly name
Microsoft.ReportingServices.Interfaces, or one of its dependencies, was not
found."
If I open another instance of the MSIDE without Vault (locally) and open a
different RDL it works fine. Is this an issue with the source control or
with the way it opens the file?
Any help will be appreciated. Need to get this solved.
PonnuI think it has to do with the way the add-in is written. Some add-ins turn
on shadow-copy, which plays havoc with the report designer as our assemblies
aren't located in the VS shared location. You might be able to copy the
report designer assemlies into the IDE directory. Not sure if you can
configure the add-in not to shadow copy.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
"Ponnurangam" <ponnurangam@.trellisys.net> wrote in message
news:uZiORNloEHA.1160@.tk2msftngp13.phx.gbl...
> Hello,
> I just installed Vault Source Control on my machine. I then opened a
> Reporting Services project with rdl's in it. Every RDL that is currently
> in
> source control opens with this error
> "Deserialization failed: File or assembly name
> Microsoft.ReportingServices.Interfaces, or one of its dependencies, was
> not
> found."
> If I open another instance of the MSIDE without Vault (locally) and open a
> different RDL it works fine. Is this an issue with the source control or
> with the way it opens the file?
> Any help will be appreciated. Need to get this solved.
> Ponnu
>