Should I blame this problem on RS?

Michael,

I think your problem may be connected with ReSharper, because we also
use 'Microsoft.VisualStudio.Shell.Interop' assembly. This assembly is copied
to the PrivateAssemblies folder in the VS installation (on my machine this
is
"C:\Microsoft Visual Studio .NET 2003\Common7\IDE\PrivateAssemblies\").
PrivateAssemblies folder is included into the VS.NET private probing path
(where
the CLR attempts to load assemblies from). In your scenario it seems that
when you create a new report project, VS.NET tries to load
'Microsoft.VisualStudio.Shell.Interop'
assembly needed by reporting services, and fails, because the version of the
assembly copied
by ReSharper does not match that required by reporting services.

Could you please describe where SQL Server reporting services installs its
files on your machine?
This would help us to figure out how to resolve this situation.

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1e672$tq6$1@is.intellij.net...

I run a pretty stock install of VS.NET 2003. I've also installed RS v.66.
Today, I installed SQL Server reporting services which comes with a report
designed integrated with VS.NET. Whenever I try to create a new report
project, I get this error:

>

The located assembly's manifest definition with name
'Microsoft.VisualStudio.Shell.Interop' does not match the assembly
reference.

>

So, my unvalidated suspicion is that it may have something to do with
ReSharper (given how ReSharper most likely plugs into the IDE shell
interop). Could that be the case or am I way off?

>

Thanks!
-Michael

>
>

Yup, thats exactly what happens. Reporting Services installs its DLL's
(including the shell dll which is a version newer than the one you are
using) into C:\Program Files\Microsoft SQL Server\80\Tools\Report Designer.
Please, please, see if you can resolve this: I need Reporting Services, but
I want ReSharper back!!! :)

Thanks!
-Michael

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1g22b$4na$1@is.intellij.net...

Michael,

>

I think your problem may be connected with ReSharper, because we also
use 'Microsoft.VisualStudio.Shell.Interop' assembly. This assembly is

copied

to the PrivateAssemblies folder in the VS installation (on my machine this
is
"C:\Microsoft Visual Studio .NET 2003\Common7\IDE\PrivateAssemblies\").
PrivateAssemblies folder is included into the VS.NET private probing path
(where
the CLR attempts to load assemblies from). In your scenario it seems that
when you create a new report project, VS.NET tries to load
'Microsoft.VisualStudio.Shell.Interop'
assembly needed by reporting services, and fails, because the version of

the

assembly copied
by ReSharper does not match that required by reporting services.

>

Could you please describe where SQL Server reporting services installs its
files on your machine?
This would help us to figure out how to resolve this situation.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1e672$tq6$1@is.intellij.net...

I run a pretty stock install of VS.NET 2003. I've also installed RS

v.66.

Today, I installed SQL Server reporting services which comes with a

report

designed integrated with VS.NET. Whenever I try to create a new report
project, I get this error:

>

The located assembly's manifest definition with name
'Microsoft.VisualStudio.Shell.Interop' does not match the assembly
reference.

>

So, my unvalidated suspicion is that it may have something to do with
ReSharper (given how ReSharper most likely plugs into the IDE shell
interop). Could that be the case or am I way off?

>

Thanks!
-Michael

>
>

>
>

Michael,

it seems that ReSharper installer uselessly copies the following assemblies
into PrivateAssemblies folder:

Microsoft.VisualStudio.Shell.Interop.dll,
Microsoft.VisualStudio.OLE.Interop.dll,
Microsoft.VisualStudio.TextManager.Interop.dll

In fact, these assemblies are located in the Global Assembly Cache. Could
you please try to delete abovementioned
files from your PrivateAssemblies folder and look how ReSharper and
reporting services will work?

Please let us know about the resutls.

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1g7p0$8au$1@is.intellij.net...

Yup, thats exactly what happens. Reporting Services installs its DLL's
(including the shell dll which is a version newer than the one you are
using) into C:\Program Files\Microsoft SQL Server\80\Tools\Report

Designer.

Please, please, see if you can resolve this: I need Reporting Services,

but

I want ReSharper back!!! :)

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1g22b$4na$1@is.intellij.net...

Michael,

>

I think your problem may be connected with ReSharper, because we also
use 'Microsoft.VisualStudio.Shell.Interop' assembly. This assembly is

copied

to the PrivateAssemblies folder in the VS installation (on my machine

this

is
"C:\Microsoft Visual Studio .NET 2003\Common7\IDE\PrivateAssemblies\").
PrivateAssemblies folder is included into the VS.NET private probing

path

(where
the CLR attempts to load assemblies from). In your scenario it seems

that

when you create a new report project, VS.NET tries to load
'Microsoft.VisualStudio.Shell.Interop'
assembly needed by reporting services, and fails, because the version of

the

assembly copied
by ReSharper does not match that required by reporting services.

>

Could you please describe where SQL Server reporting services installs

its

files on your machine?
This would help us to figure out how to resolve this situation.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1e672$tq6$1@is.intellij.net...

I run a pretty stock install of VS.NET 2003. I've also installed RS

v.66.

Today, I installed SQL Server reporting services which comes with a

report

designed integrated with VS.NET. Whenever I try to create a new report
project, I get this error:

>

The located assembly's manifest definition with name
'Microsoft.VisualStudio.Shell.Interop' does not match the assembly
reference.

>

So, my unvalidated suspicion is that it may have something to do with
ReSharper (given how ReSharper most likely plugs into the IDE shell
interop). Could that be the case or am I way off?

>

Thanks!
-Michael

>
>

>
>

>
>

I uninstalled RS 66 and deleted the Private Assemblies folder when I was
troubleshooting this problem. When I went to install RS 67, I got the
following error while the install was running "registrar.exe":

-

Error
-

An exception has occurred during assembly copying.
Details:System.IO.DirectoryNotFoundException: Could not find a part of the
path "C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies\ReSharper.dll".

at System.IO.__Error.WinIOError(Int32 errorCode, String str)

at System.IO.File.InternalCopy(String sourceFileName, String
destFileName, Boolean overwrite)

at System.IO.File.Copy(String sourceFileName, String destFileName,
Boolean overwrite)

at Registrar.Main(String[] args)
-

OK
-

This was followed by a few more assemblies that could not be copied. After I
OK'd out of the error messages, the command prompt closed and the installer
reported that ReSharper was successfully installed (clearly NOT correct).

I then manually created the PrivateAssemblies folder and re-ran the
installer and picked the "Repair" option. The install ran through to
completion w/o errors and the files were placed in the PrivateAssemblies
folder. I started VS.NET and got this error:

-

Microsoft Development Environment
-

The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to load or
caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it again.

Error Message: The system cannot find the file specified.


Error number: 80070002
-

Yes No
-

I selected "No", quit out of VS.NET and un-installed ReSharper.
Interestingly, the un-installer did not remove the files from the
PrivateAssemblies folder.

I ran the installer again, and again it went through w/o errors. I restarted
VS.NET and got the same error again.

Any idea what file it seems to be missing?

Thanks!
-Michael

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1hr7k$o61$1@is.intellij.net...

Michael,

>

it seems that ReSharper installer uselessly copies the following

assemblies

into PrivateAssemblies folder:

>

Microsoft.VisualStudio.Shell.Interop.dll,
Microsoft.VisualStudio.OLE.Interop.dll,
Microsoft.VisualStudio.TextManager.Interop.dll

>

In fact, these assemblies are located in the Global Assembly Cache. Could
you please try to delete abovementioned
files from your PrivateAssemblies folder and look how ReSharper and
reporting services will work?

>

Please let us know about the resutls.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1g7p0$8au$1@is.intellij.net...

Yup, thats exactly what happens. Reporting Services installs its DLL's
(including the shell dll which is a version newer than the one you are
using) into C:\Program Files\Microsoft SQL Server\80\Tools\Report

Designer.

Please, please, see if you can resolve this: I need Reporting Services,

but

I want ReSharper back!!! :)

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1g22b$4na$1@is.intellij.net...

