I want to skin a vb.net app I made ive googled some stuff and I've seen skinned vb.net apps.
However it seems like any time i try to find someone explaining it its a link to a pay for product.
Does anyone have anything useful on this?
A:
Unfortunatly VB.NET does not provide 'skinning' out of the box. It simply uses the standard windows interface. The only changes to the UI are made when you change the display properties.
I'm not aware of an open source project that provides skinning functionality, however I have used a number of commercial products. By far, one of the best I have used is the Application Styling Framework found in NET Advantage by Infragistics.
Ady
2008-10-27 01:04:18
A:
As the previous answers have stated, vanilla VB is a pain to do this in but there is a free alternative (in VB still). Unfortunately it will involve you learning a lot of stuff and rewriting your app to work with WPF (Windows Presentation Foundation).
Put simply WPF is a replacement for WinForms (which you are probably using now). The main difference being that WPF is vector based and resolution independent whilst WinForms is bitmap based. The output of WPF looks great but it is a lot to learn.
You can easily skin a WPF app and the Microsoft samples show you how to do this too. Using WPF may limit the systems you can install on as it needs .Net 3.0 (best to use 3.0 SP1 or 3.5 SP1 if you can).
A quick Google for WPF and skinning shows a lot of promise.
Ryan
Ryan ONeill
2008-10-28 11:08:14
Skinning an app would be easier in win forms than converting a whole app to wpf.As far as im concerned wpf might be the future of win forms but its horrible. Further more as ivve stated in other threads its possible to do this in win forms.. HOW
2008-10-28 11:31:02
+1
A:
I remember making a "skinnable" vb.net winforms app (a media player) when I was still a student (maybe 6 years ago).
It was ugly, but the way I did it was as follows:
Select a transparency color. Wherever you use this color the app will be transparent (I used Fuchsia (#FF00FF), which I recall being a standard for video games back in the day.
Use a naming convention for child controls (particular buttons, sliders, etc).
Create images for the controls in step 2.
Set 1 pixel wide color coated place holders for those controls. Eg a blue pixel was my play button, a green pixel was my pause button, etc. The placeholder marked the upper left corner of the control.
At runtime dynamically generate the controls (really images with onclick events) and place them on top of the place holders.
I'm sure there is a nicer way to do this, but that was my crude approach.
Giovanni Galbo
2008-10-28 11:34:22