Problems with ReSharper build 67 and 68

Hi,

this post is for everyone experiencing problems with running ReSharper
(exception "The add-in ... failed to load..." on startup) or conflicts with
other VS.NET components (like Sql Server Reporting Services). The problem
is connected with the assemblies:

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

We ask you to do the following:

1) Please make sure that none of the abovementioned assemblies reside in the
VS.NET PrivateAssemblies folder:
(something like "C:\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies\"). They were copied there
during ReSharper installation prior to the build 67. If they are found in
the PrivateAssemblies, delete them manually.

2) Please put the abovementioned assemblies into the Global Assembly Cache.
This can be done by running

gacutil.exe /i <assembly-path>

gacutil.exe resides in the .NET Framework SDK installation directory
("C:\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin\gacutil.exe").
You should do this for all three assemblies.

Please let us know if this helps or you still experience the problem.
Thanks.
--
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


3 comments
Comment actions Permalink

After deleting "Microsoft.VisualStudio.*.dll" from PrivateAssemlbies, please
try out build 69.
It should install the necessary files in GAC.

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

Hi,

>

this post is for everyone experiencing problems with running ReSharper
(exception "The add-in ... failed to load..." on startup) or conflicts

with

other VS.NET components (like Sql Server Reporting Services). The problem
is connected with the assemblies:

>

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

>

We ask you to do the following:

>

1) Please make sure that none of the abovementioned assemblies reside in

the

VS.NET PrivateAssemblies folder:
(something like "C:\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies\"). They were copied there
during ReSharper installation prior to the build 67. If they are found in
the PrivateAssemblies, delete them manually.

>

2) Please put the abovementioned assemblies into the Global Assembly

Cache.

This can be done by running

>

gacutil.exe /i <assembly-path>

>

gacutil.exe resides in the .NET Framework SDK installation directory
("C:\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin\gacutil.exe").
You should do this for all three assemblies.

>

Please let us know if this helps or you still experience the problem.
Thanks.
--
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>


0
Comment actions Permalink

Hi Dimitry

Thanks for that. It works for me. However, the assemblies you mentioned
weren't present on my machine.

Anyway, thanks for the quick response.

--
Cheers

Barry Carr
Ixian Software Components Ltd
Blairgowrie
Perthshire
Scotland

0
Comment actions Permalink

Barry,

note about deleting assemblies only concerns those users
who have installed ReSharper builds prior to 67.

"Barry Carr" <barrycarr@ixian-software.com> wrote in message
news:c1nfgd$sib$1@is.intellij.net...

Hi Dimitry

>

Thanks for that. It works for me. However, the assemblies you mentioned
weren't present on my machine.

>

Anyway, thanks for the quick response.

>

--
Cheers

>

Barry Carr
Ixian Software Components Ltd
Blairgowrie
Perthshire
Scotland



0

Please sign in to leave a comment.