Michael,

>

I think your problem may be connected with ReSharper, because we also
use 'Microsoft.VisualStudio.Shell.Interop' assembly. This assembly is

copied

to the PrivateAssemblies folder in the VS installation (on my machine

this

is
"C:\Microsoft Visual Studio .NET

2003\Common7\IDE\PrivateAssemblies\").

PrivateAssemblies folder is included into the VS.NET private probing

path

(where
the CLR attempts to load assemblies from). In your scenario it seems

that

when you create a new report project, VS.NET tries to load
'Microsoft.VisualStudio.Shell.Interop'
assembly needed by reporting services, and fails, because the version

of

the

assembly copied
by ReSharper does not match that required by reporting services.

>

Could you please describe where SQL Server reporting services installs

its

files on your machine?
This would help us to figure out how to resolve this situation.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1e672$tq6$1@is.intellij.net...

I run a pretty stock install of VS.NET 2003. I've also installed RS

v.66.

Today, I installed SQL Server reporting services which comes with a

report

designed integrated with VS.NET. Whenever I try to create a new

report

project, I get this error:

>

The located assembly's manifest definition with name
'Microsoft.VisualStudio.Shell.Interop' does not match the assembly
reference.

>

So, my unvalidated suspicion is that it may have something to do

with

ReSharper (given how ReSharper most likely plugs into the IDE shell
interop). Could that be the case or am I way off?

>

Thanks!
-Michael

>
>

>
>

>
>

>
>

Michael,

first, I don't think it's a good idea to delete the entire Private
Assemblies folder - this folder
is a part of the VS directory hierarchy, and many applications (VS.NET
itself and ReSharper including)
rely on it to exist.

Could you please provide us with the following information:

1) What files are currently in your PrivateAssemblies and PublicAssemblies
folders
2) What assemblies from "Microsoft.VisualStudio.*.Interop.dll" family (and
what versions) are located in
the GAC on your system
(The GAC typically live in "C:\WINDOWS\assembly\" and includes several
subfolders).

Sorry for taking your time, but this information is really important for us
to understand how to cope with
this problem. We'll probably include a collector of such infromation into
the ReSharper installer.

Thanks in advance,
Dmitry

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1ivr5$rai$1@is.intellij.net...

I uninstalled RS 66 and deleted the Private Assemblies folder when I was
troubleshooting this problem. When I went to install RS 67, I got the
following error while the install was running "registrar.exe":

>

---------------------------
Error
---------------------------
An exception has occurred during assembly copying.
Details:System.IO.DirectoryNotFoundException: Could not find a part of the
path "C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies\ReSharper.dll".

>

at System.IO.__Error.WinIOError(Int32 errorCode, String str)

>

at System.IO.File.InternalCopy(String sourceFileName, String
destFileName, Boolean overwrite)

>

at System.IO.File.Copy(String sourceFileName, String destFileName,
Boolean overwrite)

>

at Registrar.Main(String[] args)
---------------------------
OK
---------------------------

>

This was followed by a few more assemblies that could not be copied. After

I

OK'd out of the error messages, the command prompt closed and the

installer

reported that ReSharper was successfully installed (clearly NOT correct).

>

I then manually created the PrivateAssemblies folder and re-ran the
installer and picked the "Repair" option. The install ran through to
completion w/o errors and the files were placed in the PrivateAssemblies
folder. I started VS.NET and got this error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to load or
caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

I selected "No", quit out of VS.NET and un-installed ReSharper.
Interestingly, the un-installer did not remove the files from the
PrivateAssemblies folder.

>

I ran the installer again, and again it went through w/o errors. I

restarted

VS.NET and got the same error again.

>

Any idea what file it seems to be missing?

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1hr7k$o61$1@is.intellij.net...

Michael,

>

it seems that ReSharper installer uselessly copies the following

assemblies

into PrivateAssemblies folder:

>

Microsoft.VisualStudio.Shell.Interop.dll,
Microsoft.VisualStudio.OLE.Interop.dll,
Microsoft.VisualStudio.TextManager.Interop.dll

>

In fact, these assemblies are located in the Global Assembly Cache.

Could

you please try to delete abovementioned
files from your PrivateAssemblies folder and look how ReSharper and
reporting services will work?

>

Please let us know about the resutls.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1g7p0$8au$1@is.intellij.net...

Yup, thats exactly what happens. Reporting Services installs its DLL's
(including the shell dll which is a version newer than the one you are
using) into C:\Program Files\Microsoft SQL Server\80\Tools\Report

Designer.

Please, please, see if you can resolve this: I need Reporting

Services,

but

I want ReSharper back!!! :)

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1g22b$4na$1@is.intellij.net...

Michael,

>

I think your problem may be connected with ReSharper, because we

also

use 'Microsoft.VisualStudio.Shell.Interop' assembly. This assembly

is

copied

