Hi,

on a C# page, this directive would make the members of namespace Foo available:

<%@ Import Namespace="Foo" %> 

To achieve the same on an IronPython page, I need to write:

from Foo import *

So the namespace directive is superfluent there. Is this by design or something that will get fixed? I like declaring often-used namespaces with directives...

Best regards,
xanadu

Hi xanadu,

There is a list of default namespaces already imported by Visual Studio in ASP.NET. You only need to import others when they are required.

mobRDF:

Hi xanadu,

There is a list of default namespaces already imported by Visual Studio in ASP.NET. You only need to import others when they are required.

Hi mobRDF,

you're right, but my point was that if I need to import a namespace not in the default namespace, then I can use the Import directive in both C# and VB.NET, but not in IronPython. The Page, Import and other directives are designed to be language-neutral, but the IronPython implementation ignores the Import. I wondered if that would be fixed or not in a future release, or if it is by design.

Best regards,
xanadu