G
Guest
Hi,
I am porting an existing ASP applcation to ASP.NET which heavily depends on Mainpulation through Scripting.Dictionary. Can anyone help me out with an alternative to use of Scripting.Dictionary.
Secondly, most of the migration done through VS.NET wizard has placed the existing ASP code in <Script> tags in an aspx place. Does the runtime take <script language="VB" runat="Server"> tag as a .NET code and compile it or leaves it for interpretation at runtime each time the page is accessed.
Last but not the least, the VS.NET debugger acts strange and makes silly jumps where as at times to on comments while going through the script tags.
Thanx ..... for atleast reading this - if not replying
Adnan
I am porting an existing ASP applcation to ASP.NET which heavily depends on Mainpulation through Scripting.Dictionary. Can anyone help me out with an alternative to use of Scripting.Dictionary.
Secondly, most of the migration done through VS.NET wizard has placed the existing ASP code in <Script> tags in an aspx place. Does the runtime take <script language="VB" runat="Server"> tag as a .NET code and compile it or leaves it for interpretation at runtime each time the page is accessed.
Last but not the least, the VS.NET debugger acts strange and makes silly jumps where as at times to on comments while going through the script tags.
Thanx ..... for atleast reading this - if not replying
Adnan