to the PrivateAssemblies folder in the VS installation (on my

machine

this

is
"C:\Microsoft Visual Studio .NET

2003\Common7\IDE\PrivateAssemblies\").

PrivateAssemblies folder is included into the VS.NET private probing

path

(where
the CLR attempts to load assemblies from). In your scenario it seems

that

when you create a new report project, VS.NET tries to load
'Microsoft.VisualStudio.Shell.Interop'
assembly needed by reporting services, and fails, because the

version

of

the

assembly copied
by ReSharper does not match that required by reporting services.

>

Could you please describe where SQL Server reporting services

installs

its

files on your machine?
This would help us to figure out how to resolve this situation.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1e672$tq6$1@is.intellij.net...

I run a pretty stock install of VS.NET 2003. I've also installed

RS

v.66.

Today, I installed SQL Server reporting services which comes with

a

report

designed integrated with VS.NET. Whenever I try to create a new

report

project, I get this error:

>

The located assembly's manifest definition with name
'Microsoft.VisualStudio.Shell.Interop' does not match the assembly
reference.

>

So, my unvalidated suspicion is that it may have something to do

with

ReSharper (given how ReSharper most likely plugs into the IDE

shell

interop). Could that be the case or am I way off?

>

Thanks!
-Michael

>
>

>
>

>
>

>
>

>
>

Dmitry, thanks for following up.

At first I did not delete the PrivateAssemblies folder, I merely renamed it.
However, it didnt look like it was needed for anything VS.NET or Reporting
Services were doing, so I deleted the backup. Then I went through all the
steps to install RS 67 that I described in a previous post.

Righ now my PrivateAssemblies folder contains the following files:
CookComputing.XmlRpc.dll
JetBrainsShared.dll
Microsoft.VisualStudio.VSIP.Helper.dll
ReSharper.dll
ReSharper.pdb
ReSharperPkgLib.dll
Services.dll
Services.pdb

PublicAssemblies:
extensibility.dll
MCppCodeDomParser.dll
MCppCodeDomProvider.dll
Microsoft.VisualStudio.VCCodeModel.dll
Microsoft.VisualStudio.VCProject.dll
Microsoft.VisualStudio.VCProjectEngine.dll
readme.txt
VSLangProj.dll
VSLangProj2.dll
VsMacroHierarchyLib.dll

GAC:
none that match your query


I went and looked at the VS.NET install disc and found that by default the
PrivateAssemblies folder contains two files:
msatinterop.dll
readme.txt

I copied those two files into the PrivateAssemblies folder and installed
ReSharper 67 again. Started VS.NET and (again) got the following error:

-

Microsoft Development Environment
-

The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to load or
caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it again.

Error Message: The system cannot find the file specified.


Error number: 80070002
-

Yes No
-

The only file I found that matches the dll "family" you were looking for,
either on my hard drive or on the VS.NET setup disc, was
"Microsoft.VisualStudio.Converters.Interop.dll". That file lives in
"C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE".

Any other ideas?

Thanks!
-Michael


"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1k8ug$p7n$1@is.intellij.net...

Michael,

>

first, I don't think it's a good idea to delete the entire Private
Assemblies folder - this folder
is a part of the VS directory hierarchy, and many applications (VS.NET
itself and ReSharper including)
rely on it to exist.

>

Could you please provide us with the following information:

>

1) What files are currently in your PrivateAssemblies and PublicAssemblies
folders
2) What assemblies from "Microsoft.VisualStudio.*.Interop.dll" family (and
what versions) are located in
the GAC on your system
(The GAC typically live in "C:\WINDOWS\assembly\" and includes several
subfolders).

>

Sorry for taking your time, but this information is really important for

us

to understand how to cope with
this problem. We'll probably include a collector of such infromation into
the ReSharper installer.

>

Thanks in advance,
Dmitry

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1ivr5$rai$1@is.intellij.net...

I uninstalled RS 66 and deleted the Private Assemblies folder when I was
troubleshooting this problem. When I went to install RS 67, I got the
following error while the install was running "registrar.exe":

>

---------------------------
Error
---------------------------
An exception has occurred during assembly copying.
Details:System.IO.DirectoryNotFoundException: Could not find a part of

the

path "C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies\ReSharper.dll".

>

at System.IO.__Error.WinIOError(Int32 errorCode, String str)

>

at System.IO.File.InternalCopy(String sourceFileName, String
destFileName, Boolean overwrite)

>

at System.IO.File.Copy(String sourceFileName, String destFileName,
Boolean overwrite)

>

at Registrar.Main(String[] args)
---------------------------
OK
---------------------------

>

This was followed by a few more assemblies that could not be copied.

After

I

OK'd out of the error messages, the command prompt closed and the

installer

reported that ReSharper was successfully installed (clearly NOT

correct).

>

I then manually created the PrivateAssemblies folder and re-ran the
installer and picked the "Repair" option. The install ran through to
completion w/o errors and the files were placed in the PrivateAssemblies
folder. I started VS.NET and got this error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to load or
caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it

again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

I selected "No", quit out of VS.NET and un-installed ReSharper.
Interestingly, the un-installer did not remove the files from the
PrivateAssemblies folder.

>

I ran the installer again, and again it went through w/o errors. I

restarted

VS.NET and got the same error again.

>

Any idea what file it seems to be missing?

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1hr7k$o61$1@is.intellij.net...

Michael,

>

it seems that ReSharper installer uselessly copies the following

assemblies

into PrivateAssemblies folder:

>

Microsoft.VisualStudio.Shell.Interop.dll,
Microsoft.VisualStudio.OLE.Interop.dll,
Microsoft.VisualStudio.TextManager.Interop.dll

>

In fact, these assemblies are located in the Global Assembly Cache.

Could

you please try to delete abovementioned
files from your PrivateAssemblies folder and look how ReSharper and
reporting services will work?

>

Please let us know about the resutls.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1g7p0$8au$1@is.intellij.net...

Yup, thats exactly what happens. Reporting Services installs its

DLL's

(including the shell dll which is a version newer than the one you

are

using) into C:\Program Files\Microsoft SQL Server\80\Tools\Report

Designer.

Please, please, see if you can resolve this: I need Reporting

Services,

but

I want ReSharper back!!! :)

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in

message

news:c1g22b$4na$1@is.intellij.net...

Michael,

>

I think your problem may be connected with ReSharper, because we

also

use 'Microsoft.VisualStudio.Shell.Interop' assembly. This assembly

is

copied

to the PrivateAssemblies folder in the VS installation (on my

machine

this

is
"C:\Microsoft Visual Studio .NET

2003\Common7\IDE\PrivateAssemblies\").

PrivateAssemblies folder is included into the VS.NET private

probing

path

(where
the CLR attempts to load assemblies from). In your scenario it

seems

that

when you create a new report project, VS.NET tries to load
'Microsoft.VisualStudio.Shell.Interop'
assembly needed by reporting services, and fails, because the

version

of

the

assembly copied
by ReSharper does not match that required by reporting services.

>

Could you please describe where SQL Server reporting services

installs

its

files on your machine?
This would help us to figure out how to resolve this situation.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in

message

news:c1e672$tq6$1@is.intellij.net...

I run a pretty stock install of VS.NET 2003. I've also installed

RS

v.66.

Today, I installed SQL Server reporting services which comes

with

a

report

designed integrated with VS.NET. Whenever I try to create a new

report

project, I get this error:

>

The located assembly's manifest definition with name
'Microsoft.VisualStudio.Shell.Interop' does not match the

assembly

reference.

>

So, my unvalidated suspicion is that it may have something to do

with

ReSharper (given how ReSharper most likely plugs into the IDE

shell

interop). Could that be the case or am I way off?

>

Thanks!
-Michael

>
>

>
>

>
>

>
>

>
>

>
>

One more tidbit:

I copied "Microsoft.VisualStudio.Shell.Interop.dll" from the ReSharper
folder into the PrivateAssemblies folder and VS.NET started just fine and
ReSharper was working. Unfortunately, this causes Report Services to stop
working which brings me right back to square one. Well, maybe square two
since we now know the offending DLL and how ReSharper is not loading it when
it lives in the ReSharper folder.

Thanks!
-Michael


"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1l98d$87b$1@is.intellij.net...

Dmitry, thanks for following up.

>

At first I did not delete the PrivateAssemblies folder, I merely renamed

it.

However, it didnt look like it was needed for anything VS.NET or Reporting
Services were doing, so I deleted the backup. Then I went through all the
steps to install RS 67 that I described in a previous post.

>

Righ now my PrivateAssemblies folder contains the following files:
CookComputing.XmlRpc.dll
JetBrainsShared.dll
Microsoft.VisualStudio.VSIP.Helper.dll
ReSharper.dll
ReSharper.pdb
ReSharperPkgLib.dll
Services.dll
Services.pdb

>

PublicAssemblies:
extensibility.dll
MCppCodeDomParser.dll
MCppCodeDomProvider.dll
Microsoft.VisualStudio.VCCodeModel.dll
Microsoft.VisualStudio.VCProject.dll
Microsoft.VisualStudio.VCProjectEngine.dll
readme.txt
VSLangProj.dll
VSLangProj2.dll
VsMacroHierarchyLib.dll

>

GAC:
none that match your query

>
>

I went and looked at the VS.NET install disc and found that by default the
PrivateAssemblies folder contains two files:
msatinterop.dll
readme.txt

>

I copied those two files into the PrivateAssemblies folder and installed
ReSharper 67 again. Started VS.NET and (again) got the following error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to load or
caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

The only file I found that matches the dll "family" you were looking for,
either on my hard drive or on the VS.NET setup disc, was
"Microsoft.VisualStudio.Converters.Interop.dll". That file lives in
"C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE".

>

Any other ideas?

>

Thanks!
-Michael

>
>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1k8ug$p7n$1@is.intellij.net...

Michael,

>

first, I don't think it's a good idea to delete the entire Private
Assemblies folder - this folder
is a part of the VS directory hierarchy, and many applications (VS.NET
itself and ReSharper including)
rely on it to exist.

>

Could you please provide us with the following information:

>

1) What files are currently in your PrivateAssemblies and

