Question for ReSharper 3.0: No ASP.NET support anymore?

Hello Harald,

unfortunately, this is true to a certain extent: ReSharper 3.0 indeed doesn't
recognize the <%Register> ASP directives, so it is unable to figure out
correct references between ASPX files and user controls. In fact, this has
never worked properly in ReSharper. In ReSharper 2.x all the contents of
Web Sites
was considered to be a single project, which is also not correct - e.g. this
caused separate classes to be treated as different parts of the same class,
which is
clearly wrong. So in 3.0 we re-designed ASP.NET support and attempted to
mimic the compilation model of ASP.NET, but our efforts have only partially
been successful,
and the mentioned problem with <% Register> directives is one of the unresolved
issues.

We will try to address these issues ASAP, already in the 3.0.2 bugfix update
(3.0.1 is a critical bugfix update which is going to be released very soon).
Unfortunately, VS's
Web Sites compilation model is a kind of 'black box', and the module (and
references) structure of Web Site is not exposed in API. So we're looking
into a radically different way
to support Web Sites, similar to what VS 2005 does.

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

I've just read in the EAP forum that ReSharper 3.0 might not support
ASP.NET anymore: UserControls are not recognized anymore and so all
their properties are markes as invalid by ReSharper (see thread
http://www.intellij.net/forums/thread.jspa?threadID=267676 ).

Is this still the case for the released version? It will be impossible
for us to upgrade to 3.0 if it turns out that ASP.NET UserControls
support (which is are core functionality) is now broken in 3.0.

Harry

"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:c8a8945d1c228c982e99a65e603@news.intellij.net...

Hello Harald,

>

unfortunately, this is true to a certain extent: ReSharper 3.0 indeed
doesn't recognize the <%Register> ASP directives, so it is unable to
figure out
correct references between ASPX files and user controls. In fact, this has
never worked properly in ReSharper. In ReSharper 2.x all the contents of
Web Sites
was considered to be a single project, which is also not correct - e.g.
this caused separate classes to be treated as different parts of the same
class, which is
clearly wrong. So in 3.0 we re-designed ASP.NET support and attempted to
mimic the compilation model of ASP.NET, but our efforts have only
partially been successful, and the mentioned problem with <% Register>
directives is one of the unresolved issues.

>

We will try to address these issues ASAP, already in the 3.0.2 bugfix
update (3.0.1 is a critical bugfix update which is going to be released
very soon). Unfortunately, VS's
Web Sites compilation model is a kind of 'black box', and the module (and
references) structure of Web Site is not exposed in API. So we're looking
into a radically different way
to support Web Sites, similar to what VS 2005 does.

Do you have the same problem with Web Application Projects? We don't use web
sites, and never will.
--
John

John,

No, it should be ok with WebApplication projects.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

No, it should be ok with WebApplication projects.

Hmm, we are also using WebApplication Projects.
So can anybody confirm that UserControls registered with <%Register>-directives in WebApplication Projects are recognized correctly with ReSharper 3.0?

Thanks,
Harry

Harrald,

I've just checked. It works at my side.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"