J
Jim Andersen
Could someone clarify this behaviour ?
In .Net 1.1 (Vis Stu 2003), I could make a Class module, a .vb file, with a
bunch of global functions.
In my aspx-pages I could then call those functions.
The "old" 1.1 project had name A, and the vb-file started with
Namespace A
Public module Module 1
Public Function ZZ
and in the CBF file the code started with
Namespace A
BUT
In 2.0 (Vis Stu 2005) the CBF can't "find" the functions. I have to type
A.ZZ. And if I then insert
Namespace A
in the top of the CBF, it suddenly can't "find" any of its controls. All my
Me.TextBox1 get a squigly line.
/jim
In .Net 1.1 (Vis Stu 2003), I could make a Class module, a .vb file, with a
bunch of global functions.
In my aspx-pages I could then call those functions.
The "old" 1.1 project had name A, and the vb-file started with
Namespace A
Public module Module 1
Public Function ZZ
and in the CBF file the code started with
Namespace A
BUT
In 2.0 (Vis Stu 2005) the CBF can't "find" the functions. I have to type
A.ZZ. And if I then insert
Namespace A
in the top of the CBF, it suddenly can't "find" any of its controls. All my
Me.TextBox1 get a squigly line.
/jim