PublicAssemblies

folders
2) What assemblies from "Microsoft.VisualStudio.*.Interop.dll" family

(and

what versions) are located in
the GAC on your system
(The GAC typically live in "C:\WINDOWS\assembly\" and includes several
subfolders).

>

Sorry for taking your time, but this information is really important for

us

to understand how to cope with
this problem. We'll probably include a collector of such infromation

into

the ReSharper installer.

>

Thanks in advance,
Dmitry

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1ivr5$rai$1@is.intellij.net...

I uninstalled RS 66 and deleted the Private Assemblies folder when I

was

troubleshooting this problem. When I went to install RS 67, I got the
following error while the install was running "registrar.exe":

>

---------------------------
Error
---------------------------
An exception has occurred during assembly copying.
Details:System.IO.DirectoryNotFoundException: Could not find a part of

the

path "C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies\ReSharper.dll".

>

at System.IO.__Error.WinIOError(Int32 errorCode, String str)

>

at System.IO.File.InternalCopy(String sourceFileName, String
destFileName, Boolean overwrite)

>

at System.IO.File.Copy(String sourceFileName, String destFileName,
Boolean overwrite)

>

at Registrar.Main(String[] args)
---------------------------
OK
---------------------------

>

This was followed by a few more assemblies that could not be copied.

After

I

OK'd out of the error messages, the command prompt closed and the

installer

reported that ReSharper was successfully installed (clearly NOT

correct).

>

I then manually created the PrivateAssemblies folder and re-ran the
installer and picked the "Repair" option. The install ran through to
completion w/o errors and the files were placed in the

PrivateAssemblies

folder. I started VS.NET and got this error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to load

or

caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it

again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

I selected "No", quit out of VS.NET and un-installed ReSharper.
Interestingly, the un-installer did not remove the files from the
PrivateAssemblies folder.

>

I ran the installer again, and again it went through w/o errors. I

restarted

VS.NET and got the same error again.

>

Any idea what file it seems to be missing?

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1hr7k$o61$1@is.intellij.net...

Michael,

>

it seems that ReSharper installer uselessly copies the following

assemblies

into PrivateAssemblies folder:

>

Microsoft.VisualStudio.Shell.Interop.dll,
Microsoft.VisualStudio.OLE.Interop.dll,
Microsoft.VisualStudio.TextManager.Interop.dll

>

In fact, these assemblies are located in the Global Assembly Cache.

Could

you please try to delete abovementioned
files from your PrivateAssemblies folder and look how ReSharper and
reporting services will work?

>

Please let us know about the resutls.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1g7p0$8au$1@is.intellij.net...

Yup, thats exactly what happens. Reporting Services installs its

DLL's

(including the shell dll which is a version newer than the one you

are

using) into C:\Program Files\Microsoft SQL Server\80\Tools\Report

Designer.

Please, please, see if you can resolve this: I need Reporting

Services,

but

I want ReSharper back!!! :)

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in

message

news:c1g22b$4na$1@is.intellij.net...

Michael,

>

I think your problem may be connected with ReSharper, because we

also

use 'Microsoft.VisualStudio.Shell.Interop' assembly. This

assembly

is

copied

to the PrivateAssemblies folder in the VS installation (on my

machine

this

is
"C:\Microsoft Visual Studio .NET

2003\Common7\IDE\PrivateAssemblies\").

PrivateAssemblies folder is included into the VS.NET private

probing

path

(where
the CLR attempts to load assemblies from). In your scenario it

seems

that

when you create a new report project, VS.NET tries to load
'Microsoft.VisualStudio.Shell.Interop'
assembly needed by reporting services, and fails, because the

version

of

the

assembly copied
by ReSharper does not match that required by reporting services.

>

Could you please describe where SQL Server reporting services

installs

its

files on your machine?
This would help us to figure out how to resolve this situation.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in

message

news:c1e672$tq6$1@is.intellij.net...

I run a pretty stock install of VS.NET 2003. I've also

installed

RS

v.66.

Today, I installed SQL Server reporting services which comes

with

a

report

designed integrated with VS.NET. Whenever I try to create a

new

report

project, I get this error:

>

The located assembly's manifest definition with name
'Microsoft.VisualStudio.Shell.Interop' does not match the

assembly

reference.

>

So, my unvalidated suspicion is that it may have something to

do

with

ReSharper (given how ReSharper most likely plugs into the IDE

shell

interop). Could that be the case or am I way off?

>

Thanks!
-Michael

>
>

>
>

>
>

>
>

>
>

>
>

>
>

I spoke too soon. I actually needed all three Interop dlls: Shell, OLE, and
TextManager for ReSharper to work. So, it looks like RS needs to know to
look for them in its install folder in order to play nice with other Add-Ins
(and hopefully VS.NET will be able to load and manage multiple versions side
x side).

-Michael

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1l9s5$bus$1@is.intellij.net...

One more tidbit:

>

I copied "Microsoft.VisualStudio.Shell.Interop.dll" from the ReSharper
folder into the PrivateAssemblies folder and VS.NET started just fine and
ReSharper was working. Unfortunately, this causes Report Services to stop
working which brings me right back to square one. Well, maybe square two
since we now know the offending DLL and how ReSharper is not loading it

when

it lives in the ReSharper folder.

>

Thanks!
-Michael

>
>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1l98d$87b$1@is.intellij.net...

Dmitry, thanks for following up.

>

At first I did not delete the PrivateAssemblies folder, I merely renamed

it.

However, it didnt look like it was needed for anything VS.NET or

Reporting

Services were doing, so I deleted the backup. Then I went through all

the

steps to install RS 67 that I described in a previous post.

>

Righ now my PrivateAssemblies folder contains the following files:
CookComputing.XmlRpc.dll
JetBrainsShared.dll
Microsoft.VisualStudio.VSIP.Helper.dll
ReSharper.dll
ReSharper.pdb
ReSharperPkgLib.dll
Services.dll
Services.pdb

>

PublicAssemblies:
extensibility.dll
MCppCodeDomParser.dll
MCppCodeDomProvider.dll
Microsoft.VisualStudio.VCCodeModel.dll
Microsoft.VisualStudio.VCProject.dll
Microsoft.VisualStudio.VCProjectEngine.dll
readme.txt
VSLangProj.dll
VSLangProj2.dll
VsMacroHierarchyLib.dll

>

GAC:
none that match your query

>
>

I went and looked at the VS.NET install disc and found that by default

the

PrivateAssemblies folder contains two files:
msatinterop.dll
readme.txt

>

I copied those two files into the PrivateAssemblies folder and installed
ReSharper 67 again. Started VS.NET and (again) got the following error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to load or
caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it

again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

The only file I found that matches the dll "family" you were looking

for,

either on my hard drive or on the VS.NET setup disc, was
"Microsoft.VisualStudio.Converters.Interop.dll". That file lives in
"C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE".

>

Any other ideas?

>

Thanks!
-Michael

>
>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1k8ug$p7n$1@is.intellij.net...

Michael,

>

first, I don't think it's a good idea to delete the entire Private
Assemblies folder - this folder
is a part of the VS directory hierarchy, and many applications (VS.NET
itself and ReSharper including)
rely on it to exist.

>

Could you please provide us with the following information:

>

1) What files are currently in your PrivateAssemblies and

