13 comments
Comment actions Permalink

I second that. Working on it every day since release.

Eugene Pasynkov (JetBrains) wrote:

I've just tried ReSharper on VS 2005 RC. It works fine.

0
Comment actions Permalink

Hello, Eugene,

It really works! =) And moreover, the problem with magenta lightbulb has
gone! So it seems to be some MS bug indeed...

Unfortunately, the highlighers still behave strangely with RC. BTW, have
you told MSers about this issue...? It would be very unpleasant to have it
in release.


0
Comment actions Permalink

Unfortunately, the highlighers still behave strangely with RC. BTW, have
you told MSers about this issue...? It would be very unpleasant to have it
in release.


Yes.
And they confirmed the bug in VS core.

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

I'd not say their confirmed, but rather they suspect this. Unfortunately,
many of them (including the person we discussed the problem with) seem to be
on a kind of vacation after PDC :(

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> Unfortunately, the highlighers still behave strangely with RC. BTW,
>> have you told MSers about this issue...? It would be very unpleasant
>> to have it in release.
>>

Yes.
And they confirmed the bug in VS core.



0
Comment actions Permalink

Maxim,

It really works! =) And moreover, the problem with magenta lightbulb has
gone! So it seems to be some MS bug indeed...

Wow! Great news! I managed to reproduce the magenta lightbulb persistently
on one of our PCs and have spent half a week trying to remove it. But failed
:)
--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

I've just tried ReSharper on VS 2005 RC. It works fine.


It seems to work for me too; however during the install I noticed that the
install script (which runs in the command window) ran InstallUtil.exe from
the v2.0.50215 framework directory (Beta 2), instead of from the new v2.0.50727
directory.

Is this a problem with my configuration, or is it something to do with the
ReSharper install?


0
Comment actions Permalink

Hello Gerrod,

It seems to work for me too; however during the install I noticed that
the install script (which runs in the command window) ran
InstallUtil.exe from the v2.0.50215 framework directory (Beta 2),
instead of from the new v2.0.50727 directory.


Very strange... How did you manage to have BOTH of these versions installed?
AFAIK RC setup requests to remove all previous versions of FW 2.0 -- and
refuses to continue until that is done.


0
Comment actions Permalink

Very strange... How did you manage to have BOTH of these versions
installed? AFAIK RC setup requests to remove all previous versions of
FW 2.0 -- and refuses to continue until that is done.


You're absolutely right; I ran every clean up utility that I could get my
hands on (basically the Sql Server cleanup utility, and the vs_uninst.exe
one as well). One of them wiped out the old version of the framework, to
the extent that it was removed from the Add/Remove program menu.

But as it turns out, the entire v2.0.50215 framework directory (or at least
a heap of its contents) was left on my PC. I'm not sure if that's an exception,
or typical...


0
Comment actions Permalink

Hello Gerrod,

But as it turns out, the entire v2.0.50215 framework directory (or at
least a heap of its contents) was left on my PC. I'm not sure if
that's an exception, or typical...


I have tried VS Beta 1 and Beta 2 before installing RC. How there's only
one version of FW 2.0 in %WINDIR%\Microsoft.NET.


0
Comment actions Permalink

Hello Gerrod,

since the user may have a plenty of 2.0 .NET frameworks installed on her
machine,
choosing the right one becomes a problem for the installer. ReSharper currently
chooses
one that contains the file 'InstallUtil.exe' of a version not smaller than
2.0.50215 (the
version of framework shipped with Whidbey Beta 2 to which ReSharper 2.0 targeted
initially).
In your situation, I suspect that it finds the complete 2.0.50215 framework
and is happy with it, since it matches
the abovementioned condition. This doesn't seem to be a problem, as ReSharper
binaries are compiled
against that very 2.0.50215 framework, so its InstallUtil.exe works fine
with them.

We may reconsider this policy if any problems are discovered. Thank you for
interesting observation!

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> I've just tried ReSharper on VS 2005 RC. It works fine.
>>

It seems to work for me too; however during the install I noticed that
the install script (which runs in the command window) ran
InstallUtil.exe from the v2.0.50215 framework directory (Beta 2),
instead of from the new v2.0.50727 directory.

Is this a problem with my configuration, or is it something to do with
the ReSharper install?



0
Comment actions Permalink

Hi Dmitry -

No problems. Curious though; how does ReSharper look for the InstallUtil.exe? Going off what you're saying, does it just parse the -

C:\WINDOWS\Microsoft.NET\Framework

- directory, and look at whatever versions it finds in there? As, even more curiously, when I renamed the framework directory:

v2.0.50215 --> v2.0.50215_old

ReSharper STILL used this InstallUtil.exe!

Hope that helps; if not, as you said, it is at least "interesting" :)

Cheers -
/gerrod

0
Comment actions Permalink

Hello Gerrod,

yes, it really works like this. It searches for a directory containing
the file InstallUtil.exe of a proper version in the C:\WINDOWS\Microsoft.NET\Framework
folder (ok, in what is specified in the registry), so renaming the framework
directory doesn't
confuse it.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi Dmitry -

No problems. Curious though; how does ReSharper look for the
InstallUtil.exe? Going off what you're saying, does it just parse the
-

C:\WINDOWS\Microsoft.NET\Framework

- directory, and look at whatever versions it finds in there? As, even
more curiously, when I renamed the framework directory:

v2.0.50215 --> v2.0.50215_old

ReSharper STILL used this InstallUtil.exe!

Hope that helps; if not, as you said, it is at least "interesting" :)

Cheers -
/gerrod



0
Comment actions Permalink

Errata:

'InstallUtil.exe of a proper version in the C:\WINDOWS\Microsoft.NET\Framework
folder'

should be

'InstallUtil.exe of a proper version in a one-level subfolder of the C:\WINDOWS\Microsoft.NET\Framework
folder'

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello Gerrod,

yes, it really works like this. It searches for a directory containing
the file InstallUtil.exe of a proper version in the
C:\WINDOWS\Microsoft.NET\Framework
folder (ok, in what is specified in the registry), so renaming the
framework
directory doesn't
confuse it.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> Hi Dmitry -
>>
>> No problems. Curious though; how does ReSharper look for the
>> InstallUtil.exe? Going off what you're saying, does it just parse the
>> -
>>
>> C:\WINDOWS\Microsoft.NET\Framework
>>
>> - directory, and look at whatever versions it finds in there? As,
>> even more curiously, when I renamed the framework directory:
>>
>> v2.0.50215 --> v2.0.50215_old
>>
>> ReSharper STILL used this InstallUtil.exe!
>>
>> Hope that helps; if not, as you said, it is at least "interesting"
>> :)
>>
>> Cheers -
>> /gerrod


0

Please sign in to leave a comment.