Book a Demo

Author Topic: .NET Framework instantiated objects  (Read 4508 times)

rescobar

  • EA User
  • **
  • Posts: 69
  • Karma: +0/-0
  • Viva Bolivia
    • View Profile
.NET Framework instantiated objects
« on: February 18, 2003, 12:09:01 pm »
Please somebody could explain me why the following statement

Protected WithEvents dgGradosRiesgo As System.Web.UI.WebControls.DataGrid

in a ASP.NET form produces an attribute in the resulting class reversed by EA instead of a separate class associated with the form??

Thanks for your kind help
Sergio Escobar
[email protected]

Steven Burton

  • Guest
Re: .NET Framework instantiated objects
« Reply #1 on: February 19, 2003, 10:14:57 am »
The statement you made is a variable declaration, not a class declaration. Reverse engineering should generate an attribute in the containing class, not a new class. If you need a new class, you must make a class declaration.

rescobar

  • EA User
  • **
  • Posts: 69
  • Karma: +0/-0
  • Viva Bolivia
    • View Profile
Re: .NET Framework instantiated objects
« Reply #2 on: February 21, 2003, 05:25:15 am »
Hi Steven!
I don't undestand how you make a "class declaration" or a "variable declaration". As I understand, a class should instantiated not declared as a variable.
.NET documentation establish: "The Protected keyword confers protected access on one or more declared programming elements. Protected elements are accessible only from within their own class or from a derived class. Protected access is not a superset of friend access", so it seems that Protected regards classes, not variables.
Please explain me these concepts.
Regards
Sergio Escobar
[email protected]