PublicAssemblies

folders
2) What assemblies from "Microsoft.VisualStudio.*.Interop.dll" family

(and

what versions) are located in
the GAC on your system
(The GAC typically live in "C:\WINDOWS\assembly\" and includes several
subfolders).

>

Sorry for taking your time, but this information is really important

for

us

to understand how to cope with
this problem. We'll probably include a collector of such infromation

into

the ReSharper installer.

>

Thanks in advance,
Dmitry

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1ivr5$rai$1@is.intellij.net...

I uninstalled RS 66 and deleted the Private Assemblies folder when I

was

troubleshooting this problem. When I went to install RS 67, I got

the

following error while the install was running "registrar.exe":

>

---------------------------
Error
---------------------------
An exception has occurred during assembly copying.
Details:System.IO.DirectoryNotFoundException: Could not find a part

of

the

path "C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies\ReSharper.dll".

>

at System.IO.__Error.WinIOError(Int32 errorCode, String str)

>

at System.IO.File.InternalCopy(String sourceFileName, String
destFileName, Boolean overwrite)

>

at System.IO.File.Copy(String sourceFileName, String

destFileName,

Boolean overwrite)

>

at Registrar.Main(String[] args)
---------------------------
OK
---------------------------

>

This was followed by a few more assemblies that could not be copied.

After

I

OK'd out of the error messages, the command prompt closed and the

installer

reported that ReSharper was successfully installed (clearly NOT

correct).

>

I then manually created the PrivateAssemblies folder and re-ran the
installer and picked the "Repair" option. The install ran through to
completion w/o errors and the files were placed in the

PrivateAssemblies

folder. I started VS.NET and got this error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to load

or

caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it

again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

I selected "No", quit out of VS.NET and un-installed ReSharper.
Interestingly, the un-installer did not remove the files from the
PrivateAssemblies folder.

>

I ran the installer again, and again it went through w/o errors. I

restarted

VS.NET and got the same error again.

>

Any idea what file it seems to be missing?

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in

message

news:c1hr7k$o61$1@is.intellij.net...

Michael,

>

it seems that ReSharper installer uselessly copies the following

assemblies

into PrivateAssemblies folder:

>

Microsoft.VisualStudio.Shell.Interop.dll,
Microsoft.VisualStudio.OLE.Interop.dll,
Microsoft.VisualStudio.TextManager.Interop.dll

>

In fact, these assemblies are located in the Global Assembly

Cache.

Could

you please try to delete abovementioned
files from your PrivateAssemblies folder and look how ReSharper

and

reporting services will work?

>

Please let us know about the resutls.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in

message

news:c1g7p0$8au$1@is.intellij.net...

Yup, thats exactly what happens. Reporting Services installs its

DLL's

(including the shell dll which is a version newer than the one

you

are

using) into C:\Program Files\Microsoft SQL

Server\80\Tools\Report

Designer.

Please, please, see if you can resolve this: I need Reporting

Services,

but

I want ReSharper back!!! :)

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in

message

news:c1g22b$4na$1@is.intellij.net...

Michael,

>

I think your problem may be connected with ReSharper, because

we

also

use 'Microsoft.VisualStudio.Shell.Interop' assembly. This

assembly

is

copied

