XP Look and feel in VSC#.NET

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

How can I get the Win XP look and feel in Visual Studio C# .NET? I have
tried the MSDN example with the manifest file, but it doesn't seem
to help.
 
Hi,

I'm not very sure but I think that you have to use 2005 for this, 2003 does
not support visual styles.
 
Joachim said:
How can I get the Win XP look and feel in Visual Studio C# .NET? I have
tried the MSDN example with the manifest file, but it doesn't seem
to help.
Click to expand...

This should work, what OS are you running this on and how does your manifest
looks like?

Willy.
 
the .EnableVisualStyles() works for MOST controls you'll use, but not
for things like tab pages (which, real XP styled ones are a gradient).

I have found that Skybound VisualStyles (free to use) is a great
solution. Just drag and drop it into your form, and all the controls
become XP styled. So you can just use all your regular controls and not
have to redevelop your forms.

link:
http://www.skybound.ca/developer/visualstyles/default.aspx


Rahul said:
You have to use third party controls
Like you can use

Component One
Magic Library
Click to expand...


--
<font face="trebuchet ms">
Mark Ribau
Lead Windows Developer | <a href="www.redbugtech.com/blogs/mark.php">My
Tech Blog</a>
<a href="http://www.redbugtech.com">Redbug Technologies, Inc.</a> -
www.redbugtech.com
</font>
 
I'm running Win XP Pro SP2. This is my myApp.exe.manifest file:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="X86"
name="Microsoft.Winweb.<SpotOnClient>"
type="win32"
/>
<description>.NET control deployment tool</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>


Have I done something wrong?

Regards,
Joachim
 
This is just a wild guess, as I have no real knowledge of manifest files...
but this line caught my eye. The angle brackets are often used in examples
as something meant to be replaced, but not used in the final version. Have
you tried without the < and > ?

-mdb
 
I had this issue also at one time and I fixed it by creating a post build
event that would copy this file to the output directory. That way you don't
have to remember it if you ever clear out that directory or do a release
build.

Eric Renken
 
Joachim said:
Yes! Now it works. I just forgot to copy the manifest file to the Debug
folder. Thanks!
Click to expand...

The manifest must be in the folder of the exe, but much better is to embed
the manifest as a resource in your executable.

Willy.
 
Just by embedding it will it use that manifest or do you need to do
something special. You have caught my interest on how to do this.

Eric Renken
 
Back
Top