auto digrammer

auto digrammer. just updated microsoft.service.location, unity reference, updated wpftoolkit reference to the one in the lib folder. ignore system.xaml warning. recompile SUT.Print.engine . then everything will work.

1. The type 'IUnityContainer' is defined in an assembly that is not referenced
2. Microsoft.Practices.Unity 3.5.0.0 or 4.0.1? #229
3. 200% Reflective Class Diagram Creation Tool

ok so just follow these steps to resolve building issues


1. download the code zip
2. Extract it somewhere
3. OPen solutioon in VS2012
4. Open the references for the SUT.PrintEngine project
5. Remove the references to
- Microsoft.Practices.Unity
- Microsoft.Practices.ServiceLocation

6. Re add the references from the folder "Lib" within the downloaded code project file under the "Sut.PrintEngine" project
- Microsoft.Practices.Unity
- Microsoft.Practices.ServiceLocation

7. rebuild
8. happy days
4. Reference to System.Xaml missing from template WPF UserControl
5. "Assembly '...' Was Not Found" When including a reference to a local namespace
6. Troubleshoot broken references
7. Cannot find System.Xaml?
8. Back port .NET 4 to 3.5 SP1 in VS2010

argeting .net framework 3.5, just remove the reference to System.xaml. it shall be fine.

9. Duplicate AssemblyVersion Attribute

the good answer is:
Starting from Visual Studio 2017 another solution to keep using the AssemblyInfo.cs file is to turn off automatic assembly info generation like this:
false

10. VS 2017 does not create AssemblyInfo.cs
11. Shared AssemblyInfo for uniform versioning across the solution
12. How to use Assembly Version and Assembly File Version
13. Understanding the Visual Studio AssemblyInfo Class
14. Defining Common Assembly Properties for Multi-project .NET Core 2.0 Solution in Visual Studio 2017
15. .NET Standard GenerateAssemblyInfo Add Item AssemblyInfo Error
16. Duplicate AssemblyVersion Attribute
17. How to: Enable and Disable Automatic Binding Redirection
18. Allow C# application built with .NET 2.0 to run on .NET 4.0/4.5
19. Migration Guide to the .NET Framework 4.8, 4.7, 4.6, and 4.5
20. Migration of .Net 2.0/3.0/3.5 Application to .Net 4.5
21. How to: Configure an App to Support .NET Framework 4 or later versions
22. Version compatibility in the .NET Framework
23. Backwards Compatibility of .NET Framework 4
24. What is .NET framework backward compatibility?
25. Building Applications for Different .NET Framework Versions
26. Multi-Targeting and Porting a .NET Library to .NET Core 2.0
27. How a Windows 10 Update Might Have Broken Your .NET App
28. Should, When, and How Can I Migrate to .NET Core
29. Upgrading Projects to .NET 4.6
30. How to: Determine which .NET Framework versions are installed
31. .NET Versioning and Multi-Targeting - .NET 4.5 is an in-place upgrade to .NET 4.0
32. The Complete List of Migration Issues Upgrading to .NET 4.0