to the PrivateAssemblies folder in the VS installation (on my

machine

this

is
"C:\Microsoft Visual Studio .NET

2003\Common7\IDE\PrivateAssemblies\").

PrivateAssemblies folder is included into the VS.NET private

probing

path

(where
the CLR attempts to load assemblies from). In your scenario it

seems

that

when you create a new report project, VS.NET tries to load
'Microsoft.VisualStudio.Shell.Interop'
assembly needed by reporting services, and fails, because the

version

of

the

assembly copied
by ReSharper does not match that required by reporting

services.

>

Could you please describe where SQL Server reporting services

installs

its

files on your machine?
This would help us to figure out how to resolve this

situation.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in

message

news:c1e672$tq6$1@is.intellij.net...

I run a pretty stock install of VS.NET 2003. I've also

installed

RS

v.66.

Today, I installed SQL Server reporting services which comes

with

a

report

designed integrated with VS.NET. Whenever I try to create a

new

report

project, I get this error:

>

The located assembly's manifest definition with name
'Microsoft.VisualStudio.Shell.Interop' does not match the

assembly

reference.

>

So, my unvalidated suspicion is that it may have something

to

do

with

ReSharper (given how ReSharper most likely plugs into the

IDE

shell

interop). Could that be the case or am I way off?

>

Thanks!
-Michael

>
>

>
>

>
>

>
>

>
>

>
>

>
>

>
>

Michael,

since build 69, ReSharper installs Microsoft.VisualStudio.*.dlls in the GAC.
This should fix the problem with version compatibility. However, you should
clean up PrivateAssemblies from Microsoft.VisualStudio.*.dlls, as described
in the post "Problems with ReSharper build 67 and 68".

Thanks,
Dmitry

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1lb3f$jbv$1@is.intellij.net...

I spoke too soon. I actually needed all three Interop dlls: Shell, OLE,

and

TextManager for ReSharper to work. So, it looks like RS needs to know to
look for them in its install folder in order to play nice with other

Add-Ins

(and hopefully VS.NET will be able to load and manage multiple versions

side

x side).

>

-Michael

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1l9s5$bus$1@is.intellij.net...

One more tidbit:

>

I copied "Microsoft.VisualStudio.Shell.Interop.dll" from the ReSharper
folder into the PrivateAssemblies folder and VS.NET started just fine

and

ReSharper was working. Unfortunately, this causes Report Services to

stop

working which brings me right back to square one. Well, maybe square two
since we now know the offending DLL and how ReSharper is not loading it

when

it lives in the ReSharper folder.

>

Thanks!
-Michael

>
>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1l98d$87b$1@is.intellij.net...

Dmitry, thanks for following up.

>

At first I did not delete the PrivateAssemblies folder, I merely

renamed

it.

However, it didnt look like it was needed for anything VS.NET or

Reporting

Services were doing, so I deleted the backup. Then I went through all

the

steps to install RS 67 that I described in a previous post.

>

Righ now my PrivateAssemblies folder contains the following files:
CookComputing.XmlRpc.dll
JetBrainsShared.dll
Microsoft.VisualStudio.VSIP.Helper.dll
ReSharper.dll
ReSharper.pdb
ReSharperPkgLib.dll
Services.dll
Services.pdb

>

PublicAssemblies:
extensibility.dll
MCppCodeDomParser.dll
MCppCodeDomProvider.dll
Microsoft.VisualStudio.VCCodeModel.dll
Microsoft.VisualStudio.VCProject.dll
Microsoft.VisualStudio.VCProjectEngine.dll
readme.txt
VSLangProj.dll
VSLangProj2.dll
VsMacroHierarchyLib.dll

>

GAC:
none that match your query

>
>

I went and looked at the VS.NET install disc and found that by default

the

PrivateAssemblies folder contains two files:
msatinterop.dll
readme.txt

>

I copied those two files into the PrivateAssemblies folder and

installed

ReSharper 67 again. Started VS.NET and (again) got the following

error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to load

or

caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it

again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

The only file I found that matches the dll "family" you were looking

for,

either on my hard drive or on the VS.NET setup disc, was
"Microsoft.VisualStudio.Converters.Interop.dll". That file lives in
"C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE".

>

Any other ideas?

>

Thanks!
-Michael

>
>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1k8ug$p7n$1@is.intellij.net...

Michael,

>

first, I don't think it's a good idea to delete the entire Private
Assemblies folder - this folder
is a part of the VS directory hierarchy, and many applications

(VS.NET

itself and ReSharper including)
rely on it to exist.

>

Could you please provide us with the following information:

>

1) What files are currently in your PrivateAssemblies and

PublicAssemblies

folders
2) What assemblies from "Microsoft.VisualStudio.*.Interop.dll"

family

(and

what versions) are located in
the GAC on your system
(The GAC typically live in "C:\WINDOWS\assembly\" and includes

several

subfolders).

>

Sorry for taking your time, but this information is really important

for

us

to understand how to cope with
this problem. We'll probably include a collector of such infromation

into

the ReSharper installer.

>

Thanks in advance,
Dmitry

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1ivr5$rai$1@is.intellij.net...

I uninstalled RS 66 and deleted the Private Assemblies folder when

I

was

troubleshooting this problem. When I went to install RS 67, I got

the

following error while the install was running "registrar.exe":

>

---------------------------
Error
---------------------------
An exception has occurred during assembly copying.
Details:System.IO.DirectoryNotFoundException: Could not find a

part

of

the

path "C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies\ReSharper.dll".

>

at System.IO.__Error.WinIOError(Int32 errorCode, String str)

>

at System.IO.File.InternalCopy(String sourceFileName, String
destFileName, Boolean overwrite)

>

at System.IO.File.Copy(String sourceFileName, String

destFileName,

Boolean overwrite)

>

at Registrar.Main(String[] args)
---------------------------
OK
---------------------------

>

This was followed by a few more assemblies that could not be

copied.

After

I

OK'd out of the error messages, the command prompt closed and the

installer

reported that ReSharper was successfully installed (clearly NOT

correct).

>

I then manually created the PrivateAssemblies folder and re-ran

the

installer and picked the "Repair" option. The install ran through

to

completion w/o errors and the files were placed in the

PrivateAssemblies

folder. I started VS.NET and got this error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to

load

or

caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it

again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

I selected "No", quit out of VS.NET and un-installed ReSharper.
Interestingly, the un-installer did not remove the files from the
PrivateAssemblies folder.

>

I ran the installer again, and again it went through w/o errors. I

restarted

VS.NET and got the same error again.

>

Any idea what file it seems to be missing?

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in

message

news:c1hr7k$o61$1@is.intellij.net...

Michael,

>

it seems that ReSharper installer uselessly copies the following

assemblies

into PrivateAssemblies folder:

>

Microsoft.VisualStudio.Shell.Interop.dll,
Microsoft.VisualStudio.OLE.Interop.dll,
Microsoft.VisualStudio.TextManager.Interop.dll

>

In fact, these assemblies are located in the Global Assembly

Cache.

Could

you please try to delete abovementioned
files from your PrivateAssemblies folder and look how ReSharper

and

reporting services will work?

>

Please let us know about the resutls.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in

message

news:c1g7p0$8au$1@is.intellij.net...

Yup, thats exactly what happens. Reporting Services installs

its

DLL's

(including the shell dll which is a version newer than the one

you

are

using) into C:\Program Files\Microsoft SQL

Server\80\Tools\Report

Designer.

Please, please, see if you can resolve this: I need Reporting

Services,

but

I want ReSharper back!!! :)

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in

message

news:c1g22b$4na$1@is.intellij.net...

Michael,

>

I think your problem may be connected with ReSharper,

because

we

also

use 'Microsoft.VisualStudio.Shell.Interop' assembly. This

assembly

is

copied

