I am experiencing an inconsistency with non-default assemblies under
According to the docs
non default assemblies are available to script blocks so long as the
class is fully qualified with the namespace. This works only in the
case of System.IO and not for other assemblies. System.IO, according
to the docs, is not a part of the default assembly.
The following is an example of a script block that does not work:
<msxsl:script language="VB" implements-prefix="vb">
Dim o As System.Web.Page
Dim s As String
o = New System.Web.HttpUtility()
s = System.Web.HttpUtility.HtmlDecode(">")
This code snippet reports that the class can not be found.
I understand that the workaround is to use extension objects. I
prefer this approach. But this condition makes me wonder what a
developer is to do when they do not have access to the transform code
in order to add extension objects and only have the stylesheet to work
I am not concerned about custom assemblies in this particular
situation. Although, I am curious as to how custom assemblies would
work since System.Data and System.Web are in the GAC, should be able
to be referenced, but return errors.
Is accessing non-default assemblies something that is supported in the
current framework or not?