Build Script Support issues

Hello

I have few problems with build script support in R# (using build 265
with VS.NET 2005) I'm using MSBuild.


1) How R# detects that actual opened file is build script? By file
extension or by anything else ?
For example for file with extension .proj R# does everything described
in documentation but for file extension wdproj (Web Deployment Project)
no R# feature is available :(
I thing that these feature will be much helpful if R# looks for the
xmlns in the file header (
xmlns="http://schemas.microsoft.com/developer/msbuild/2003" for msbuild)
than when it is active by file extension...


2) Visual studio IntelliSense is not completely disabled even for files
where R# works ok. For example when i type "]]>
Is there any chance to change this ? :)
Because this makes msbuild support in R# only 10% useful it should be. I
can't imagine anybody using absolute paths for their task assemblies...
Consequences of this design is:
- R# doesn't list tasks in "available tasks" popup (VS.NET does so thus
is not the worst issue)
- #R doesn't recognize Items and Properties created by these tasks so
these are not available in code completion.....

In short, all these issues makes all the build script support in R#
useless for me.......and it makes me angry because i love R# ! :)

With regards

Michal Levy

2 comments
Comment actions Permalink

Can anyone from JB comment on this, please ?

I've buyed several copies of R# for the team I'm leading because of it's
outstanding features.... I do not like the fact that some of the
important features are only "half baked" or buggy, even in release
version and after second bug fix release :((

Thanx for your time

Michal Levy
Mediaresearch a.s.

Michal Levy wrote:

Hello

I have few problems with build script support in R# (using build 265
with VS.NET 2005) I'm using MSBuild.


1) How R# detects that actual opened file is build script? By file
extension or by anything else ?
For example for file with extension .proj R# does everything described
in documentation but for file extension wdproj (Web Deployment Project)
no R# feature is available :(
I thing that these feature will be much helpful if R# looks for the
xmlns in the file header (
xmlns="http://schemas.microsoft.com/developer/msbuild/2003" for msbuild)
than when it is active by file extension...


2) Visual studio IntelliSense is not completely disabled even for files
where R# works ok. For example when i type "<", VS pops up small window
with available items (Target for example). When i type "<Target" and
type space, list of attributes is displayed....again from VS.NET. When i
want to see R# vatiants of these, i must press Ctrl+Space

3) (Last one i discussed earlier with Andrey Serebryansky)
I know that R# doesn't load any task assembly (UsingTask) specified
using a property value...for example:
<UsingTask
AssemblyFile="$(MSBuildProjectDirectory)\MSBuild.Community.Tasks.dll"
TaskName="Add" />
Is there any chance to change this ? :)
Because this makes msbuild support in R# only 10% useful it should be. I
can't imagine anybody using absolute paths for their task assemblies...
Consequences of this design is:
- R# doesn't list tasks in "available tasks" popup (VS.NET does so thus
is not the worst issue)
- #R doesn't recognize Items and Properties created by these tasks so
these are not available in code completion.....

In short, all these issues makes all the build script support in R#
useless for me.......and it makes me angry because i love R# ! :)

With regards

Michal Levy

0
Comment actions Permalink

Hello Michal,
1. Currently ReSharper detects a MSBuild script only if it has '.proj' extension.
If you'd like ReSharper to detect other extensions too, please add a request
to our tracking system: http://www.jetbrains.net/jira/browse/RSRP. Probably
you're right and looking at the referenced xmlns is a better way to detect
a MSBuild script.

2. To completely turn off Visual Studio IntelliSense in build files you should
go to Tools > Options > Text Editor > XML > General tab and uncheck the 'Auto-list
members' option.

3. Could you please add a request regarding this issue to our tracking system?
We will do our best to fix this problem.

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

Hello

I have few problems with build script support in R# (using build 265
with VS.NET 2005) I'm using MSBuild.

1) How R# detects that actual opened file is build script? By file
extension or by anything else ?
For example for file with extension .proj R# does everything described
in documentation but for file extension wdproj (Web Deployment
Project)
no R# feature is available :(
I thing that these feature will be much helpful if R# looks for the
xmlns in the file header (
xmlns="http://schemas.microsoft.com/developer/msbuild/2003" for
msbuild)
than when it is active by file extension...
2) Visual studio IntelliSense is not completely disabled even for
files where R# works ok. For example when i type "<", VS pops up small
window with available items (Target for example). When i type
"<Target" and type space, list of attributes is displayed....again
from VS.NET. When i want to see R# vatiants of these, i must press
Ctrl+Space

3) (Last one i discussed earlier with Andrey Serebryansky)
I know that R# doesn't load any task assembly (UsingTask) specified
using a property value...for example:
<UsingTask
AssemblyFile="$(MSBuildProjectDirectory)\MSBuild.Community.Tasks.dll"
TaskName="Add" />
Is there any chance to change this ? :)
Because this makes msbuild support in R# only 10% useful it should be.
I
can't imagine anybody using absolute paths for their task
assemblies...
Consequences of this design is:
- R# doesn't list tasks in "available tasks" popup (VS.NET does so
thus
is not the worst issue)
- #R doesn't recognize Items and Properties created by these tasks so
these are not available in code completion.....
In short, all these issues makes all the build script support in R#
useless for me.......and it makes me angry because i love R# ! :)

With regards

Michal Levy



0

Please sign in to leave a comment.