Solution Analysis Find Errors in *.aspx pages?

I'm new to resharper and I can't figure out if I'm doing something wrong.  I'm trying out the new 4.5 Beta and my main goal is to catch .net code errors in aspx and ascx files.  The web site and documentation gave me the impression that the solution analysis would find errors in aspx and ascx files that would normally not be found by the compiler unless you open the file. However, after letting the solution anlysis run (our project is large and it took several hours) it did not find any of these errors.

As an example, my main problem is that I have lots of aspx files where we use syntax like:

     Title="<# MyClass.MyObject.Title #>"

Then we change a namespace and now we need to change the syntax to:

     Title="<# MyClass.NewNamespace.MyObject.Title #>"

This kind of change is not picked up by the compiler and we can only find them when they cause errors at runtime or when you open the file in the Visual Studio html editor.  These are content files and the large number of files makes opening them all in the editor not feasible.

Does ReSharper handle this or not?  Is there a setting that I do not know about?  Thanks in advance for your help.

3 comments

I have an update to this question.

I have reproduced my problem in a small test solution.  The problem appears to be between a VB.Net web project that is referencing a C# class library.  I created a C# class library that has only a static string, which I reference and display on an aspx web page.  If the web project and class library are C# and I change the namespace of the referenced string, ReSharper picks up the change and gives me an error.  If the web project is VB.Net and the class library is C# and I change the namespace, I get no error from ReSharper and the reference causes an error at runtime.  Is this expected behavior or is there a workaround?

0

Okay, one more update.  The problem seems to be with analyzing the aspx and ascx pages of VB.Net web projects.  When I use a C# project, I get intellisense and the solution analysis picks up any errors, even if I'm referencing something in a VB.Net dll.  However, when I use a VB.Net project, I don't get intellisense and the solution analysis doesn't pick up any errors, no matter if the dll is C# or VB.Net.

0

Unfortunately, our support for VB.NET is limited. In particular, we do not
analyze vb.net files (including aspx pages with vb.net language) for syntax
errors. We currently have no plans for supporting error analysis in vb.net.

Valentin Kipiatkov
CTO and Chief Scientist
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Okay, one more update. The problem seems to be with analyzing the
aspx and ascx pages of VB.Net web projects. When I use a C# project,
I get intellisense and the solution analysis picks up any errors, even
if I'm referencing something in a VB.Net dll. However, when I use a
VB.Net project, I don't
get intellisense and the solution analysis doesn't pick up any
errors, no matter if the dll is C# or VB.Net.
---
Original message URL:
http://www.jetbrains.net/devnet/message/5234621#5234621



0

Please sign in to leave a comment.