System.Windows.Shell namespace
-
Not a programming question. I've been sniffing around the Shell namespace new in .NET 4.0, which is part of PresentationFramework assembly. Well. A so-called "shell" is a part of OS which evolve quite quickly. What if a new feature is added, which will happen sooner or later? Will it be shipped with .NET 5.0 or in a java-like update or in another System.Core2 thing... Adding wrappers for OS-specific shell features to the framework ain't a good idea -- just my 2 penses. Any thoughts about this?
Greetings - Jacek
-
Not a programming question. I've been sniffing around the Shell namespace new in .NET 4.0, which is part of PresentationFramework assembly. Well. A so-called "shell" is a part of OS which evolve quite quickly. What if a new feature is added, which will happen sooner or later? Will it be shipped with .NET 5.0 or in a java-like update or in another System.Core2 thing... Adding wrappers for OS-specific shell features to the framework ain't a good idea -- just my 2 penses. Any thoughts about this?
Greetings - Jacek
Well, it is in the "System.Windows" namespace. I definitely think the annoying OS-specific stuff should be wrapped and be made available in the .Net Framework. That provides a layer to help avoid changes when the underlying OS changes. So in Windows 8 we can use the same .Net functions. If the functions no longer exist on that OS, they can perhaps throw an exception and having a bool that says IsFeatureAvailable would be nice too.
-
Not a programming question. I've been sniffing around the Shell namespace new in .NET 4.0, which is part of PresentationFramework assembly. Well. A so-called "shell" is a part of OS which evolve quite quickly. What if a new feature is added, which will happen sooner or later? Will it be shipped with .NET 5.0 or in a java-like update or in another System.Core2 thing... Adding wrappers for OS-specific shell features to the framework ain't a good idea -- just my 2 penses. Any thoughts about this?
Greetings - Jacek
Yeah, OSes are pretty much a shell game.
-
Yeah, OSes are pretty much a shell game.
-
Not a programming question. I've been sniffing around the Shell namespace new in .NET 4.0, which is part of PresentationFramework assembly. Well. A so-called "shell" is a part of OS which evolve quite quickly. What if a new feature is added, which will happen sooner or later? Will it be shipped with .NET 5.0 or in a java-like update or in another System.Core2 thing... Adding wrappers for OS-specific shell features to the framework ain't a good idea -- just my 2 penses. Any thoughts about this?
Greetings - Jacek
-
How else do you legitimately access those features?
Join the cool kids - Come fold with us[^]
Trollslayer wrote:
How else do you legitimately access those features?
Hmm, you are right. Anyway it must be placed somewhere or we are back to interop. The best place for that would be a 2nd party .NET library -- not in the framework itself. The same with GDI/WPF. Who uses both GDI and WPF? If GDI was in a separate lib from the beginning there wouldn't such a mess today. A designer would choose a technology for GUI and data storage and wouldn't have to reference all former/future technologies. But this is just my opinion. Ouch. Kombadibilidy.
Greetings - Jacek