5 comments

Hello,

Where are the nightly builds? The last one dates back to November 12th


Probably, you're looking at the 4.1 branch builds list. R# 4.5 Nightly Builds
are posted to the new page on Wiki. See the announcement for more details:
news://news.intellij.net/gj0tg7$tqi$1@is.intellij.net .


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Hello,

devenv /RootSuffix ReSharper

I receive the error "Cannot find one or more components. Please
reinstall the application."


Did this command succeed before running the InstallExperimentalHive batch?
The hive must be already operable before installing R# into it.

BTW - On another Vista x64 machine (my laptop), I tried the same
steps, but received the following error when running the msbuild step.

"JetBrains.VSIntegration.Install.InstallExperimenta
lHive" task could not be loaded from the assembly C:\Program Files
(x86)\JetBrains\ReSharper\v4.5\Bin\JetBrains.Platform.ReSharper.VSIntegration.dll.
is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)


Very strange. Could it be that you're running 64-bit MSBuild version in this
case?


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

I didn't realize that you needed to create the experimental hive yourself. I
thought the JetBrains.VSIntegration.Install.InstallExperimentalHive would do
that. The task reported success even though the experimental hive was not
present. Given my lack of experience (and most developers lack of
experience) in VSX development - it's a pretty specialized skill honestly -
I would recommend expanding the install notes to include mention of:

- Installing VSX SDK (I didn't realize that this was a separate install from
a full VS2008 install)
- Running "VsRegEx GetOrig 9.0 ReSharper RANU"
- Copying InstallExperimentalHive.Proj to your ReSharper install location
- Running "msbuild InstallExperimentalHive.Proj /t:Build" as the user who
will be running VS2008
- Running "devenv /RootSuffix ReSharper /Setup"
- Creating a shortcut to "devenv /RootSuffix ReSharper"

BTW - When I followed these steps, I was only able to run VS2008 with
ReSharper 4.5 as an administrator. Trying to run
"InstallExperimentalHive.Proj" as a normal user failed with a security
exception trying to write to HLKM. If I try to run "devenv /RootSuffix
ReSharper" as a normal user, ReSharper 4.1 tries to load, but fails with an
error.

BTWx2 - I need to try these steps on my laptop to see if they resolve the
problem. I'll double-check, but I'm quite certain that MSBuild v3.5 x64 is
installed on that box too as I've run 64-bit builds using C# 3.0.

Thanks for your help!
James

"Serge Baltic" <baltic@intellij.net> wrote in message
news:dc0986bf132cdf8cb3f1aec0ab8ae@news.intellij.net...

Hello,

>
>> devenv /RootSuffix ReSharper
>>
>> I receive the error "Cannot find one or more components. Please
>> reinstall the application."
>

Did this command succeed before running the InstallExperimentalHive batch?
The hive must be already operable before installing R# into it.

>
>> BTW - On another Vista x64 machine (my laptop), I tried the same
>> steps, but received the following error when running the msbuild step.

>> "JetBrains.VSIntegration.Install.InstallExperimenta
>> lHive" task could not be loaded from the assembly C:\Program Files
>> (x86)\JetBrains\ReSharper\v4.5\Bin\JetBrains.Platform.ReSharper.VSIntegration.dll.
>> is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
>

Very strange. Could it be that you're running 64-bit MSBuild version in
this case?

>


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”

>


0

Hello,

I didn't realize that you needed to create the experimental hive
yourself. I thought the
JetBrains.VSIntegration.Install.InstallExperimentalHive would do that.
The task reported success even though the experimental hive was not
present. Given my lack of experience (and most developers lack of
experience) in VSX development - it's a pretty specialized skill
honestly - I would recommend expanding the install notes to include
mention of:


Sounds reasonable, but I'd rather keep the description brief.

The main goal of this build task (which, actually, exposes the part of our
installer build process and local quick installation tool) is to allow R#
plugin devs to have more than one R# version installed for the same Visual
Studio, simultaneousely. This way the plugins could be tested for compatibility
against multiple R# versions. This audience is expected to have the required
VSX experience and general understanding of Visual Studio hives. Anyway you
got to have some knowledge of what a Visual Studio hive is to think of installing
R# for it, and that knowledge generally goes along with VSX. I can't recall
any non-VSX user trying this functionality before.

The main reason, however, is that I'd like to have some educational threshold
for this functionality (zero for its main audience anyway), because providing
support to general users for it on a regular basis sounds more like a nightmare.
Experimental hives are so experimental, you know. Main-hive integration is
already complicated enough.

