November 2005 - Posts

Is your VS2005 project "clean"?

When I tried to upgrade a WinForm project integrating Microsoft OWC from Sept CTP to RTM recently, I faced an error that some assemblies are missing, like the "MSDATASRC 8.0.. blah blah".

I'm pretty sure I clean all CTP products properly and then install the RTM of VS2005. Therefore, I guess there are something wrong in the registration of the OWC component. I uninstall the component and then manually install it. It works. The component is visible in my toolbox and I'm able to drag & drop the control on my WinForm:

Therefore, I listed out my un/re-install/register procedures and informed my colleagues. Ouch... No luck, all of the errors appear in his machine... I have no idea but later, he can compile the project successuflly in VS2005 RTM by clicking 1 button! The magic is... the "Clean" button when right-clicking the project name in Solution Explorer.

I can't search any useful information about the use of this option on MSDN site... What's the actual use of this mysterious Clean option?

Colt Kwong

Posted by Colt | 5 comment(s)
Filed under:

The Binding Handle is Invalid in VS 2005 Resolved

I tried to run one of my WinForm 2.0 solution in my home machine tonight, but a confusing error message displayed when I pressed the F5 button: "Unable to attach debugger. The binding handle is invalid"... What's the binding handle in VS2005? I did a quick search on the product feedback site and luckily, I found the resolution at here.

In short, the solution is to start the Terminal Services in Computer Management panel manually.
(Terminal Services hook up with debugger in VS2005?)

Colt Kwong

Posted by Colt | 32 comment(s)
Filed under:

Errors in using BackgroundWorker Component in WinForm 2.0 Development

I'm doing the multithreading programming for a data access / retrieval process in one of my WinForm 2.0 application this morning, the introduction of a new multithread component - BackgroundWorker - is excellent!

It's much simpler as in WinForm 1.0 dev (no more manual delegation), and this component expose events: DoWork, ProgressChanged and RunWorkerCompleted. What we have to do is to trigger the RunWorkerAsync method, update the ProgressBar control in the ProgressChanged event (most of the cases), and then finish up all works in the RunWorkerCompleted event. Yes, the name of these events explains its usage already, and VS2005 also provides a thread-safe (read more...) dev environment / notification for you throughout the dev process.

However, what I got suck is the WorkerReportsProgress and WorkersSupportCancellation properties... I prepared the module and ready to run, but the result is not what I expect. I tried to debug it and caught this exception:



The WorkerReportsProgress and WorkersSupportCancellation properties need to be config as True if you want to report a progress state or break the asyn call during execution. Well, and the default values are False... :S


Colt Kwong

Posted by Colt | with no comments
Filed under:

A new book and Starter Kit for ASP.NET v2.0

Congrats to a friend of mine - Bipin for the release of his ASP.NET 2.0 book and the ASP.NET jobs site starter kit.

Download Personal Web Site Starter Kit

Colt Kwong

Posted by Colt | with no comments
Filed under:
More Posts