could you please clarify what do you mean? The files under the 'Solution Items' virtual folder should be available in 'Go To File' but ReSharper doesn't consider them as regular project items. For instance, if a C# file is placed under 'Solution Items', ReSharper will not analyze it. The reason is that such files simply don't have enough context information to do any serious analysis - e.g. it's unclear what types/assemblies are referenced from them and so on. Isn't this is the case for you? Thanks.
The reason is that such files simply don't have enough context information to do any serious analysis - e.g. it's unclear what types/assemblies are referenced from them and so on. Isn't this is the case for you?
Absolutely. Thanx.
I am used these files for code clips, and making dirt prototypes for classes. Its useful - VS IDE made basic parsing for this sources, but this items is not include in builds.
(Also possible to make txt, xml, xslt, shemas, html - maybe its useful to make global descriptions for solutions, when solution contain more than one project)
My simple think is about R# visual assistance (colors) in these files like in normal sources, but its realy not critical.
ReSharper's treatment of such files also depends on their extensions - what I said in my previous post applies mostly to C# files. MSBuild and Nant scripts under solution items which are more or less common are analyzed as if they were in a project.
>> The reason is that such files simply don't have enough context >> information to do any serious analysis - e.g. it's unclear what >> types/assemblies are referenced from them and so on. Isn't this is >> the case for you? >>
Absolutely. Thanx.
I am used these files for code clips, and making dirt prototypes for classes. Its useful - VS IDE made basic parsing for this sources, but this items is not include in builds. (Also possible to make txt, xml, xslt, shemas, html - maybe its useful to make global descriptions for solutions, when solution contain more than one project)
My simple think is about R# visual assistance (colors) in these files like in normal sources, but its realy not critical.
Hello ivan.tsarevich,
could you please clarify what do you mean? The files under the 'Solution
Items' virtual folder should be available
in 'Go To File' but ReSharper doesn't consider them as regular project items.
For instance, if a C# file is placed under 'Solution
Items', ReSharper will not analyze it. The reason is that such files simply
don't have enough context information to do any serious analysis -
e.g. it's unclear what types/assemblies are referenced from them and so on.
Isn't this is the case for you? Thanks.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9175bf58c842e6365f7c44@news.intellij.net...
Absolutely. Thanx.
I am used these files for code clips, and making dirt prototypes
for classes.
Its useful - VS IDE made basic parsing for this sources, but
this items is not include in builds.
(Also possible to make txt, xml, xslt, shemas, html - maybe its useful
to make global descriptions for solutions, when solution contain more
than one project)
My simple think is about R# visual assistance (colors) in these files like
in normal sources, but its realy not critical.
Thanx,
ivan.tsarevich
P.S.
http://msdn2.microsoft.com/en-us/library/zk273747.aspx
Hello ivan.tsarevich,
ReSharper's treatment of such files also depends on their extensions - what
I said in my previous post
applies mostly to C# files. MSBuild and Nant scripts under solution items
which are more or less common are
analyzed as if they were in a project.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> The reason is that such files simply don't have enough context
>> information to do any serious analysis - e.g. it's unclear what
>> types/assemblies are referenced from them and so on. Isn't this is
>> the case for you?
>>