Build 448, code inspections does not work for ASP.NET projects

ReSharper 3.0 beta build 448, code inspections does not work for ASP.NET projects

6 comments
Comment actions Permalink

Hello Mileta,

I think we fixed it for latest build, watch next nightly (453).

Sincerely,
Ilya Ryzhenkov

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


MC> ReSharper 3.0 beta build 448, code inspections does not work for
MC> ASP.NET projects
MC>


0
Comment actions Permalink

Hi Ilya,

thanks for getting R# more and more stable, it's a breeze to work with.

The only thing to comes to my mind, is that with any of my solutions, adding
or removing a project somehow distorts the in-memory cache of R#, so that
it shows errors where there are none (such as missing references and such).

I'll name my problems here:
1) My projects all have references to DLLs in one folder, named "References".
All my projects have a post-build event that copies its output into that
folder.
This makes for less dependency problems in other areas. R# handles these
situations very well, but when adding and/or removing projects, it seems
to miss the ball.

2) This is especially true for WebService projects. When I add one webservice
project (in my solution I do generally not have added these, because VS2005
seems to lock some output files in that case), R# seems to not recognize
any of the references of the website/webservice project. About every line
is in error, while the project builds just fine.


I also use MSBuild files, that build my projects outside of VS2005, and updates
the same folder. R# recognizes the output generally smoothly. (it didn't
before ;) Very good marks here !!

3) When custom tools are used that update files behind the scenes, I generally
have to open the generated source file, to make R# see the new content.
R# seems to refresh its cache concerning that code file, and all is well.
If I don't, R# has no idea of the changes.

4) When generating proxies (for the webservices), I do this in batch files,
outside of VS2005. When the source file is generated, R# again has no idea.
I open the generated source file in VS2005, only then the cache is refreshed.

Are these issues that you are looking into, or do they sound new ?

Thanks for your thoughts,

Dirk

Hello Mileta,

I think we fixed it for latest build, watch next nightly (453).

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

MC>> ReSharper 3.0 beta build 448, code inspections does not work for
MC>> ASP.NET projects
MC>>


0
Comment actions Permalink

I forgot to mention one thing:

5) in the MSBUILD files, we have one top file, that imports the rest. The
child files have no knowledge of the others, but use their target names for
listing dependencies.
Resharper marks any target that is not recognized as a target in the same
file as an error. Can I (such as external properties) mark these as external
targets ? I think R# currently has no support for this ?

Thanks for your thoughts,
Dirk

Hi Ilya,

thanks for getting R# more and more stable, it's a breeze to work
with.

The only thing to comes to my mind, is that with any of my solutions,
adding or removing a project somehow distorts the in-memory cache of
R#, so that it shows errors where there are none (such as missing
references and such).

I'll name my problems here:
1) My projects all have references to DLLs in one folder, named
"References".
All my projects have a post-build event that copies its output into
that
folder.
This makes for less dependency problems in other areas. R# handles
these situations very well, but when adding and/or removing projects,
it seems to miss the ball.

2) This is especially true for WebService projects. When I add one
webservice project (in my solution I do generally not have added
these, because VS2005 seems to lock some output files in that case),
R# seems to not recognize any of the references of the
website/webservice project. About every line is in error, while the
project builds just fine.

I also use MSBuild files, that build my projects outside of VS2005,
and updates the same folder. R# recognizes the output generally
smoothly. (it didn't before ;) Very good marks here !!

3) When custom tools are used that update files behind the scenes, I
generally
have to open the generated source file, to make R# see the new
content.
R# seems to refresh its cache concerning that code file, and all is
well.
If I don't, R# has no idea of the changes.
4) When generating proxies (for the webservices), I do this in batch
files,
outside of VS2005. When the source file is generated, R# again has no
idea.
I open the generated source file in VS2005, only then the cache is
refreshed.
Are these issues that you are looking into, or do they sound new ?

Thanks for your thoughts,

Dirk

>> Hello Mileta,
>>
>> I think we fixed it for latest build, watch next nightly (453).
>>
>> Sincerely,
>> Ilya Ryzhenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
MC>>> ReSharper 3.0 beta build 448, code inspections does not work for
MC>>> ASP.NET projects
MC>>>


0
Comment actions Permalink

Mileta,

We have introduced a bug prior to publishing build 448, that prevented ASP
files from referencing resources declared in
App_GlobalResources and App_LocalResources as well as Web References.
The bug is already fixed and the fix is available in recent nightly build,
that may be downloaded from
http://www.jetbrains.net/confluence/display/ReSharper/Nightly+Builds

If it is not your case, could you provide us with a small sample solution,
that illiterates the problem?
--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Sorry, but this is not yet fixed, build 454.

0
Comment actions Permalink

Millet,

Could you provide us with a sample solution, please?

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


0

Please sign in to leave a comment.