to the PrivateAssemblies folder in the VS installation (on

my

machine

this

is
"C:\Microsoft Visual Studio .NET

2003\Common7\IDE\PrivateAssemblies\").

PrivateAssemblies folder is included into the VS.NET private

probing

path

(where
the CLR attempts to load assemblies from). In your scenario

it

seems

that

when you create a new report project, VS.NET tries to load
'Microsoft.VisualStudio.Shell.Interop'
assembly needed by reporting services, and fails, because

the

version

of

the

assembly copied
by ReSharper does not match that required by reporting

services.

>

Could you please describe where SQL Server reporting

services

installs

its

files on your machine?
This would help us to figure out how to resolve this

situation.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in

message

news:c1e672$tq6$1@is.intellij.net...

I run a pretty stock install of VS.NET 2003. I've also

installed

RS

v.66.

Today, I installed SQL Server reporting services which

comes

with

a

report

designed integrated with VS.NET. Whenever I try to create

a

new

report

project, I get this error:

>

The located assembly's manifest definition with name
'Microsoft.VisualStudio.Shell.Interop' does not match the

assembly

reference.

>

So, my unvalidated suspicion is that it may have something

to

do

with

ReSharper (given how ReSharper most likely plugs into the

IDE

shell

interop). Could that be the case or am I way off?

>

Thanks!
-Michael

>
>

>
>

>
>

>
>

>
>

>
>

>
>

>
>

>
>

Excellent! Just installed build 69 and I'm back in business! ;)

-Michael


"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1n4fp$se6$1@is.intellij.net...

Michael,

>

since build 69, ReSharper installs Microsoft.VisualStudio.*.dlls in the

GAC.

This should fix the problem with version compatibility. However, you

should

clean up PrivateAssemblies from Microsoft.VisualStudio.*.dlls, as

described

in the post "Problems with ReSharper build 67 and 68".

>

Thanks,
Dmitry

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1lb3f$jbv$1@is.intellij.net...

I spoke too soon. I actually needed all three Interop dlls: Shell, OLE,

and

TextManager for ReSharper to work. So, it looks like RS needs to know to
look for them in its install folder in order to play nice with other

Add-Ins

(and hopefully VS.NET will be able to load and manage multiple versions

side

x side).

>

-Michael

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1l9s5$bus$1@is.intellij.net...

One more tidbit:

>

I copied "Microsoft.VisualStudio.Shell.Interop.dll" from the ReSharper
folder into the PrivateAssemblies folder and VS.NET started just fine

and

ReSharper was working. Unfortunately, this causes Report Services to

stop

working which brings me right back to square one. Well, maybe square

two

since we now know the offending DLL and how ReSharper is not loading

it

when

it lives in the ReSharper folder.

>

Thanks!
-Michael

>
>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1l98d$87b$1@is.intellij.net...

Dmitry, thanks for following up.

>

At first I did not delete the PrivateAssemblies folder, I merely

renamed

it.

However, it didnt look like it was needed for anything VS.NET or

Reporting

Services were doing, so I deleted the backup. Then I went through

all

the

steps to install RS 67 that I described in a previous post.

>

Righ now my PrivateAssemblies folder contains the following files:
CookComputing.XmlRpc.dll
JetBrainsShared.dll
Microsoft.VisualStudio.VSIP.Helper.dll
ReSharper.dll
ReSharper.pdb
ReSharperPkgLib.dll
Services.dll
Services.pdb

>

PublicAssemblies:
extensibility.dll
MCppCodeDomParser.dll
MCppCodeDomProvider.dll
Microsoft.VisualStudio.VCCodeModel.dll
Microsoft.VisualStudio.VCProject.dll
Microsoft.VisualStudio.VCProjectEngine.dll
readme.txt
VSLangProj.dll
VSLangProj2.dll
VsMacroHierarchyLib.dll

>

GAC:
none that match your query

>
>

I went and looked at the VS.NET install disc and found that by

default

the

PrivateAssemblies folder contains two files:
msatinterop.dll
readme.txt

>

I copied those two files into the PrivateAssemblies folder and

installed

ReSharper 67 again. Started VS.NET and (again) got the following

error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to load

or

caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it

again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

The only file I found that matches the dll "family" you were looking

for,

either on my hard drive or on the VS.NET setup disc, was
"Microsoft.VisualStudio.Converters.Interop.dll". That file lives in
"C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE".

>

Any other ideas?

>

Thanks!
-Michael

>
>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in

message

news:c1k8ug$p7n$1@is.intellij.net...

Michael,

>

first, I don't think it's a good idea to delete the entire Private
Assemblies folder - this folder
is a part of the VS directory hierarchy, and many applications

(VS.NET

itself and ReSharper including)
rely on it to exist.

>

Could you please provide us with the following information:

>

1) What files are currently in your PrivateAssemblies and

PublicAssemblies

folders
2) What assemblies from "Microsoft.VisualStudio.*.Interop.dll"

family

(and

what versions) are located in
the GAC on your system
(The GAC typically live in "C:\WINDOWS\assembly\" and includes

several

subfolders).

>

Sorry for taking your time, but this information is really

important

for

us

to understand how to cope with
this problem. We'll probably include a collector of such

infromation

into

the ReSharper installer.

>

Thanks in advance,
Dmitry

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in

message

news:c1ivr5$rai$1@is.intellij.net...

I uninstalled RS 66 and deleted the Private Assemblies folder

when

I

was

troubleshooting this problem. When I went to install RS 67, I

got

the

following error while the install was running "registrar.exe":

>

---------------------------
Error
---------------------------
An exception has occurred during assembly copying.
Details:System.IO.DirectoryNotFoundException: Could not find a

part

of

the

path "C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies\ReSharper.dll".

>

at System.IO.__Error.WinIOError(Int32 errorCode, String str)

>

at System.IO.File.InternalCopy(String sourceFileName, String
destFileName, Boolean overwrite)

>

at System.IO.File.Copy(String sourceFileName, String

destFileName,

Boolean overwrite)

>

at Registrar.Main(String[] args)
---------------------------
OK
---------------------------

>

This was followed by a few more assemblies that could not be

copied.

After

I

OK'd out of the error messages, the command prompt closed and

the

installer

reported that ReSharper was successfully installed (clearly NOT

correct).

>

I then manually created the PrivateAssemblies folder and re-ran

the

installer and picked the "Repair" option. The install ran

through

to

completion w/o errors and the files were placed in the

PrivateAssemblies

folder. I started VS.NET and got this error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to

load

or

caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use

it

again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

I selected "No", quit out of VS.NET and un-installed ReSharper.
Interestingly, the un-installer did not remove the files from

the

PrivateAssemblies folder.

>

I ran the installer again, and again it went through w/o errors.

I

restarted

VS.NET and got the same error again.

>

Any idea what file it seems to be missing?

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in

message

news:c1hr7k$o61$1@is.intellij.net...

Michael,

>

it seems that ReSharper installer uselessly copies the

following

assemblies

into PrivateAssemblies folder:

>

Microsoft.VisualStudio.Shell.Interop.dll,
Microsoft.VisualStudio.OLE.Interop.dll,
Microsoft.VisualStudio.TextManager.Interop.dll

>

In fact, these assemblies are located in the Global Assembly

Cache.

Could

you please try to delete abovementioned
files from your PrivateAssemblies folder and look how

ReSharper

and

reporting services will work?

>

Please let us know about the resutls.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in

message

news:c1g7p0$8au$1@is.intellij.net...

Yup, thats exactly what happens. Reporting Services installs

its

DLL's

(including the shell dll which is a version newer than the

one

you

are

using) into C:\Program Files\Microsoft SQL

Server\80\Tools\Report

Designer.

Please, please, see if you can resolve this: I need

Reporting

Services,

but

I want ReSharper back!!! :)

>

Thanks!
-Michael

>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote

in

message

news:c1g22b$4na$1@is.intellij.net...

Michael,

>

I think your problem may be connected with ReSharper,

because

we

also

use 'Microsoft.VisualStudio.Shell.Interop' assembly. This

assembly

is

copied

