WPF ToolKit.Extended MessageBox in VS2008.

Aug 10, 2010 at 1:55 PM


     I am using .NetFramework 3.5 and I want to use messagebox from Toolkit.exteded in my project but its for 4.0 framework. Can anyone please tell me are you people going to provide some binaries or installer for .Net 3.5 to use these extended controls.


Aug 17, 2010 at 4:16 PM

Are you talking about the Extended WPF Toolkit project located at http://wpftoolkit.codeplex.com/?

Aug 17, 2010 at 4:20 PM

Hi Brian,

               Thanks for your reply. Yes I am looking for same. Actually I want to have customized message box in my application but I am working on .Net 3.5 framework. How can I use this messagebox in my application, as I have found the source code is developed in framework 4.0. please suggest some solution.


Aug 17, 2010 at 4:26 PM

There is a release scheduled for September.  I will create binaries targeting the 3.5 framework.  If you can't wait that long I suggest that you download Visual Studio 2010 and the Extended WPF Toolkit source, and change the target framework to .net framework 3.5 in the project' properties diloag.

Aug 17, 2010 at 4:34 PM
Brian thanks for quick reply, well i shall be very gratefull to you if you could provide me with the binaries as I have very tight sechedule of work to download VS2010. Thanks.
Aug 17, 2010 at 4:46 PM

Now that I think about it, I am unable to provide 3.5 binaries, due to the fact that there are many dependencies on 4.0 features, such as the VisualStateManager, and named parameters.  To target the 3.5 framework I would have to have a reference to the WPF Toolkit in order to use the VisualStateManager, which is something I am not willing to do.  I do not want the Extended WPF Toolkit to have any dependencies on third party DLLs.  If you need the toolkit kit for 3.5 you will have to download VS2010 and add a reference to the WPF Toolkit and modify all styles that use the VisualStateManager, to use the VisualStateManager from the toolkit instead.  You will also have to modify a method in the ColorPicker control to not use named parameters.  I would be willing to help you resolve any issues you run into.

Aug 17, 2010 at 4:52 PM
Yes! I was looking into the source code and found this Visualstatemanager introduced in .Net 4.0 framework and was thinking how ill it be resolved in 3.5 without putting extra efforts to resolve the dependencies. Any ways thanks for your help cheers.
Sep 5, 2010 at 4:34 AM

Due to popular demand, I have just released a version for Visual Studio 2008 and .NET 3.5. It does have a dependency on the WPFToolkit and won't work without it.