Problems with latest builds

There are problems that make builds starting with 787 (and maybe before) competely unusable.
Create a new class and R# won't see it (no refactoring, etc.) until you restart VS. It's like R# only parses files on startup. Extremely annoying.

Oh, and PLEASE make documentation installation optional. Are you really updating it in every nightly build? How many people actually use it and need those latest updates? Merging takes a long time, especially if you have to do it twice a day: to install a new version and then rollback to an old (working) version.

9 comments
Comment actions Permalink

I'm having the same problem. Every build since 787 has random problems that make it unusable.
Every day I have to uninstall and reinstall 786 which works fine.
This then means I'm not doing any meaningful testing of later builds.
I second making documentation install optional - it would be much quicker without that.
Just put a checkbox on the first setup screen. I never use the advanced button.
The big problem is that build 786 now says it only has 2 days left. It's definitely not 30 days since 30th April. Is there a temporary license key I can use?

0
Comment actions Permalink

I've already tried begging about the documentation, but to no avail.

Given that JB claim there isn't any documentation for 4.0/VS2008, making people wait 20 minutes for a merge of non-existent documentation just seems perverse.

I've largely given up installing new builds because I've got so sick of how long the installation takes (overwhelmingly because of the documentation-which-doesn't-exist).

Will

0
Comment actions Permalink

I've done repeated installations and uninstallations of various versions of R#4 across three different machines and have never seen this 20 minute help merge that I keep hearing about. Can those experiencing it please provide more details as to the other components and applications installed on their machines, as I'm sure that the JetBrains folks would need such details in order to investigate any such problem.

0
Comment actions Permalink

I have VS2008, with Visual Assist (which doesn't mess with the MSDN help) and VisualSVN (which also doesn't as far as I know). Running on Vista.

But given that JB's only response to complaints about problems with the documentation is to deny that there is any documentation, I'm not particularly willing to spend a great deal of time isolating the problem.

And any time I feel like warming to JB, a quick 'dir %temp%\JetLogs' reminds me of the contempt in which this forum is held.

Will

0
Comment actions Permalink

Alex

I'm using VS2005 SP1 + Updates for Vista on Vista 64. What about you? Other people seem to be using latest builds without so many problems.

0
Comment actions Permalink

VS2005 (no sP1) on XP SP2, 32bit.
Not much in common, except for problems :)

0
Comment actions Permalink

I know that Philip is having problems even with SP1, but he's on Vista 64 so he is also exposed to a variety of other potential issues. With that said: is there any particular reason that you are back on VS 2005 RTM, given that SP1 fixed a number of nasty issues and has been out for literally years now?

Edited by: Jeremy Gray on May 13, 2008 5:59 PM

0
Comment actions Permalink

From our experience, SP1 introduced other problems (specifically with UI form designer). There are no issues in VS I would want to install SP1 for.
Are you suggesting that SP1 will fix R# performance problems?

0
Comment actions Permalink

Jeremy,

I personally don't have any issues with Vista 64, (well ok it needs a lot of RAM but that's not a problem).
What's strange is that R#4 was behaving pretty well until build 786 and it then became very flaky.
I now can't install build 786 since it insists the license has expired, so I've reverted to 3.1.
The only new feature I miss is camel humps intellisense.
Since the beta is supposedly imminent I'm going to wait for that and spend less time installing/uninstalling.

In response to a previous question about why help merging takes a long time I can only assume it's because I have the VS combined help collection which includes R# help because it's selected in the collection manager. I'm going to deselect R# from there and see if it helps next time I do an install.

0

Please sign in to leave a comment.