Nice. It doesn't tell me any error with my code, but I get a bunch of errors with code that was apparently generated automatically. Unfortunately, I don't know enough about Microsoft's code to fix it for them. I've examined my source file but don't see anything wrong with it. My source file has some server-side scripting that is in the same file as the HTML.
> Nice. It doesn't tell me any error with my code, but I get a bunch of errors > with code that was apparently generated automatically. Unfortunately, I > don't know enough about Microsoft's code to fix it for them. I've examined > my source file but don't see anything wrong with it. My source file has some > server-side scripting that is in the same file as the HTML.
> I have no idea how to proceed on this.
> Any tips?
> Jonathan
It looks like you did not define any class. Please read some tutorials about ASP.NET before you start copying and pasting code. If you use Visual Studio, try to create new Web Form and see what classes and methods it will create.
You page class must have following
public partial class test_test: System.Web.UI.Page {
This is incorrect. When everything is placed in a single file, you do not need to define the class--in fact you cannot! I have countless pages created this way.
I am not in need of basic ASP.NET tutorial--I've built dozens of sites. I'm in need of advanced methods of troubleshooting some of ASP.NET's quirks. I accept these errors may be the result of my error somewhere, but ASP.NET should be able to do a little better job of telling me what that error is.
> Nice. It doesn't tell me any error with my code, but I get a bunch of > errors with code that was apparently generated automatically. > Unfortunately, I don't know enough about Microsoft's code to fix it for > them. I've examined my source file but don't see anything wrong with it. > My source file has some server-side scripting that is in the same file as > the HTML.
> This is incorrect. When everything is placed in a single file, you do not > need to define the class--in fact you cannot! I have countless pages created > this way.
> I am not in need of basic ASP.NET tutorial--I've built dozens of sites. I'm > in need of advanced methods of troubleshooting some of ASP.NET's quirks. I > accept these errors may be the result of my error somewhere, but ASP.NET > should be able to do a little better job of telling me what that error is.
> Jonathan
When you said "I don't know enough about Microsoft's code" it sounds like you were new in this subject ;-) especially because the error message was more or less clear and correct. Anyway, glad that you fixed it now.
> I managed to resolve this. My form page had an extra '}' in the > client-side script area yet the page didn't flag any errors.
This is a difficult area, however, as the compiler is concerned with either
a) script blocks with runat=server b) code files
Other bits in the tagged files are not the major concern. This is changing, over time, as javaScript (or ECMAScript) is becomming more and more popular as people create object libraries in JavaScript (jQuery, etc). And with AJAX becomming more prevalent, you will see even more.
So the IDE is slowly catching up, but tooling always lags behind technology. It is unfortunate, perhaps, but the bits have to work first before the devs can understand how the tool should react.
|
