I want to refer to evengaggregator in my project and cannot find microsoft.practices.composite library easily. I could not find that in reference and tried few installation but no luck yet. I am using .net 4.0. Could you please help me to get start on how do I get microsoft.practices libraries on my machine? I am new to WPF and trying to join the dots here.
Thx,
Nikunj
Open below link and download prism library.
http://compositewpf.codeplex.com
after downloading go to Lib folder of downloaded prism and add reference of DLL to your project as required.
Related
I am working with Spire.PdfViewer for a WPF Application.
After downloading the package, the Spire.PdfViewer.Wpf.dll should be found in the bin folder of my project. Unfortunately I'm not able to find the library on my network.
The documentation is found under this link:
http://www.e-iceblue.com/Tutorials/Spire.PDFViewer/Demos/Quick-guide/WPF-How-to-add-Controls-to-Toolbox.html
Thank you
According to the description for Spire.PDFViewer NuGet package on the official site, it mentioned that “With Spire.PDFViewer, developers can create any WinForms application to open, view and print PDF document in C# and Visual Basic on .NET”. It is a free version for .NET.
For the version for WPF, you need to buy download the Spire.PDFViewer Pack from below link, which contains Spire.PDFViewer for WPF components.
http://www.e-iceblue.com/Introduce/word-viewer-wpf-introduce.html#.V8Uzrih94z4
After installing, please choose the Spire.PdfViewer.Wpf.dll from C:\Program Files (x86)\e-iceblue\Spire.PdfViewer\Bin\WPF4.0. Then you can add PDFViewer controls into Toolbox.
Adding MVVM Light reference to a WPF projects adds a large number of system assemblies to the list of dependencies in the accompanying MSI Setup project. These assemblies (50+ in number) are then copied to the application folder when the app is installed. Why is it so? Why can't it reference it from GAC directly?
Note: Copy Local option is set to True for MVVMLight.dll. I obviously can't set it to False.
Reproducing it is extremely simple. I'm using VS2015 Community.
Create a new WPF Application project.
Add NuGet reference to MVVM Light (or the Lib-only version; doesn't matter).
Add an MSI Setup project to the solution (must have the extension installed).
Add Primary Project Output of WPF application to the setup project.
There you go. A long list of System.X.Y will be added to the list. If you build and install the setup project, you'll see all these DLLs in Program Files folder.
Why? And how to fix it?
Update
The problem does not appear if WPF application targets .NET Framework 4.0 and you add NuGet reference AFTER that. But if you target .NET 4.5, 4.5.1 or 4.6, the long list of dependencies appears again. Think MVVM Light (or NuGet) is having trouble finding the correct package sub-folder.
I don't know why it happens but I can offer a workaround. Just open the project's Detected Dependencies folder, select all of the System dlls, right-click and select Exclude.
Overly agressive dependency scanning is one of the many reasons I don't use Visual Studio Deployment Projects. Instead I use WiX / IsWiX. Both open source and the later written by myself.
For more information see:
http://www.github.com/iswix-llc/iswix-tutorials
I recently discovered memory leaks in our Silverlight application and I have managed to find the source - Context Menu. From what I have searched this is a known issue and there are patches available to fix this. I downloaded the Silverlight ToolKit Source Code and made changes to the class I was having issues with and copied the new DLL to the Silverlight5.0 folder in program files but now I am get XAML Parse Exception errors. I understand this is due to one library being from a different source.
But how do i fix it? I have tried changing references but that didn't help. I tried going back by re-installing Silverlight 5 toolkit but I still get the error.
I haven't found a proper article yet on how to edit and use Silverlight toolkit source code.
why dont you just add 'Silverlight ToolKit Source Code' as another project in your solution and link it to your main project by reference ? parse exception can occur by you messing something up or the toolkit may be a bit buggy too but with attached toolkit as a project you can edit and try easily, quickly and you will not be influencing other apps using silverlight
I had the same problem. I think you didn't copy all used *.dll from the new built toolkit solution into your working project.
I mean, you have to check all references of your working project, all references depending on the toolkit solution have to be renewed to your newly built toolkit project.
The problem is that there are some *.dll's which are linked to each other, when you replace only one of them, the compiler can't ind the other one.
Build entire toolkit solution
Delete old references in your working project
Place all used *.dll's from the toolkit solution into your project
Add new references
Build
I am authoring a management pack with custom views using Silverlight / WPF (shared code) and MP authoring console and MP authoring tool in Visual Studio.
I am following this tutorial on custom views.
Widget for SCOM operation and web console - custom
In Section 4.1: It mentions: Add a reference to Microsoft.EnterpriseManagement.CompositionEngine and Microsoft.EnterpriseManagement.Presentation.Core assemblies. These can typically be found in the Console folder of the Operations Manager installation. Attention: the assemblies from the RTM/CU1 installation will not work! You need to download the sample project files and use the included assemblies.
I cannot add references to the Silverlight project. I get an error message:
Is there any way to get around this?
I understand that the .net runtime is different than that of Silverlight. Yet, this tutorial shows a working example, so it there a missing step or a different binary. What am I missing?
In Section 4.1: It mentions: Add a reference to Microsoft.EnterpriseManagement.CompositionEngine and Microsoft.EnterpriseManagement.Presentation.Core assemblies. These can typically be found in the Console folder of the Operations Manager installation. Attention: the assemblies from the RTM/CU1 installation will not work! You need to download the sample project files and use the included assemblies.
The important bit is the bit in bold, you need to download the sample project and copy the references from there. Were you doing this?
http://gallery.technet.microsoft.com/Creating-a-Widget-for-104711ac
If you download this zip and go to the following sub directory
\Creating a Widget for Operations Manager Dashboard - Walkthrough %231.zip\Creating a Widget for Operations Manager Dashboard - Walkthrough #1\Section_4\AlertSummarySilverlight\Bin\Debug
You'll see the two assemblies in this folder. Copying them out of the zip into another folder and add a reference to them. This works for me in Silverlight 5.
Is there SDK available to download for wpf, as I wanto read that SDK when I don't have internet. Any idea about it, from where can I download SDK for WPF.
WPF is part of Visual studio, you don't need an SDK.
If you want to learn WPF, trying buying a book (an online book as well)
if you want to use it and get help, I think installing MSDN locally will do it.
I think you are talking about the API!? This should be included in the MSDN Library which you can download from here. However, the library is several GB...