Shannara
Newcomer
Well, it looks like microsoft has done it again, refused to listen to it's users 
Reference URL: http://www.pscode.com/vb/scripts/ShowCode.asp?txtCodeId=1151&lngWId=10
The above URL is the FIRST pure VB.NET source code to the VSA scripting engine. So I dinked around with it and throughly went over the documentation.
A little bit of history first:
The Microsoft Scripting Control provides a very easy way to add scripting to an application. For those who require 100s of scripts being loaded at one time, then need to modify a single script, the control is a P.O.S. (grr filters) . In order to update a script already loaded, you must reset the control, which will delete ALL scripts it has loaded, and reload all of the scripts. That, is a major no-no, as microsoft knows.
Anyways, all through out the different microsoft scripting newsgroups, people have complained about this. Then microsoft announced that the .NET framework will come with VSA. Yippe! But guess what? Microsoft made the same mistake, or implimented the same flaw (which could be called a bug), as with the scripting control. They refused to allow you to remove or modify just a single loaded script.
So, for those of you thinking about adding server side scripting with either the microsoft control or the VSA.net, you might want to think otherwise Microsoft does not care about the scripting community
A nice, but harder then hell workaround is to have an array of scripting engines (a HUGE array), and have each engine load roughly 10 - 20 scripts. That way, when you modify a script, you only have to reload 10 - 20 of them. Granted this takes up TONS of memory, and a nice hit on speed, but hey, at least you will have scripting...
Thanks to microsoft
Reference URL: http://www.pscode.com/vb/scripts/ShowCode.asp?txtCodeId=1151&lngWId=10
The above URL is the FIRST pure VB.NET source code to the VSA scripting engine. So I dinked around with it and throughly went over the documentation.
A little bit of history first:
The Microsoft Scripting Control provides a very easy way to add scripting to an application. For those who require 100s of scripts being loaded at one time, then need to modify a single script, the control is a P.O.S. (grr filters) . In order to update a script already loaded, you must reset the control, which will delete ALL scripts it has loaded, and reload all of the scripts. That, is a major no-no, as microsoft knows.
Anyways, all through out the different microsoft scripting newsgroups, people have complained about this. Then microsoft announced that the .NET framework will come with VSA. Yippe! But guess what? Microsoft made the same mistake, or implimented the same flaw (which could be called a bug), as with the scripting control. They refused to allow you to remove or modify just a single loaded script.
So, for those of you thinking about adding server side scripting with either the microsoft control or the VSA.net, you might want to think otherwise
Microsoft does not care about the scripting community A nice, but harder then hell workaround is to have an array of scripting engines (a HUGE array), and have each engine load roughly 10 - 20 scripts. That way, when you modify a script, you only have to reload 10 - 20 of them. Granted this takes up TONS of memory, and a nice hit on speed, but hey, at least you will have scripting...
Thanks to microsoft