9 comments
Comment actions Permalink

Please provide more complete description of your problem, preferably with screenshots.

0
Comment actions Permalink

I am intrigued to know why you want me to submit a screen image and a description of the problem. I had expected your familiarity with the software would tell you this is a "tooltip" message that appears when editing an aspx file where a tag that includes the asp namespace appears, i.e. <asp:ListItem>.



Attachment(s):
NamespaceNotBound.JPG
0
Comment actions Permalink

You may be quite surprised with size of the out code base and amount of stuff we are familiar with. My request is purely practical, because there's always too much place for ambiguity. You should always provide as much information as possible if you want your problem solved.

This is normal XML NS warning - editor expects you to bound asp namespace prefix to its schema. There's should be "light bulb" popping up when you place caret inside red "asp" text.
Press Alt-Enter to activate intention and add appropriate schema definition.

0
Comment actions Permalink

It would be very nice if the software responded as you have suggestion but unfortunately it does not. Where is the appropriate schema to be added and what is the appropriate schema? I would have thought that the asp namespace would be implied in an aspx file. The context menu is less than helpful.



Attachment(s):
CreateNamespaceDeclaration.JPG
0
Comment actions Permalink

There's no specific support for ASP.NET or any other .NET specific technology in WebStorm/PhpStorm 1.0 and it is not planned. We can't provide any support regarding ASP.NET tag schema. .NET stuff is covered by other product http://www.jetbrains.com/resharper/index.html

0
Comment actions Permalink

I use resharper. I had hoped to use webstorm to validate and reformat aspx files. Is there a resolution of this problem?

0
Comment actions Permalink

There's no specific formatter for ASP.NET - HTML/XHTML/XML formatter will be applied depending on doctype.
Schema resolution does not significantly affect formatter AFAIK.
You can also simply suppress the inspection - however schema-based completion will not be available w/o proper asp xsd

0
Comment actions Permalink

This bug/feature is still present in latest WebStorm 2.0.1. I know, WebStorm does not support ASP.NET, but in my opinion adding some rule like "not to show errors for <asp: ...> elements" will be really nice. Or at least change the result of the inspection for asp: namespace elements within aspx and ascx files to warning/hint instead of error.
Thanks :)

0
Comment actions Permalink

Please file a feature request with all details on your expectations (may be some screenshots) to project issue tracker http://youtrack.jetbrains.net/issues/WI

0

Please sign in to leave a comment.