By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,154 Members | 1,050 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,154 IT Pros & Developers. It's quick & easy.

Weird build error

P: n/a
My aspnet web was working perfectly fine, then I added a second datalist to
a page. The datalist can be formatted in the designer and everything looks
fine. In the codefile, I can see the datalist after me. and intellesense
works for the control datalist2. Build\Rebuild all reports a failure, but
does not specify the errors. Running the page results in a message box
'There were build errors. Would you like to continue and run the last
successful build?'. There are zero errors shown on the error list. Weird,
right? AND, when I comment out lines in the codefile that reference the
datalist2, the web runs just fine. So we have
the control displays correctly in the designer
Intellesense shows the control's members and methods in the codefile
Rebuilding from the menu fails for some unspecified reason
Running the web fails
But all works correctly when the lines in the codefile referencing the
datalist (ie, datalist2.enabled = true, or anything else) are commented out.

Anyone less confused by this than me?
Nov 29 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Sorry, this is in VWD 2005 Express

"Lisa Calla" <sp*********@herplace.com> wrote in message
news:e_********************@eatel.net...
My aspnet web was working perfectly fine, then I added a second datalist
to a page. The datalist can be formatted in the designer and everything
looks fine. In the codefile, I can see the datalist after me. and
intellesense works for the control datalist2. Build\Rebuild all reports a
failure, but does not specify the errors. Running the page results in a
message box 'There were build errors. Would you like to continue and run
the last successful build?'. There are zero errors shown on the error
list. Weird, right? AND, when I comment out lines in the codefile that
reference the datalist2, the web runs just fine. So we have
the control displays correctly in the designer
Intellesense shows the control's members and methods in the codefile
Rebuilding from the menu fails for some unspecified reason
Running the web fails
But all works correctly when the lines in the codefile referencing the
datalist (ie, datalist2.enabled = true, or anything else) are commented
out.

Anyone less confused by this than me?

Nov 29 '05 #2

P: n/a
Viewing the compiler output shows the following error: (which again doesn't
make sense to me) 'DataList2' is not a member of 'EqsWeb'
EqsWeb.aspx is the name of the form. It's perfectly comfortable with
DataList1. DataList2 is clearly in the aspx source with the runat=server
attrib set and no obvious formatting errors (it also shows up just fine in
the designer). I'm just at a loss here.
"Lisa Calla" <sp*********@herplace.com> wrote in message
news:e_********************@eatel.net...
My aspnet web was working perfectly fine, then I added a second datalist
to a page. The datalist can be formatted in the designer and everything
looks fine. In the codefile, I can see the datalist after me. and
intellesense works for the control datalist2. Build\Rebuild all reports a
failure, but does not specify the errors. Running the page results in a
message box 'There were build errors. Would you like to continue and run
the last successful build?'. There are zero errors shown on the error
list. Weird, right? AND, when I comment out lines in the codefile that
reference the datalist2, the web runs just fine. So we have
the control displays correctly in the designer
Intellesense shows the control's members and methods in the codefile
Rebuilding from the menu fails for some unspecified reason
Running the web fails
But all works correctly when the lines in the codefile referencing the
datalist (ie, datalist2.enabled = true, or anything else) are commented
out.

Anyone less confused by this than me?

Nov 29 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.