I would like to see a new top level forum area called "IDE Options",
with sub areas for different versions of VB.
Currently these sort of questions are scattered to the winds.
I agree with Gruff's suggestion.
I would also see it as a good place to move "IDE Customization:Tips & Tricks" posts,
like this recent one
But besides dealing with IDE customization, it could also contain threads
that explore little talked about (and maybe advanced) functionality in the VS.Net IDE perhaps..?
Although many of these types of threads end up n the General sub-forum,
they relatively quickly move off that sub-forum's current page and "disappear" into the forum's archive
where only just the right search parameters can unearth them again.
Having them all in one place means the moderators and experts can quickly
reference them from inside one forum.
As a "for instance" (and this is only one small part of what might addressed
by threads inside this new forum): MEF
MEF = Managed Extensibility Framework
Haven't heard much about it - well it has talked about.
some Automation-related links:
Automation and Extensibility for Visual Studio
Referencing Automation Assemblies and the DTE2 Object
Building Composable Apps in .NET 4 with the Managed Extensibility Framework
Automation and the Visual Studio .NET Automation Model
The Spectrum of Visual Studio .NET Automation
The Automation Objects Chart
Dynamic Source Code Generation and Compilation
I bookmarked this AtmaWeapon post
DI (Dependency Injection) and IOC (Inversion of Control) are all mentioned:
This is a powerful concept, but it gets even more powerful when taken to the extreme.
In a normal case, you're only injecting interface implementations that are part of your own assembly.
What if, when your application started up, instead of using hard-coded classes for injection
it checked a configuration file that told it where to look for dependencies to inject?
You could conceivably write an application framework that lets the user modify everything,
from the UI to the business logic, without recompiling the application!
MEF works in a similar way; you tell it where to look for dependencies and it applies them for you.
Note: Not all forum members have fastidious compulsion for bookmarking that I have
and important posts like these could potentially be missed by new forum members
not knowing what to search for
(and sometimes too afraid to admit that).
This new forum could conceivably deal with
System.ComponentModel.Design Namespace questions,
like if someone wanted to develop a custom root designer
is the only one I know of that talks about root designers,
but I wish there were more).
Creating new forums is a big thing (and somewhat of a hassle),
so I know a decision won't be made impulsively,
but hopefully it will be given a real consideration.
Also hopefully more people will weight in with their thoughts..
Maybe they can ask themselves:
"Do you really understand the VS.Net IDE completely,
(including understanding all that it can do)"?
Is this a topic you would hope to encourage members to ask more about
(and read through the threads to find out what insights the experts of the forum might have to share)?