Memory leak

There were many discussions about memory leaks in VSA engine, because .NET
Framework doesn't support dynamical unloading of code.
Will this be fixed in the future? What does Microsoft says?

nothing in the near term. VSA is a deadend, but microsoft has not decided
what the replacement will be. VSA was to be the replacement for VBA, but
that dream is over.

the office group has decided to use Visual Studio to build .net components
for office automation. as security concerns will force office to abandon VBA
in the long run, a managed replacement is needed.

-- bruce (sqlwork.com)


"mac" <mactemp (AT) ua (DOT) fm> wrote

There were many discussions about memory leaks in VSA engine, because .NET
Framework doesn't support dynamical unloading of code.
Will this be fixed in the future? What does Microsoft says?

Thanks. Any suggestions what to use if I want a scripting engine for .NET
application?

"bruce barker" <nospam_brubar (AT) safeco (DOT) com> wrote

nothing in the near term. VSA is a deadend, but microsoft has not decided
what the replacement will be. VSA was to be the replacement for VBA, but
that dream is over.

the office group has decided to use Visual Studio to build .net components
for office automation. as security concerns will force office to abandon
VBA
in the long run, a managed replacement is needed.

its depends on your needs. if scripts are not reloaded a lot you can ignore
the memory issue (my approach). you can create an appdomain to load the
scripts in (asp.net approach). unloading the appdomain will free the memory,
but cross domain calls are expensive.

i've been tempted to port an open souce javascript to .net, but haven't
looked recently.


-- bruce (sqlwork.com)




"mac" <mactemp (AT) ua (DOT) fm> wrote

Thanks. Any suggestions what to use if I want a scripting engine for .NET
application?

"bruce barker" <nospam_brubar (AT) safeco (DOT) com> wrote in message
news:#RNQshwTEHA.1284 (AT) TK2MSFTNGP10 (DOT) phx.gbl...
nothing in the near term. VSA is a deadend, but microsoft has not
decided
what the replacement will be. VSA was to be the replacement for VBA, but
that dream is over.

the office group has decided to use Visual Studio to build .net
components
for office automation. as security concerns will force office to abandon
VBA
in the long run, a managed replacement is needed.