?
=?ISO-8859-1?Q?J=F6rn_von_Holten?=
Hi,
my 3-tier system has a separate bizz-logic and storage service (MVC
paradigm as usual) and the bizz-logic layer shall drive the logic
(workflow) of the ASP site.
My "idea" is (alike Xaml but I am not allowed to use Xaml now) to store
meta info defining the design of the dialogs. These are "rendered" to
ASP.NET 2.0 objects in the visualization layer (code-behind). Obviously
I can move to Xaml quite easily later on
As newby with ASP.NET I gave Whidbey the chance to show me how things
are going to work and I easily managed to create 3-4 sample dialogs
using the visible-invisble "trick". Fine so far.
Now I tried to use "new" (C#) in the code-behind area to create those
items. A pity, that those classes are all sealed but its a great relief
anyway.
The design (I mean how it appears in IE) was still ok now, BUT ... and
here is the question ... although i added the events (for buttons and
such) as my intuition made me believe and although the debugger did not
reveal some (drastic) changes to "my" objects in contrast to those
created by Whidbey at compilation stage before ... the events don't
reach my code-behind .... which is quite unlucky. Some of the buttons
are still Whidbey-created and those still work.
Any suggestions or examples where I can see how this works. Is it a
problem with the beta-1 state of ASP.NET 2.0?
cheers Jörn
my 3-tier system has a separate bizz-logic and storage service (MVC
paradigm as usual) and the bizz-logic layer shall drive the logic
(workflow) of the ASP site.
My "idea" is (alike Xaml but I am not allowed to use Xaml now) to store
meta info defining the design of the dialogs. These are "rendered" to
ASP.NET 2.0 objects in the visualization layer (code-behind). Obviously
I can move to Xaml quite easily later on
As newby with ASP.NET I gave Whidbey the chance to show me how things
are going to work and I easily managed to create 3-4 sample dialogs
using the visible-invisble "trick". Fine so far.
Now I tried to use "new" (C#) in the code-behind area to create those
items. A pity, that those classes are all sealed but its a great relief
anyway.
The design (I mean how it appears in IE) was still ok now, BUT ... and
here is the question ... although i added the events (for buttons and
such) as my intuition made me believe and although the debugger did not
reveal some (drastic) changes to "my" objects in contrast to those
created by Whidbey at compilation stage before ... the events don't
reach my code-behind .... which is quite unlucky. Some of the buttons
are still Whidbey-created and those still work.
Any suggestions or examples where I can see how this works. Is it a
problem with the beta-1 state of ASP.NET 2.0?
cheers Jörn