Resharper EAP 5.0 build 1528 highlighting problems that aren't problems

Hi there,

I noticed in my asp.net website I have the following errors:

  1. I have Global.asax file which has the following:
    <%@ Application CodeFile="Global.asax.cs" Inherits="Global" Language="C#" %>
               (Cannot resolve symbole 'CodeFile')             (INVALID_BASE_TYPE)
    I'm not sure why I am getting those two errors, in resharper 4.5.1 I was not getting this error

  2. I also have aspx pages EnableViewState="false" EnableSessionState="ReadOnly" %>
                                                                                      (Cannot resolve symbole 'ReadOnly')
    Once again I didn't have this problem in 4.5.1

  3. <span position:relative; top:0px; bottom:10px;">
    Mulitple errors occur here: attribute value expected | Unexpected token

  4. I also outlined a problem here with slow editing of asp.net pages that has never been replied to, I even give a way of how resharper instantly speeds up after doing a certain action: http://www.jetbrains.net/devnet/thread/283293?tstart=0


No errors are found by the C# compiler which suggests these are respaher problems

Thanks for your time and effort keep up the good work

DotnetShadow

6 comments
Comment actions Permalink

1,2 Fixed. Thanks for pointing out to a problem. Though, MSDN (and Visual studio) thinks that CodeFile  is not valid attribute for Application, but compile it correctly.

3. <span position:relative; top:0px; bottom:10px;">
Eventually this line contains an error which is ignored by browser - quotes are mismatched. C# compiler does not compile HTML part of the webpages, so this is absolutely normal when website (or web app) is compiled OK but crashes while runtime or just behave unintentedly.

4. Do you experience slowdowns in 5.0? Currently we're focused on releasing ReSharper 5.0 so 4.5 issues are postponed for now.

0
Comment actions Permalink

Hey  there

  1. Firstly thanks for fixing 1
  2. and 2

  3. I can't believe the missing quote in number 3 thanks for pointing this out, I was always looking at the error part

  4. Yes I do experience slowdowns in 5.0,  it has improved some what but still not as smooth as not having resharper on or doing the trick I outlined in the other post.
    Do you have any idea why doing my trick would speed up resharper is it because something gets cleared etc? My thinking is if you can work that out then resharper would be so much quicker everywhere else. So I would say the problem exists in 4.5.1 and 5.0 builds


  5. I also this syntax highlighting probelm that I forgot to mention, it a very strange problem but I'm sure can be easily fixed: http://www.jetbrains.net/devnet/thread/282017?tstart=0


Keep up the great work

Regards DotnetShadow

0
Comment actions Permalink

About slowdown. I've no idea why it happens but our QA department has already been starting repeating the problem consistently. It would help us a lot of you VS under dotTrace and capture a snapshot of a slowdown. You're welcome to download the most recent dotTrace 4.0 build at http://www.jetbrains.net/confluence/display/NetProf/4.0+Nightly+Builds
Thanks in advance.

0
Comment actions Permalink

Hi there,

I will be happy to use dotTrace to capture a slowdown is there quickstarts or instructions on how to do this I'm a noobie when it comes to dotTrace

Regards DotnetShadow

0
Comment actions Permalink

Just run dotTrace then select profile on a local computer and chose devenv.exe to profile.

0
Comment actions Permalink

Thanks for that,

I just tried it but I have a bigger problem now, vs.net 2008 loads up I select my project and it just hangs with a waiting icon and never comes back. So I kept trying over and over still the same problem. I uninstalled the profiler and everything loads up correctly so I'm not sure what's going on with the latest DotTrace nightly build. The last version I tried was that on the 6th of Nov

So until I can get dotTrace to work I can't take a snapshot maybe I should try v3 of it?

DotnetShadow

0

Please sign in to leave a comment.