VS 2008/NET 3.5 SP1 Coming - How does this effect R# 4.0?

With the announcement today of the upcoming SP1 releases of VS2008 and .NET 3.5, is that going to have an major impact on the mentioned release of R# 4.0?

David

4 comments
Comment actions Permalink

Hello David,

We are currently in process of testing ReSharper with SP1 beta, released
recently. We will try our best to ensure compatibility before ReSharper 4
release, but since final bits of SP1 will come later, we may have to release
update to ReSharper when they are available.

PS: Amount of changes in SP1, amount of problems in VS we face when developing
addin (some of them are regressions from VS2005), this all makes me think
that VS2008 RTM was pushed to the market being not ready. I tend to perceive
VS2008 RTM as "Beta", SP1 Beta as "Release Candidate" and VS2008 SP1 release
coming in summer as "Release" :)

Sincerely,
Ilya Ryzhenkov

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


IR> With the announcement today of the upcoming SP1 releases of VS2008
IR> and .NET 3.5, is that going to have an major impact on the mentioned
IR> release of R# 4.0?
IR>
IR> David
IR>


0
Comment actions Permalink

I've been running the latest nightlies on Sp1 beta for the last two days now
w/o any noticable issues...

"Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
news:76a2bd0b157bfc8ca8576285c8924@news.intellij.net...

Hello David,

>

We are currently in process of testing ReSharper with SP1 beta, released
recently. We will try our best to ensure compatibility before ReSharper 4
release, but since final bits of SP1 will come later, we may have to
release update to ReSharper when they are available.
PS: Amount of changes in SP1, amount of problems in VS we face when
developing addin (some of them are regressions from VS2005), this all
makes me think that VS2008 RTM was pushed to the market being not ready. I
tend to perceive VS2008 RTM as "Beta", SP1 Beta as "Release Candidate" and
VS2008 SP1 release coming in summer as "Release" :)

>

Sincerely,
Ilya Ryzhenkov

>

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

>
>

IR> With the announcement today of the upcoming SP1 releases of VS2008
IR> and .NET 3.5, is that going to have an major impact on the mentioned
IR> release of R# 4.0?
IR> IR> David
IR>


0
Comment actions Permalink

I just wanted to state, that given that the team developing VS is what, 30+
people, and from what I can see there is 5 - 10 people on your team doing
R#, the quality of work that you are achieving is far and above par. The
complexity of the R# addin is mind staggering, particularly when you think
of the fact that you must maintain to distinct versions (2005 and 2008).
The fact that R# is, for nearly every professional programmer that I work
with, indispensable, say it all.

Keep up the good work, and do not let all the "complaints" that we, the EAP
users, give you. We just want the best tool on our belt to be all that much
better.

David

"Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
news:76a2bd0b157bfc8ca8576285c8924@news.intellij.net...

Hello David,

>

We are currently in process of testing ReSharper with SP1 beta, released
recently. We will try our best to ensure compatibility before ReSharper 4
release, but since final bits of SP1 will come later, we may have to
release update to ReSharper when they are available.
PS: Amount of changes in SP1, amount of problems in VS we face when
developing addin (some of them are regressions from VS2005), this all
makes me think that VS2008 RTM was pushed to the market being not ready. I
tend to perceive VS2008 RTM as "Beta", SP1 Beta as "Release Candidate" and
VS2008 SP1 release coming in summer as "Release" :)

>

Sincerely,
Ilya Ryzhenkov

>

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

>
>

IR> With the announcement today of the upcoming SP1 releases of VS2008
IR> and .NET 3.5, is that going to have an major impact on the mentioned
IR> release of R# 4.0?
IR> IR> David
IR>



0
Comment actions Permalink

I don't want to be the buzz kill on your much needed praise.

While I do think that you guys are doing the impossible I don't believe that giving feedback without first testing the software on a larger system benefits anyone. While on hello world type apps ReSharper seems to handle the SP1 betas fine, if you load up a larger application with unit tests you will fine a slightly different picture.

First off..

Kudos on what seems like finally fixing the XAML parsing bug. It seems the latest nightly build is not blowing up on XAML anymore. This has been plaguing us for months now. Here is a link to a thread for more information. http://www.intellij.net/forums/thread.jspa?messageID=5211920

Secondly

I am running VS2008 SP1 beta as well as the .Net 3.5 SP1 Beta with the latest nightly build and there are issues as to be expected.
The only major problems specific to the SP1 betas that I see is the relationship between VS NUnit and Resharper. I have a feeling that NUnit and VS are not playing nice together which is throwing off ReSharper. If I go to my tests every single Test Attribute is being red underlined by ReSharper. Keep in mind that this is code that VS can not only compile but also run and test under 2008 Sln Builder in TeamCity. If I were to change the Attribute tag to NUnit.Framework.Test I notice that ReSharper will still complain with a red underline but now will put the green and red ball next to the test. This same effect can sometimes also be achieved by retyping Test again but not always.

Hope this helps a little bit
Michael Hohlios

Using
Visual Studio 2008 9.0.30428.1 SP1 Beta 1
.Net Framework Version 3.5 SP1
Resharper 4.0.799.16
NUnit 2.4.7

Edited by: Michael Hohlios on May 16, 2008 9:39 PM - Removed brackets because it read them as links

Edited by: Michael Hohlios on May 16, 2008 9:40 PM - Fixed broken link to the other forum post

0

Please sign in to leave a comment.