Re: XML Comment Screwed - Possibly a bug in VB??

Michael,

I am quite "thick skinned" so it didn't bother me too much. I know I am not the most knowledgeable person on VB.NET as I only use the bits of the system that work for me in getting the job done. I don't have a lot of time to get to really know the product to the level that you guys do, even though I have been using VB since version 1.

I am a self employed developer and keep promising myself that when I have built up some spare funds I should get on a course that teaches me the full working of the Visual Studio IDE and a deeper understanding of VB and the ..NET framework as I am sure I am not getting the best out of it.

I just wanted to make Stephany aware that her style of response seems very unwelcoming and her tone unnecessarily superior. I have always found that these newsgroups are generally a friendly and welcoming place where developers can get help and advice from their peers without fear of being scolded for not knowing something that an expert feels they should know. I would love to spend months playing with Visual Studio and getting to know every aspect of it, but I have to earn a living and that stops me from doing that.

Thanks for taking the time to respond to this as it's nice to know that some experts do care about those who come here looking for help.

Siv

"Michel Posseth [MCP]" <MSDN@xxxxxxxxxxx> wrote in message news:%23$h6UYxzIHA.552@xxxxxxxxxxxxxxxxxxxxxxx
Siv ,,,

Don`t get upset about postings in the groups ,, some people over here are indeed a bit rude in there answering
this may have several reassons .

1. The person asnwering is really a sociopath
http://wiki.answers.com/Q/How_do_you_know_if_someone_is_a_sociopath

2. The person answering lives in a european country wich is competing in the EK soccer and he / she is not wearring orange at this moment
especially Italian and French people are a bit tricky at the moment ;-)
http://en.wikipedia.org/wiki/Netherlands_national_football_team ( scroll to the 2008 section below )

3. The person answering might not have his / her day ,,,,, most of the times a look at other postings of this person at this day and other days is enough to know if this is true .

4. Not all persons in this group ( me for instance ) are native English speakers , so remember that sometimes the postings are interpreted in a different way as they were intended.

If you are a bit longer active in this groups you will know them bether , and you will see that we are all humans here and most of the times only option 2, 3 or 4 apply . Ocassionally we have a option 1 but i can ensure you that those people are a long time not seen here .



regards

Michel Posseth






"Siv" <g@xxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht news:upN4kdtzIHA.5472@xxxxxxxxxxxxxxxxxxxxxxx
Stephany,

That may be true, I wasn't looking for excuses, like most VB'ers who come here we are looking for answers to problems that we can't resolve ourselves. I didn't come here to be scolded for not understanding the internal workings of XML. I came here to post what I thought was a bug (and still do actually) in the VB parser. I also posted it because in finding that when I removed the ampersand the issue went away. My hope being that if another VB user like me who doesn't know why this "warning" comes up and doesn't know how to get past it will read my post (and your replies subsequently) and get a resolution to the problem. I also hoped that one of the developers from Microsoft may become aware of it and perhaps tighten up the warning messages so that the warning message can be a bit more focused on what is really upsetting it.

The responses you give or rather the way that you deliver them, seem to be a bit patronising. People should not be discouraged from asking questions here even if to an experienced Guru like you they are child like. If all you are about is showing off how clever you are at the expense of other users who may not know as much as you, then you really shouldn't be here! Your responses remind me of the Linux forums a few years back where newbies were roasted for not knowing the internal working of BASH or some other esoteric Unix command line switch.

Siv


"Stephany Young" <noone@localhost> wrote in message news:OoQ1XGtzIHA.3680@xxxxxxxxxxxxxxxxxxxxxxx
Ignorance is no excuse.


"Michel Posseth [MCP]" <MSDN@xxxxxxxxxxx> wrote in message news:%23ri$16szIHA.4816@xxxxxxxxxxxxxxxxxxxxxxx
Well some people have the option on in the ide that Warning=error ( just for the simple fact that a warning then blocks a built until you solved the issue )
so maybe he wasn`t aware :-)

I guess that a lot of coders are not aware of the fact that the documentation is in fact true XML that has a use on its own and can even be used in externall reporting and tracking tools such as Ghostdoc , Sandcastle etc etc etc

regards

Michel



"Stephany Young" <noone@localhost> schreef in bericht news:eFMJuTszIHA.3680@xxxxxxxxxxxxxxxxxxxxxxx
Yes, certainly the user made an error, but the point is that VS reported a warning and not an error.


"Michel Posseth [MCP]" <MSDN@xxxxxxxxxxx> wrote in message news:u99HNHszIHA.4816@xxxxxxxxxxxxxxxxxxxxxxx
Well in fact it is an error Stephany ,, but not an error of the system but an error of the person who wrote the comment :-)
as XML follows the same rules as HTML for special characters , it seems that this person wasn`t aware of this fact
the systems just warns that the XML doc will be broken


regards
michel




"Stephany Young" <noone@localhost> schreef in bericht news:uh%23yVlozIHA.2292@xxxxxxxxxxxxxxxxxxxxxxx
1. It's NOT an error - It is a warning!
They are totally different things.

2. & is the escape character in XML.
If you wish to include an & in XML then you need
to specify it as &amp;


"Siv" <g@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:0CF67692-E4BF-487D-B96C-C794E7785FAD@xxxxxxxxxxxxxxxx
Hi,

Just busily coding away and removed a procedure from my code and all of a sudden an error came up miles away from the location of the piece of code I removed and it relates to the XML comment inserted at the top of the procedure.

I had this happen once before and I couldn't fathom why it was complaining, the XML comment is like this:

''' <summary>
''' If the Bonds flag is set in the security record we have at least one Bond & Floating Charge
''' This routine locates the bonds that are linked to the Security Record and adds them as sub nodes to
''' the main Bonds node.
''' </summary>
''' <param name="ParentNode"></param>
''' <remarks></remarks>

This gives an error:

"Warning 1 XML documentation parse error: Whitespace is not allowed at this location. XML comment will be ignored. "

I then discovered if I remove the "&" ampersand symbol the error message goes away???

Is this a "by design" thing or is this a bug in the XML comments??

Siv













.

Loading