My suggestion for VB wishlist

[TJoker .NET [MVP]]

Is there any emil alias for sending suggestions for new VB features ?
Here's one. I wish there was a keyword like AbsoluteNamespace.
The reason is recurring on my projects. I usually set the Root Namespace
project property because it simplifies changing it later. My problem happens
when I have to define a type that will not be anywhere under that root
namespace, then I cannot define it in another namespace without removing the
Root Namespace setting and changing ALL the files in the project to be
contained in the original root namespace.
The Namespace keyword creates a Sub-namespace under the root namespace, I
wis I could create a type in a totally different namespace. something like:

'project Root Namespace: MyProj
Namespace OtherProj
Public Class C1
'MyProj.OtherProj.C1
End Class
End Namespace

'wish!
AbsoluteNamespace MyOtherNamespace 'or Absolute Namespace MyOtherNamespace
Public Class C1
'MyOtherNamespace.C1 -- GREAT!!!
End Class
End AbsoluteNamespace 'or End Namespace

 

[Tom Spink]

Hi TJoker,

Then that throws the root namespace idea out the window... You can't define
anything under the root namespace anyways, even with other languages because
then you no longer have that root namespace.

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

" System.Reflection Master "

==== Converting to 2002 ====
Remove inline declarations

 

[Cowboy \(Gregory A. Beamer\)]

try (e-mail address removed)

This group is also monitored by both MVPs and Microsoft employees that will
pass items along, if they think they have merit. The above address is a more
direct link, per:

http://support.microsoft.com/defaul...port/kb/articles/Q114/4/91.asp&NoWebContent=1

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

**********************************************************************
Think Outside the Box!
**********************************************************************

 

[TJoker .NET [MVP]]

Maybe I didn't make myself clear. I do like the root namespace idea.
Currently if you set the root namespace and use the Namespace block in you
code you are actually defining a namespace under the root, like my
MyProj.OtherProj.C1 example below.
I like defining most of my types without specifying a namespace and knowing
that they'll all be under the root namespace and that I can change the root
namespace and recompile my library before the release anytime some manager
or architect decides that the namespace needs to be renamed because the
product name has changed or some other excuse.
I still want that but I can see a lot of value in being able to define some
minority of the types in my assembly in a totally different namespace. For
example if you look at the system.Data assembly you'll notice that it has
the type System.Xml.XmlDataDocument (as opposed to
System.Data.Xml.XmlDataDocument).
I'd like to do the same without any major hassle like editing all existing
files that do not have a Namespace block (I'll have to do that if I remove
the Root Namespace setting).


--
TJoker, MCSD.NET
MVP: Paint, Notepad, Solitaire

****************************************

 

[Tom Spink]

Hi TJoker,

Good example, and I can understand what you mean, after further thought, it
may be useful...

It does however, IMO, sound a bit messy, having a root namespace, then an
absolute namespace. It sounds like you have 'GoTo' *shudders* statements all
over, and it may reduce the integrity of your source code.

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

" System.Reflection Master "

==== Converting to 2002 ====
Remove inline declarations