• 0

Windows 7 Taskbar Progress Bar with C# and .NET


Question

Hey guys,

I've created a control that allows you to easily add the Windows 7 taskbar progress bars to .NET programs. It's all in my blog post "Windows 7 Taskbar Progress Bar with C# and .NET".

Here's the progress bar being used with wyBuild creating update patches for Nero:

post-44539-1248752693.png

Here's the progress bar being used with wyUpdate installing an update:

post-44539-1248752792.png

Also, the progress bar is completely backwards compatible:

post-44539-1248752818_thumb.png

I didn't want this post to sound too spammy, but I figured there are lots of .NET programmers on this board that might like this and there are no adverts on my blog. Also the component is completely open source (C#) with example projects in both C# and VB.NET.

Here's my article: Windows 7 Taskbar Progress Bar with C# and .NET

Tell me what you guys think.

22 answers to this question

Recommended Posts

  • 0
  todd said:
It looks great. Thanks for this! What controls are you using in this screenshot? Are they all private or publicly available?

Most of the controls are privately developed by my company, but some will be released in the near future. The only controls in the screenshot that are open source are VistaMenu and the Windows 7 Progress Bar.

I plan on releasing the tab bar on my blog in the coming months.

  • 0

If someone could do such for Firefox's Download Manager and DownThemAll! I would appreciate it greatly. The green would be normal downloading, marquee being scanning for viruses, yellow for pause, and red for failure. DTA would be the same except the marquee would be used for when it merges the pieces. Catch my drift?

  • 0
  Shunik Jan said:
If someone could do such for Firefox's Download Manager and DownThemAll! I would appreciate it greatly. The green would be normal downloading, marquee being scanning for viruses, yellow for pause, and red for failure. DTA would be the same except the marquee would be used for when it merges the pieces. Catch my drift?

Quite honestly, this will likely be done in C++ not C#. Also, the Mozilla devs aren't prowling the neowin programming forum. You'd be better off submitting a feature request directly to Mozilla.

At the very least you could mention it over at the Firefox forum: http://forums.mozillazine.org/viewforum.php?f=23

  • 0
  Vorenus said:
Quite honestly, this will likely be done in C++ not C#. Also, the Mozilla devs aren't prowling the neowin programming forum. You'd be better off submitting a feature request directly to Mozilla.

Should be submitted to Bugzilla, but I suspect that there is already an item there because I know this is one of the things on the to-do list.

In Mozilla, this has to be done in C++ and interfaced through XPCOM; should be a fairly simple and mostly trivial thing to do, actually. Once there is an interface for this in XPCOM, both the Firefox UI (as well as any extension) would be able to make use of it.

  • 0
  code.kliu.org said:
Should be submitted to Bugzilla, but I suspect that there is already an item there because I know this is one of the things on the to-do list.

In Mozilla, this has to be done in C++ and interfaced through XPCOM; should be a fairly simple and mostly trivial thing to do, actually. Once there is an interface for this in XPCOM, both the Firefox UI (as well as any extension) would be able to make use of it.

I think i heard Mozilla intending to remove XPCOM in the near future

  • 0

I agree - this is a very nice feature.

Hmm what about a blue color along with the red, green, and yellow? Then it'd fit so nicely with the Windows flag logo.

  • 0
  skynetXrules said:
I think i heard Mozilla intending to remove XPCOM in the near future

No. That was never in the plans, and wouldn't be possible because XPCOM (through XPConnect) is how JavaScript (which drives the UI) is able to access the low-level C++ Gecko internals. There has to be some sort of interface, and XPCOM actually makes quite a lot of sense here. What is being done is "deCOMtamination", which is the process by which some internal-use classes that don't need to be (and never should have been) exposed as an API are being converted from COM into regular C++ classes.

  MtDewCodeRedFreak said:
Hmm what about a blue color along with the red, green, and yellow? Then it'd fit so nicely with the Windows flag logo.

You can't specify the color. You can only specify a state, and Windows picks the color for you. It's not "here is a yellow bar that you can use if you want to indicate pause". It's "you can indicate to the system that the bar is paused, and Windows will set the color and animation appropriately, which, in this case, is yellow" (and it's not just a color change; that shiny strobe thingie will stop animating as well if you pause).

  • 0
  code.kliu.org said:
No. That was never in the plans, and wouldn't be possible because XPCOM (through XPConnect) is how JavaScript (which drives the UI) is able to access the low-level C++ Gecko internals. There has to be some sort of interface, and XPCOM actually makes quite a lot of sense here. What is being done is "deCOMtamination", which is the process by which some internal-use classes that don't need to be (and never should have been) exposed as an API are being converted from COM into regular C++ classes.

he read it here http://en.wikipedia.org/wiki/Firefox_3.6#Version_4.0

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Hello, My thoughts on this are mixed. Microsoft has hosted malicious code in the Microsoft Update Catalog where third party device drivers are stored; I wrote about one such incident about fifteen years ago, so if there are any other old malicious drivers floating around in the catalog, this will be a good step towards preventing any infestations from reoccurring. Another thing, which surprisingly is not mentioned in Microsoft's announcement, is that this helps protect against BYOVD (Bring Your Own Vulnerable Driver) attacks, where malware either comes with or downloads an older device drivers with vulnerabilities in it that can be exploited to gain access to kernel memory. Removing all those old device drivers from the Windows Update Catalog, potentially with all sorts of undisclosed vulnerabilities in them, means an attacker can no longer leisurely count on being able to download them from Microsoft's servers--something that may go unnoticed or ignored by security analysts. This makes the adversary attack a little more noisy, since they have to either include the device driver with the rest of their initial payload or download it from a third-party site at some point prior to beginning their BYOVD attack. On the other hand, it means that people who are looking for a specific version of an older device driver for whatever legitimate reasons, like compatibility, performance or stability, may end up going to dodgy third-party sites in search of older drivers, which increases the risk of exposure to everything from nuisance advertisements and unwanted software to actual malicious code. As for me, I have keeping copies of all the device drivers, firmware updates, etc. I have downloaded over the years, some dating back to DOS and Windows 3.x era, not just for hardware I won, but popular things like unified chipset and video card drivers, just in case I ever needed it. It might seem silly to collect such a thing, but the hardware drivers, firmware updates, and documentation are just about 2 TB in size. From my perspective, it is an inexpensive form of insurance, especially given that disk space is always getting cheaper over time. Regards, Aryeh Goretsky
    • @Raze Bold it boy. (I admit, we all did it from time to time..)
    • Fan Control V227 by Razvan Serea Fan Control is a powerful and versatile portable utility that allows you to monitor, control and customize the fans of your GPU and CPU to keep your machine cool and running smoothly. Fan Control supports a wide range of devices and hardware configurations, giving you complete control over your computer's cooling system. Fan Control backend is mainly based on LibreHardwareMonitor, an open source fork of the original OpenHardwareMonitor. This means that hardware compatiblity is entirely open for anyone to contribute, and doesn't rely on a single developer who may stop caring at some point. Combined with the plugin system, Fan Control is unlocked for many generations of hardware to come. Main features Guided setup process on first launch Save, edit and load multiple profiles Change the theme and color of the application. Multiple temperature sources ( CPU, GPU, motherboard, hard drives... ) Multiple fan curve functions, including a custom graph Mix fan curves or sensor togethers (max, min, average) Low resource usage Advanced tuning with steps, start %, stop %, response time and hysteresis FanControl V227 changelog: Allow decimal with hysteresis values Radeon Pro support through ADLX Fix a bug when cancelling the graph editing dialog Update LibreHardwareMonitorLib Download: FanControl V227 | Installer ~15.0 MB (Open Source) View: Fan Control Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Lol tf you are talking about. People are PAYING by using this app exclusively, just indirectly. Do you have any idea how much facebook charges for api access to WhatsApp which has become more or less a monopoly in e-commerce.
    • My kid tried, so I took her to Microcenter and showed her the differences in price as well as storage and specs. We bought a Windows machine. She loves it, and is off to college this fall with her gaming level windows laptop at the price of a Mac that came with a 512GB SSD, and half the RAM.
  • Recent Achievements

    • Contributor
      GravityDead went up a rank
      Contributor
    • Week One Done
      BlakeBringer earned a badge
      Week One Done
    • Week One Done
      Helen Shafer earned a badge
      Week One Done
    • First Post
      emptyother earned a badge
      First Post
    • Week One Done
      Crunchy6 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      660
    2. 2
      ATLien_0
      266
    3. 3
      Michael Scrip
      235
    4. 4
      Steven P.
      164
    5. 5
      +FloatingFatMan
      149
  • Tell a friend

    Love Neowin? Tell a friend!