Bug 3542 - "param" tag of method comments is closed incorrectly
Summary: "param" tag of method comments is closed incorrectly
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-02-20 03:59 UTC by René Ruppert
Modified: 2012-11-27 09:28 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description René Ruppert 2012-02-20 03:59:06 UTC
My method has a couple of comments on it already:

/// <summary>Does something</summary>
/// <param name="i">an integer</param>
/// <returns>a bool</returns>
public bool foo(int i);

If I now add a second parameter and want to document that too, I insert a line below "<para". Intellisens is completing this to: <param name="">

Issue 1: no closing /param tag is added
Issue 2: if I remove the closing brace and type it again, a "/para" tag is added, instead of a "/param" (missing "m").
Comment 1 Mike Krüger 2012-02-21 03:17:38 UTC
Comment 2 Sam 2012-11-25 03:08:52 UTC
What version was this fixed in? I am able to reproduce this in on Mac OS X and was just about to report the problem but found this existing instead.
Comment 3 René Ruppert 2012-11-25 10:29:19 UTC
I can confirm that the problem is back. It was fixed but is now in 3.x for sure.
Comment 4 René Ruppert 2012-11-25 10:29:31 UTC
I can confirm that the problem is back. It was fixed but is now in 3.x for sure.
Comment 5 Mike Krüger 2012-11-27 09:28:53 UTC
I'm often 1-2 versions ahead - it's fixed.