valid roleManager app.config setting fails to parse - by Simon Dahlbacka

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 508146 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 11/4/2009 5:12:45 AM
Access Restriction Public


clearing the providers collection of rolemanager using <clear></clear> fails to parse even though it should be exactly the same as using <clear/>.
Using short tag <clear/> works as expected.
Sign in to post a comment.
Posted by Stefan [MSFT] on 11/9/2009 at 4:08 PM
As part of the ongoing process for the VS 2010 release we review and consider historical feedback for inclusion in the product. Ideally we would be able to address all requested new features, however we do have to limit the ones that ultimately are implemented.

At this stage of the product lifecycle we are only concentrating on critical bugfixes. As a result we do not plan to update the <provider /> section parsing to allow <clear></clear>. Instead developers will have to continue to use the short-hand <clear /> syntax.

Thank you though for submitting your bug report on Connect.
Posted by Simon Dahlbacka on 11/9/2009 at 12:07 AM
Attached demo project.
Posted by Microsoft on 11/8/2009 at 11:24 PM
Thanks for reporting this issue.

In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Please provide us with a demo zipped project file so that we can conduct further research.

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.

Visual Studio Product Team
Posted by Microsoft on 11/5/2009 at 1:26 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted.

Thank you,
Visual Studio Product Team