Scripting.Dictionary alternative

[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

 

[Michael O'Donovan [MSFT]]

Hi,

1. You have a couple of options here. The one that probably maps the closest
is the HashTable, however the ArrayList, SortedList the ListDictionary,
StringDictionary and the HyrbidDictionary may also be options. Depends on
exactly what you are wanting to do. Search msdn.microsoft.com to see the
differences between them. Also, this article has some good info on choosen
between them
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenetchapt13.asp.
2. You really want to move the code that is inline (in script tags in .aspx)
to code behind classes. " the development experience in Visual Studio .NET
2003 is much richer when using code-behind classes. The ability to compile
the code, see all build errors at once in Visual Studio .NET 2003, and step
through your code using the Visual Studio .NET 2003 debugger can drastically
reduce the effort required to maintain and update an application." this
article explains more
http://msdn.microsoft.com/asp.net/using/migrating/aspmig/aspmigasst/optimizing.aspx.
2.b. Page logic code that is written inside <script runat=server> blocks
within an .aspx file and dynamically compiled the first time the page is
requested on the server.
Page logic code that is written within an external class that is compiled
prior to deployment on a server and linked "behind" the .aspx file at run
time. for more info visit
http://support.microsoft.com/default.aspx?scid=kb;en-us;305141#4

Hope this helps,
Michael