[Mono-bugs] [Bug 359392] New: Setting SqlDataSource. ConnectionString causes all controls' properties go back to initial value in FormView

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Wed Feb 6 18:23:36 EST 2008


https://bugzilla.novell.com/show_bug.cgi?id=359392


           Summary: Setting SqlDataSource.ConnectionString causes all
                    controls' properties go back to initial value in
                    FormView
           Product: Mono: Class Libraries
           Version: 1.9.0
          Platform: x86-64
        OS/Version: openSUSE 10.3
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: psoldack at wp.pl
         QAContact: mono-bugs at lists.ximian.com
          Found By: DeveloperNet


Created an attachment (id=193504)
 --> (https://bugzilla.novell.com/attachment.cgi?id=193504)
Application

Description of Problem:
When SqlDataSource.ConnectionString is set (let us say in Page_Load) it causes
all controls' properties go back to initial value in FormView.

Steps to reproduce the problem:
1. Unzip attachment to a folder.
2. Change ConnectionString in .aspx file to any valid database (you can change
ProviderName as well). It doesn't read any data from database because alla data
are in SQL SELECT statement.
3. Run xsp2
4. Use browser to start this application.
5. Click link inside application. Labels show up.
6. Add query string parameter "reload=1" and let it run again.
7. Click link again and see that label doesn't show.


Actual Results:
After setting ConnectionString control properties go back to initial value.

Expected Results:
Setting ConnectionString shouldn't change control properties. (As in MS.NET)

How often does this happen? 
Always.

Additional Information:
Bug existed at lease since Mono 1.2.5. Similar problem can be in GridView etc.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list