- Running "VsRegEx GetOrig 9.0 ReSharper RANU"


We do not support RANU for experimental hives. Would be a strange thing to
do, as our main hive is still an all-users-only install. Got a few Registry
things that must be written to HKLM, and devenv/setup can't run non-power-user
as well. Even worse, a per-user R# install won't be able to run plugins.

- Running "msbuild InstallExperimentalHive.Proj /t:Build" as the user who

will be running VS2008

There must be no HKCU writes (they're the same writes an all-users installer
would do), so it does not matter which user you run this under. Must be a
power user plus (or elevated), though.

That is, unless you're shooting yourself in the foot by running Vista with
the "User Account Control: Virtualizes file and registry write failures to
per-user locations" policy enabled. A nice option to mess the things up beyound
any understanding. With its help, R# task, devenv/setup and regular devenv
could easily be running different HDD and Registry copies each.

BTW - When I followed these steps, I was only able to run VS2008 with
ReSharper 4.5 as an administrator. Trying to run
"InstallExperimentalHive.Proj" as a normal user failed with a security
exception trying to write to HLKM. If I try to run "devenv /RootSuffix
ReSharper" as a normal user, ReSharper 4.1 tries to load, but fails
with an error.


Setting the Vista policies should help with such effects.

BTWx2 - I need to try these steps on my laptop to see if they resolve
the problem. I'll double-check, but I'm quite certain that MSBuild
v3.5 x64 is installed on that box too as I've run 64-bit builds using
C# 3.0.


There're two msbuild.exe's on 64-bits: one for 32, one for 64. Running the
wrong one will look basically the same way, but fail to do the right thing.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Hello,

I didn't realize that you needed to create the experimental hive
yourself. I thought the
JetBrains.VSIntegration.Install.InstallExperimentalHive would do that.
The task reported success even though the experimental hive was not
present. Given my lack of experience (and most developers lack of
experience) in VSX development - it's a pretty specialized skill
honestly - I would recommend expanding the install notes to include
mention of:


Sounds reasonable, but I'd rather keep the description brief.

The main goal of this build task (which, actually, exposes the part of our
installer build process and local quick installation tool) is to allow R#
plugin devs to have more than one R# version installed for the same Visual
Studio, simultaneousely. This way the plugins could be tested for compatibility
against multiple R# versions. This audience is expected to have the required
VSX experience and general understanding of Visual Studio hives. Anyway you
got to have some knowledge of what a Visual Studio hive is to think of installing
R# for it, and that knowledge generally goes along with VSX. I can't recall
any non-VSX user trying this functionality before.

The main reason, however, is that I'd like to have some educational threshold
for this functionality (zero for its main audience anyway), because providing
support to general users for it on a regular basis sounds more like a nightmare.
Experimental hives are so experimental, you know. Main-hive integration is
already complicated enough.

- Running "VsRegEx GetOrig 9.0 ReSharper RANU"


We do not support RANU for experimental hives. Would be a strange thing to
do, as our main hive is still an all-users-only install. Got a few Registry
things that must be written to HKLM, and devenv/setup can't run non-power-user
as well. Even worse, a per-user R# install won't be able to run plugins.

- Running "msbuild InstallExperimentalHive.Proj /t:Build" as the user who

will be running VS2008

There must be no HKCU writes (they're the same writes an all-users installer
would do), so it does not matter which user you run this under. Must be a
power user plus (or elevated), though.

That is, unless you're shooting yourself in the foot by running Vista with
the "User Account Control: Virtualizes file and registry write failures to
per-user locations" policy enabled. A nice option to mess the things up beyound
any understanding. With its help, R# task, devenv/setup and regular devenv
could easily be running different HDD and Registry copies each.

BTW - When I followed these steps, I was only able to run VS2008 with
ReSharper 4.5 as an administrator. Trying to run
"InstallExperimentalHive.Proj" as a normal user failed with a security
exception trying to write to HLKM. If I try to run "devenv /RootSuffix
ReSharper" as a normal user, ReSharper 4.1 tries to load, but fails
with an error.


Setting the Vista policies should help with such effects.

BTWx2 - I need to try these steps on my laptop to see if they resolve
the problem. I'll double-check, but I'm quite certain that MSBuild
v3.5 x64 is installed on that box too as I've run 64-bit builds using
C# 3.0.


There're two msbuild.exe's on 64-bits: one for 32, one for 64. Running the
wrong one will look basically the same way, but fail to do the right thing.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Please sign in to leave a comment.