Web Forms :: Want To Support Defining Property When Declaring The Instance Of This User Control
Jun 10, 2010
I created user control. It exposes string[] public property (it may be List<string> or whatever). I want to support defining this property in aspx code, when declaring the instance of this usercontrol. Something like this:
I have a Interface for CRUD operations.and some classes implemented it.I want to design a user control that have two buttons:insert and delete,to reuse this control over my forms.this class must have a instance of my interface to do insert and delete tasks (if I'm right).this is my interface:
[Code]...
my problem is,i can't declare a property of type ISchoolSystemRepository in user control,because i must pass T for interface.
I am trying to assign user control from another user control ..first time its binding control successfully but when we refresh the data its giving error
saying "Object reference is not set an instance".
how to refresh data from another user control ...
My senerio below :
1 Aspx page
2. User control
calling usercontrol databinding method from aspx page but once it get refreshed ,not allowed to bind it again..
I've got a web site that has a master page and that master page (mpMaster that has a user control ucControl1) which has a sub user control (ucControl2), this user control has a property which accepts a value. Now, I have a page that uses the master page and on this page I have another user control (ucPageControl), I need to find a way of setting the value in ucControl2 from ucPageControl. Is this possible at all?
i am trying to enter a value into a texbox that is placed inside a user control called CollectionRequest. i have referenced this user control in my code behind and created an instance of it but i seem to get the above error when i try to enter some manual text. code as follows:
protected CollectionRequest collReq; protected void Page_Load( object sender, EventArgs e ) { collReq = (CollectionRequest)LoadControl("~/CollectionRequest.ascx"); TextBox _txt_address = (TextBox)collReq.FindControl("txt_Address"); _txt_address.Text = "thisi is an address"; control has been referenced in source file <%@ Reference Control="~/CollectionRequest.ascx"%>
i am caling this code in my Approval.ascx.cs code. both the user controls are displayed together in the default.aspx page one above the other.
<%@ Import Namespace="System.Data.SqlClient" %> <script runat="server" > Dim connStr As String = ConfigurationManager.ConnectionStrings("cc").ConnectionString.ToString dim db As New Data.SqlClient.SqlConnection(connStr)
why this error
Object reference not set to an instance of an object.
I have designed a basic web user control to enter some values in a table. The control worked fine if it is used without similar control on same page. When another instance is pasted with different id, then both stopped working.
I have to load the values to parent page from the popup page. The popup page will be in another website(saparate server).
I used opener.document.getElementById('parentcontrolID'), this is working fine if i run in the local(i created saparate virutual directory for popup page website in my local machine) system the values are loaded properly. but Once i move to the different servers it's not working. getting this javascript error message "Object doesn't support this method or property" in the popup page bottom left corner.
What will be the problem.
Whether we can load the value to parent page from popup page even both are in saparate server?
I'm having trouble to access a Parent's property in User Control. I don't know how to access the parent. The Parent Page's name is Search.aspx. I saw the example below and tried it:
[Code]....
Than I could access the Parent's Property, but when I ran the website I got these errors:
1. The user control is not declared in the parent page 2. The user contol has a circular reference
I have a user control that has multiple instances on a single page.
Is it possible to have each instance use a unique ValidationGroup? I could expose a property, but I'm wondering if there's any way to do it automatically.
I am trying to sort in gridview however I got some error message in _dopostback function which shows "Microsoft JScript runtime error: Object doesn't support this property or method" at theForm.submit()
'Person' is not a member of type 'Transient.rowtype[(Id,Edm.Int32(Nullable=True,DefaultValue=))]' in the currently loaded schemas.
Does the EntityDataSource not support walking the relationships? How would you do this with the EntityDataSource?
Also the @userName parameter is being added in the code behind for now. Extra points for anyone who knows how to specify a username parameter directly in the WhereParameters collection.
I have a Master Page that has several User Controls on it. The MasterPage code behind does some work to calculate a value that needs to be used in all of the UserControls. From the UserControl code behind, how do I access the public property of the MasterPage that I have set?
I'm constructing a User Control that will have one Property called "ContractIdx". Here's how I've constructed this Property:
public int ContractIdx { get { return Convert.ToInt32(this.Attributes["ContractIdx"]); } set { this.Attributes["ContractIdx"] = value.ToString(); } }
I'm initially loading the User Control by passing a parameter to it and setting ContractIdx accordingly. That all works fine.
Upon Postback though I'm loading the User Control without any parameters and then setting its ID property to what it was before the Postback. My understanding was that if I did this then ViewState would properly restore everything. Yet apparently this is not the case with the "ContractIdx" attribute.
Where am I mistaken in my understanding? How should I change things to get this mechanism to work?
There is one user control say uControl.ascx. This has a public property Message. There are 2 aspx pages Default.aspx and Home.aspx which has the user control uControl.ascx. When a sumit button from Default.aspx is clicked some action takes place and the value for Message is set and then execution is redirected to Home.aspx. In Home.aspx the value for Message is lost.
Is there anyways that the value of Message is retained for both the aspx pages?
I created a simple gridview user control with a custom property ProfileType which should load different records depending on the ProfileType value when attaching to a web page.
This is my web page:
[code]....
how I can expose user control custom property at its code-behind file.
In my project, I need to create a user control to handle the sorting and pagination of all the grids in the application. The grid however will be different in different pages with different formatting.
I am able to do this by exposing a property from user control which takes gridview as the input.
then in page load, i bind this grid, and assign the sorting and paging event handlers to this gridview variable.
This way I am able to do the sorting and paging, but the problem is I have to bind the grid in all the post backs, and then in the sorting and paging events.
So when a user sorts, I have to bind the grid twice, once in page_load and then in sort event of user control.
I can store the first set of records in viewstate and bind that in page load, but is there any other way, so that i dont need to bind the grid in all post backs but only inside of not postback.
Traditionally with an Object Data Source, the wired up class will have its public properties available for binding (i.e. Gridview columns, etc.) which works well. But what if one of my wired up business objects has a property that is an object itself; can I drill down to a property on that object property and still use it?
So in additiona to the traditional:MyBusniessObject.OrderID...I want to use:MyBusniessObject.Customer.NameID Your 1st response might be to just wire up the 'Customer' class, but I need properties both on 'MyBusinessObject'and 'Customer'. I do not think this can be done, as the ODS will not display properties on an object instance property. I have tried manually typing in the drilled down value as well, but that wasn't a success either.