The Earlier Corrupted DLLs Problem

In earlier releases of Resharper, there was "breakage" of the VS.Net
environment if Resharper was uninstalled. I stopped evaluating the product,
hoping that the problem would be solved in later builds. (One "repair"
session of VS.Net was enough for me.)

So, the question is - have these problems been solved? Will I be able to
confidently install build 81 and not have to worry about a potential
non-working VS.Net after an uninstall?

I am looking forward to "developing with pleasure" - but can't afford the
downtime that is involved with a repair of the environment later on.


1 comment
Comment actions Permalink

Charles,

there was really a problem in earlier builds of ReSharper that
caused unregistration of VS csproj.dll. In fact, you didn't need to run
VS repair that is indeed a very time-consuming operation - you only
needed to register that dll again:

regsvr32.exe "Microsoft Visual Studio .NET 2003\Vc7\vcpackages\csproj.dll"


(this line was posted here many times). This should solve all the problems.

"Charles P. Cuozzo" <nospam@nospam.com> wrote in message
news:c800vi$qld$1@is.intellij.net...

In earlier releases of Resharper, there was "breakage" of the VS.Net
environment if Resharper was uninstalled. I stopped evaluating the

product,

hoping that the problem would be solved in later builds. (One "repair"
session of VS.Net was enough for me.)

>

So, the question is - have these problems been solved? Will I be able to
confidently install build 81 and not have to worry about a potential
non-working VS.Net after an uninstall?

>

I am looking forward to "developing with pleasure" - but can't afford the
downtime that is involved with a repair of the environment later on.

>
>


0

Please sign in to leave a comment.