to the PrivateAssemblies folder in the VS installation (on

my

machine

this

is
"C:\Microsoft Visual Studio .NET

2003\Common7\IDE\PrivateAssemblies\").

PrivateAssemblies folder is included into the VS.NET

private

probing

path

(where
the CLR attempts to load assemblies from). In your

scenario

it

seems

that

when you create a new report project, VS.NET tries to load
'Microsoft.VisualStudio.Shell.Interop'
assembly needed by reporting services, and fails, because

the

version

of

the

assembly copied
by ReSharper does not match that required by reporting

services.

>

Could you please describe where SQL Server reporting

services

installs

its

files on your machine?
This would help us to figure out how to resolve this

situation.

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote

in

message

news:c1e672$tq6$1@is.intellij.net...

I run a pretty stock install of VS.NET 2003. I've also

installed

RS

v.66.

Today, I installed SQL Server reporting services which

comes

with

a

report

designed integrated with VS.NET. Whenever I try to

create

a

new

report

project, I get this error:

>

The located assembly's manifest definition with name
'Microsoft.VisualStudio.Shell.Interop' does not match

the

assembly

reference.

>

So, my unvalidated suspicion is that it may have

something

to

do

with

ReSharper (given how ReSharper most likely plugs into

the

IDE

shell

interop). Could that be the case or am I way off?

>

Thanks!
-Michael

>
>

>
>

>
>

>
>

>
>

>
>

>
>

>
>

>
>

>
>

Grrr!!!

I just installed build 70 on top of 69 and we are back to the same problem.
I dont see the VisualStudio.Interop assemblies in the resharper folder or
the privateassemblies folder...

-Michael

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1nu4r$mh3$1@is.intellij.net...

Excellent! Just installed build 69 and I'm back in business! ;)

>

-Michael

>
>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in message
news:c1n4fp$se6$1@is.intellij.net...

Michael,

>

since build 69, ReSharper installs Microsoft.VisualStudio.*.dlls in the

GAC.

This should fix the problem with version compatibility. However, you

should

clean up PrivateAssemblies from Microsoft.VisualStudio.*.dlls, as

described

in the post "Problems with ReSharper build 67 and 68".

>

Thanks,
Dmitry

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1lb3f$jbv$1@is.intellij.net...

I spoke too soon. I actually needed all three Interop dlls: Shell,

OLE,

and

TextManager for ReSharper to work. So, it looks like RS needs to know

to

look for them in its install folder in order to play nice with other

Add-Ins

(and hopefully VS.NET will be able to load and manage multiple

versions

side

x side).

>

-Michael

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1l9s5$bus$1@is.intellij.net...

One more tidbit:

>

I copied "Microsoft.VisualStudio.Shell.Interop.dll" from the

ReSharper

folder into the PrivateAssemblies folder and VS.NET started just

fine

and

ReSharper was working. Unfortunately, this causes Report Services to

stop

working which brings me right back to square one. Well, maybe square

two

since we now know the offending DLL and how ReSharper is not loading

it

when

it lives in the ReSharper folder.

>

Thanks!
-Michael

>
>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in message
news:c1l98d$87b$1@is.intellij.net...

Dmitry, thanks for following up.

>

At first I did not delete the PrivateAssemblies folder, I merely

renamed

it.

However, it didnt look like it was needed for anything VS.NET or

Reporting

Services were doing, so I deleted the backup. Then I went through

all

the

steps to install RS 67 that I described in a previous post.

>

Righ now my PrivateAssemblies folder contains the following files:
CookComputing.XmlRpc.dll
JetBrainsShared.dll
Microsoft.VisualStudio.VSIP.Helper.dll
ReSharper.dll
ReSharper.pdb
ReSharperPkgLib.dll
Services.dll
Services.pdb

>

PublicAssemblies:
extensibility.dll
MCppCodeDomParser.dll
MCppCodeDomProvider.dll
Microsoft.VisualStudio.VCCodeModel.dll
Microsoft.VisualStudio.VCProject.dll
Microsoft.VisualStudio.VCProjectEngine.dll
readme.txt
VSLangProj.dll
VSLangProj2.dll
VsMacroHierarchyLib.dll

>

GAC:
none that match your query

>
>

I went and looked at the VS.NET install disc and found that by

default

the

PrivateAssemblies folder contains two files:
msatinterop.dll
readme.txt

>

I copied those two files into the PrivateAssemblies folder and

installed

ReSharper 67 again. Started VS.NET and (again) got the following

error:

>

---------------------------
Microsoft Development Environment
---------------------------
The Add-in 'ReSharper for VS.NET, version 1.0.67.111' failed to

load

or

caused an exception.
Would you like to remove this Add-in?
If you choose yes, you will need to reinstall the Add-in to use it

again.

>

Error Message: The system cannot find the file specified.

>
>

Error number: 80070002
---------------------------
Yes No
---------------------------

>

The only file I found that matches the dll "family" you were

looking

for,

either on my hard drive or on the VS.NET setup disc, was
"Microsoft.VisualStudio.Converters.Interop.dll". That file lives

in

"C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE".

>

Any other ideas?

>

Thanks!
-Michael

>
>

"Dmitry Shaporenkov(JetBrains)" <dsha@jetbrains.com> wrote in

message

news:c1k8ug$p7n$1@is.intellij.net...

Michael,

>

first, I don't think it's a good idea to delete the entire

Private

Assemblies folder - this folder
is a part of the VS directory hierarchy, and many applications

(VS.NET

itself and ReSharper including)
rely on it to exist.

>

Could you please provide us with the following information:

>

1) What files are currently in your PrivateAssemblies and

PublicAssemblies

folders
2) What assemblies from "Microsoft.VisualStudio.*.Interop.dll"

family

(and

what versions) are located in
the GAC on your system
(The GAC typically live in "C:\WINDOWS\assembly\" and includes

several

subfolders).

>

Sorry for taking your time, but this information is really

important

for

us

to understand how to cope with
this problem. We'll probably include a collector of such

infromation

into

the ReSharper installer.

>

Thanks in advance,
Dmitry

>

"Michael Teper" <michael.dot.teper@convade.dot.com> wrote in

message

news:c1ivr5$rai$1@is.intellij.net...

I uninstalled RS 66 and deleted the Private Assemblies folder

when

I

was

troubleshooting this problem. When I went to install RS 67, I

got

the

following error while the install was running "registrar.exe":

>

---------------------------
Error
---------------------------
An exception has occurred during assembly copying.
Details:System.IO.DirectoryNotFoundException: Could not find a

part

of

the

path "C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies\ReSharper.dll".

>

at System.IO.__Error.WinIOError(Int32 errorCode, String

str)

>

at System.IO.File.InternalCopy(String sourceFileName,

String

destFileName, Boolean overwrite)

>

at System.IO.File.Copy(String sourceFileName, String

destFileName,

Boolean overwrite)

>

at Registrar.Main(String[] args)
---------------------------
OK
---------------------------

>

This was followed by a few more assemblies that could not be

copied.

After

I

OK'd out of the error messages, the command prompt closed and

the

installer

reported that ReSharper was successfully installed (clearly

NOT

correct).

>

I then manually created the PrivateAssemblies folder and