I am a little confused - there is 213 and 214 there at the same time - does this comment apply to 213 AND 214 or is it only 214 (or only 213 for that matter) that is unstable and needs the previous uninstall?
Or can we just go straight to 214 without uninstalling and without unstableness? In which case why are both downloads there?
Ronnie
ReSharper build #213 is out.
IMPORTANT NOTE: Uninstall any previous EAP builds of ReSharper 2.0! Upgrade without uninstalling works incorrectly (known problem)!
Changes:
a.. Asynchronous startup b.. Automatically set shortcuts in VS2003 and German localization Attention: this build is rather unstable yet due to major changes in startup process and core data structures
Hmm, I think I was just confused as to why 214 and 213 are there at the same time - I seem to be running 213! Therefore, obviously, the release notes are re:214 - I think I'll hang on until 215.....
Ronnie
Hello Eugene,
I am a little confused - there is 213 and 214 there at the same time - does this comment apply to 213 AND 214 or is it only 214 (or only 213 for that matter) that is unstable and needs the previous uninstall?
Or can we just go straight to 214 without uninstalling and without unstableness? In which case why are both downloads there?
Ronnie
>> ReSharper build #213 is out. >> >> IMPORTANT NOTE: Uninstall any previous EAP builds of ReSharper 2.0! >> Upgrade without uninstalling works incorrectly (known problem)! >> >> Changes: >> >> a.. Asynchronous startup >> b.. Automatically set shortcuts in VS2003 and German localization >> Attention: this build is rather unstable yet due to major changes in >> startup >> process and core data structures >> Full list of fixed bugs is available at >> http://www.intellij.net/tracker/resharper/searchSCR?ok=search&search= >> S >> earch&Field0=fixedInBuild&Operation0=GREATER&Value0=213&Field1=fixedI >> n >> Build&Operation1=LESS&Value1=215 >> You can download ReSharper from the download page of the ReSharper >> site: http://www.jetbrains.net/confluence/display/ReSharper/Download
It is a misprint. We have published build 214 with new caches. Unfortunately, it's rather unstable (we just looking for more feedback), so we did not remove the link to build 213, to have more or less stable build published too. -- Sergey V. Coox JetBrains, Inc http://www.jetbrains.com "Develop with pleasure!" "Ronnie Barker" <ronnie@freenet.co.uk> wrote in message news:b5214412496d8c7dad845e434be@news.jetbrains.com...
Monday when I am back at work after the holiday I will give build # 214 a shot, because I will be doing lots of refactoring on a project next week. I will post as much feedback as possible.
It is a misprint. We have published build 214 with new caches. Unfortunately, it's rather unstable (we just looking for more feedback), so we did not remove the link to build 213, to have more or less stable build published too. -- Sergey V. Coox JetBrains, Inc http://www.jetbrains.com "Develop with pleasure!" "Ronnie Barker" <ronnie@freenet.co.uk> wrote in message news:b5214412496d8c7dad845e434be@news.jetbrains.com...
Unfortunately, it's rather unstable (we just looking for more feedback)
Firstly, this build works much better with generics. We have a project in our solution which uses them extensively and in quite tricky ways (like declaring Base and Dervied : Base]]> afterwards). Working with this code in build 213 is really painful -- I get numerous exceptions and wrong error highlighting. Build 214 behaves much better (but still not perfect -- I wil submit all wrong highlightings I've found to the tracker).
The most serious problem with 214 is its new caches. For me they almost never work.... When I close solution and reload it afterwards no ids are resolved at all.
As I understand you use build 214 (or some derivative from it) in your dialy work. Do you also experience such problems? Or maybe my usecases are somewhat non-standard...
> >> Unfortunately, it's rather unstable (we just looking for more >> feedback) >
Firstly, this build works much better with generics. We have a project in our solution which uses them extensively and in quite tricky ways (like declaring Base<T> and Dervied : Base<Derived> afterwards). Working with this code in build 213 is really painful -- I get numerous exceptions and wrong error highlighting. Build 214 behaves much better (but still not perfect -- I wil submit all wrong highlightings I've found to the tracker).
>
The most serious problem with 214 is its new caches. For me they almost never work.... When I close solution and reload it afterwards no ids are resolved at all.
>
As I understand you use build 214 (or some derivative from it) in your dialy work. Do you also experience such problems? Or maybe my usecases are somewhat non-standard...
Unfortunately, it does not always work. During some loads I get 'attempt to release lock' exception and after that error analysis becomes broken. I also noticed that deleting *.user files one can get positive effects =)
As I understand you use build 214 (or some derivative from it) in your dialy work. Do you also experience such problems? Or maybe my usecases are somewhat non-standard...
In fact, we used it for a while before publishing - it was more or less workable comparing to build 213, which crached several times a day (at least at my PC), but now all of us are on holidays, so there's almost no any development with the current build. Note, that we don't use generics to have the source code compilable for both frameworks, so some features are almost not tested.
Hello Eugene,
I am a little confused - there is 213 and 214 there at the same time - does
this comment apply to 213 AND 214 or is it only 214 (or only 213 for that
matter) that is unstable and needs the previous uninstall?
Or can we just go straight to 214 without uninstalling and without unstableness?
In which case why are both downloads there?
Ronnie
Hello Me!,
Hmm, I think I was just confused as to why 214 and 213 are there at the same
time - I seem to be running 213!
Therefore, obviously, the release notes are re:214 - I think I'll hang on
until 215.....
Ronnie
>> ReSharper build #213 is out.
>>
>> IMPORTANT NOTE: Uninstall any previous EAP builds of ReSharper 2.0!
>> Upgrade without uninstalling works incorrectly (known problem)!
>>
>> Changes:
>>
>> a.. Asynchronous startup
>> b.. Automatically set shortcuts in VS2003 and German localization
>> Attention: this build is rather unstable yet due to major changes in
>> startup
>> process and core data structures
>> Full list of fixed bugs is available at
>> http://www.intellij.net/tracker/resharper/searchSCR?ok=search&search=
>> S
>> earch&Field0=fixedInBuild&Operation0=GREATER&Value0=213&Field1=fixedI
>> n
>> Build&Operation1=LESS&Value1=215
>> You can download ReSharper from the download page of the ReSharper
>> site: http://www.jetbrains.net/confluence/display/ReSharper/Download
Ronni,
It is a misprint. We have published build 214 with new caches.
Unfortunately, it's rather unstable (we just looking for more feedback), so
we
did not remove the link to build 213, to have more or less stable build
published too.
--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Ronnie Barker" <ronnie@freenet.co.uk> wrote in message
news:b5214412496d8c7dad845e434be@news.jetbrains.com...
Monday when I am back at work after the holiday I will give build # 214 a
shot, because I will be doing lots of refactoring on a project next week. I
will post as much feedback as possible.
Gabriel Lozano-Morán
MCSD .NET
Real Software
http://www.realsoftware.be
http://www.realdn.be
"Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message
news:dp36qh$jm3$1@is.intellij.net...
>
Hello Sergey,
Firstly, this build works much better with generics. We have a project in
our solution which uses them extensively and in quite tricky ways (like declaring
Base and Dervied : Base]]> afterwards). Working with this code in
build 213 is really painful -- I get numerous exceptions and wrong error
highlighting. Build 214 behaves much better (but still not perfect -- I wil
submit all wrong highlightings I've found to the tracker).
The most serious problem with 214 is its new caches. For me they almost never
work.... When I close solution and reload it afterwards no ids are resolved
at all.
As I understand you use build 214 (or some derivative from it) in your dialy
work. Do you also experience such problems? Or maybe my usecases are somewhat
non-standard...
Best regards,
Maxim
Currently we've found that hot startup isn't working :(
Please could you remove the caches directory before VS startup
--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Maxim Babenko" <mab@shade.msu.ru> wrote in message
news:10562632715773077656250@news.intellij.net...
>
>> Unfortunately, it's rather unstable (we just looking for more
>> feedback)
>
>
>
>
>
>
Hello Eugene,
Do you mean "before solution load"? I will try.
Aother question is how did you manage to break the intellisense autopopup...
=) Do you prefer to have it switched off?
Best regards,
Maxim
>> Currently we've found that hot startup isn't working :( Please could
>> you remove the caches directory before VS startup
Yes.
Personally, yes.
--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Hello Eugene,
Unfortunately, it does not always work. During some loads I get 'attempt
to release lock' exception and after that error analysis becomes broken.
I also noticed that deleting *.user files one can get positive effects =)
I see...
Best regards,
Maxim
Maxim,
In fact, we used it for a while before publishing - it was more or less
workable comparing to build 213, which crached several times a day (at least
at my PC), but now all of us are on holidays, so there's almost no any
development with the current build.
Note, that we don't use generics to have the source code compilable for both
frameworks, so some features are almost not tested.
--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"