Where can I find System.Windows.Controls.dll for Silverlight 3? I need it to be able to use the TreeView control and the AutoCompleteBox control. Toolkit November 2009 is installed but the dll that I need was not included.
The AutoCompleteBox and the TreeView are part of the SDK not the Toolkit. The dlls that contains them are found typically at the following paths respectively:-
C:\Program Files\Microsoft SDKs\Silverlight\v3.0\Libraries\Client\System.Windows.Controls.Input.dll
C:\Program Files\Microsoft SDKs\Silverlight\v3.0\Libraries\Client\System.Windows.Controls.dll
(Note use "Program Files (x86)" on 64 bit systems)
However you should add them simply by using the "Add Reference" dialog, they have the component names of System.Windows.Controls.Input and System.Windows.Controls.
What is in the Toolkit and what is in the SDK can be a bit confusing. This is typically because things have a habit of migrating from Toolkit to the SDK once it matures. A clever bit of QA that.
Related
Using Visual Studio Installer, I created the .msi file for the WPF project and the class library for the custom action. Everything works fine, but there are many dll assembly files associated with the project in C:\Program Files (x86)\Publisher\Program.
I applied Fody.Costura to WPF project after researching when building the WPF project. Therefore, it is working properly in the release/debug folder of the WPF project. When I tried adding a WPF project with 'project out...' to Visual Studio Installer, regardless of Fody.Costura, dlls appeared. On the client-side, there are still dlls. Can they be hidden under the program files folder?
FYI. WPF project is built on .NET Framework 4.8.
I found a way to hide dll files using the Hidden property. By setting this property to 'True', DLL files become hidden but still exist. If you have other ways, feel free to leave your comment.
I've installed MVVM Light Toolkit through NuGet in VS 2017. The problem is that when I click "Add New Item" on any project, I don't see any MVVM templates that appear in MVVM Light tutorials.
They must look like this (but I don't see them in my project):
http://prntscr.com/n9bs1q
I found similar questions about VS 2012. The answers advise to search for C:\Program Files (x86)\Laurent Bugnion (GalaSoft)\Mvvm Light Toolkit\Vsix
But I have no such folder not in Program Files (x86), neither in Program Files.
Help me please, what should I do for the templates to appear?
MVVM Light NuGet can only add related resources (assemblies/.cs files) into the project. It wont add Templates into Visual Studio. To get templates in Visual Studio, you have to install MVVM Light Visual Studio Extension by following the below steps.
Open Visual Studio and go to Tools->Extensions and Updates.
In the Extensions and Updates window lick Online in the left pane.
In the search bar, type MVVM Light.
In the search results find MVVM Light for VS2017. Click Download and accept license.
Extension will be installed once Visual Studio gets restarted. Then you can get the templates.
UPDATE:
They have stopped support of Item Templates for MVVM Light in Visual Studio 2017. Its been there up to VS 2015. So you can only get Project Templates (File->New Project) in VS 2017 extension. You can see similar queries here.
Installing WPF Controls onto a machine is a messy task.
I tested installation in various systems including VMs. Following are the issues I have seen.
Controls not installed in the VS Toolbox.
Controls are isntalled but, cannot be dragged-n-dropped onto the WPF Window
Duplicate entries in the Toolbox sometimes!
I do not know what is wrong with the ToolboxControlsInstaller package. It messes up the Toolbox all the time, well most of the times.
Any guidelines what is the best practices to install WPF controls?
Our customers are very annoyed with these Toolbox behaviors.
Any help is welcome!
Regars,
-Datte
Our customers were annoyed too.
So I wrote this tutorial article covering toolbox installation once and for all:
Visual Studio Toolbox Control Integration
The most convenient approach seems to be using the Toolbox Controls Installer (TCI) package already pre-installed in VS2010 and newer. This includes just adding a key in registry, i.e.
HKLM\SOFTWARE\Microsoft\VisualStudio\10.0\ToolboxControlsInstaller\SampleControl, Version=3.7.0.0, Culture=neutral, PublicKeyToken=3cc4c7b61201d46c
You can also specify a custom tab name.
If you don't have a custom installer for your components, wrapping the DLLs in a VSI or VSIX package may be convenient. The VSIX is more powerful, support quiet install, custom tab name and uninstallation, but only VS2010 or newer.
Be careful with registry + VS2012. I discussed how the registry should be updated for VS2012, or simply call:
devenv.exe /ResetSkipPkgs
and then
devenv.exe /Setup
To clear things up.
Sometimes one also have to clear the Toolbox cache (TBD files), which seems to be a quite evil thing!
How do you install WPF controls into toolbox? However, these are all common issues with Visual Studio toolbox if you(or someone while installing other components) have done some mistakes in configuring. Refer the below links which has suggestions to avoid these issues.
Installing controls to VS 2010 procedure : How to add my custom WPF control to the ToolBox by using the WPF ToolBox Control template
Icons messed up issue : Visual studio 2005 toolbox icons messed up (though this is not reported with VS 2010, this solution would work for VS 2010 also).
I installed the wpftoolkit.msi and added a reference to it, but it doesn't get dipslayed in the toolbox, is there anything else that needs to be done? I followed the instructions from the code plex site, I can access some of the controls from code, only a few, I added WPFToolkit as a reference, does any other reference need to be added for the chart controls and so that they can be accessed from the toolbox?
EDIT: I added all dlls in the folder and still cannot access the chart control.
Answer: I provided an answer bellow you neeed to include a different namespace for the charts the default one from the codeplex site doesn't include all controls.
I believe this is the answer if you want to add the charting controls to your toolbox.
If you just add a reference to what the codeplex site says you won't get all controls.
using Microsoft.Windows.Controls doesn't work you need to include the reference name, if you click on properties for the reference name you can copy name, for charting it is: System.Windows.Controls.DataVisualization.Toolkit
For the toolbox:
Go to your toolbox, right click create a new tab. In the new tab right click choose items add all the controls from the System.Windows.Controls.DataVisualization.Toolkit namespace. You should have all of them in the toolbox.
Here it is http://wpf.codeplex.com/releases/view/40535
Installation and Usage Instructions
Please note: The WPF Toolkit is dependent on .NET Framework 3.5 SP1. You must install .NET Framework 3.5 SP1 in order to use any features in the Toolkit.
Instructions for using the WPF Toolkit binaries:
Install .NET Framework 3.5 SP1
If you have a previous version of WPF Toolkit installed, uninstall it through the Remove Programs dialog on the Control Panel (look for "WPF Toolkit October 2008" or "WPF Toolkit January 2009" or "WPF Toolkit March 2009" or "WPF Toolkit June 2009")
Download the WPFToolkit_Binaries or WPFToolkit_BinariesAndSource
Run the WPFToolkit.msi to install the WPFToolkit.dll and WPF Toolkit design time binaries to your Program Files folder
Reference the binaries in your project:
Reference WPFToolkit.dll in your project
Add a using statement ("using Microsoft.Windows.Controls;") to the top of .cs files
Add a new xmlns (for example, xmlns:toolkit="http://schemas.microsoft.com/wpf/2008/toolkit") to the top of XAML files
Remember to use the namespace prefix (in the above example, ) in the body of your XAML
If Visual Studio 2010 based on WPF, why I cannot open it with reflector?
In other words, devenv.exe seems to be native assembly, so where is the WPF UI code?
The Visual Studio devenv.exe executable is indeed a native program. However, native programs can load the .NET runtime and thereby host Windows Forms and WPF components. In fact, Visual Studio has always done this. Even before VS2010 adopted WPF for its editor and shell, the various Visual Studio designers were implemented in Windows Forms. If you go into the Common7\IDE and Common7\IDE\PrivateAssemblies directories, you'll find lots of designer DLLs that you can view in Reflector (e.g. Microsoft.VisualStudio.ORDesigner.Dsl.dll is the LINQ to SQL designer).
So the new WPF bits of Visual Studio are just another set of managed assemblies hosted in the native executable. I'm not sure which particular assemblies host the WPF bits -- and to be honest there are probably dozens. But looking at the VS process in the debugger, I'd say Microsoft.VisualStudio.Editor.dll (which lives in the GAC, not in the VS install directory) would be a good place to start.