Quantcast
Channel: patterns & practices: Prism
Viewing all 1878 articles
Browse latest View live

Created Unassigned: Cannot use GetExportedValue in MEF [10699]

$
0
0
I am trying to prototype a PRISM MEF application framework in order to restructure my project for usage
with PRISM but I cannot seem to get this to work with MEF:

[https://edi.codeplex.com/wikipage?title=PRISM%20Unity%20versus%20MEF](https://edi.codeplex.com/wikipage?title=PRISM%20Unity%20versus%20MEF)

My problem is that I want to do something like *RegisterInstance* in *Unity* in **MEF**. Somehow I cannot determine why the ExportedValue<T>() call that I am using does not work for me? Can someone have a look at my prototype and tell me what I am doing wrong here?

Thanks Dirkster

New Post: How to programmatically move the main window in Prism WPF In C#

$
0
0
I do not think this is a prism problem. I would use an attached behavior and viewmodel pair to resolve this problem.
The behavior could bind to an attached property that is based on an event that would indicate when the window is to be re-positioned.

You could also do the same with window class that inherits from Window but does evaluate its DataContext Changed event to
react on a Move Window event that could be triggered by the viewmodel. I am talking about something like this:

https://fsc.codeplex.com/SourceControl/latest#InplaceEditBoxLib/Views/EditBox.xaml.cs

I know this control is not a Window but it implements the pattern that I am referring to. It evaluates the DataContextChanged
event and filters an interface out of the viewmodel if one was attached:

https://fsc.codeplex.com/SourceControl/latest#InplaceEditBoxLib/Interfaces/IEditBox.cs

The interface contains a events that are fired by the viewmodel:
https://fsc.codeplex.com/SourceControl/latest#InplaceEditBoxLib/Events/EditEvent.cs

Hope this helps.

New Post: How to programmatically move the main window in Prism WPF In C#

$
0
0
First, thanks so much for your reply.

Yes, it is not a prism problem. It is so odd that it was WindowState="Maximized" ResizeMode="CanMinimize" in my project XAML file that prevents me from resizing and moving my main window. The main window is just a shell which holds many user controls that in turn bound with a view model.

I never thought about these attributes have such effect on resizing and reposition. I tried to change style with different setters, all my efforts failed. By trial and error,
I delete WindowState="Maximized" ResizeMode="CanMinimize" from my project XAML, then I got what I wanted---moving the main window, centering it.

Could Anyone explain why WindowState="Maximized" ResizeMode="CanMinimize" in my project XAML can prevent me from resizing and moving my main window?

New Post: Attach "Expanded" command while using HierarchicalDataTemplate in TreeView

$
0
0
You did save me some time posting this WPF TreeWiewItem behavior. Thanks.

Just for those who are not into PRISM. You will also need the CommandBehaviorBase class defined, for example, here:
https://github.com/xperiandri/PortablePrism/blob/master/Prism.StoreProfile/Commands/CommandBehaviorBase.cs

...and then you can apply all 3 classes with an XAML like this:
xmlns:behav="clr-namespace:Behaviours"
<TreeView.ItemContainerStyle>
  <Style TargetType="{x:Type TreeViewItem}">
    <Setter Property="behav:Expanded.Command" Value="{Binding DemoExpandCommand}" />
  </Style>
</TreeView.ItemContainerStyle>
...where DemoExpandCommand is an ICommand in the bound viewmodel of the treeview item.
The command is triggered upon expansion of the treeview item node.

Great work - thanks a lot.

New Post: Dynamically Creating regions and Injecting Views

$
0
0
Hi

I am new to Mef+ Prism.We follow MVVM Pattern. I have been looking for a example for creating regions dynamically and injecting views into it but could not able to find a good example for it So starting this thread.

My Scenario: We are using Telerik Rad Controls for this.

I have a MEMBER who has multiple ORDERS associated to him.So When the user selects the member, All the orders that are associated to him should be displayed in each RadPane.
So I have to generate Radpanes dynamically depending upon the number of orders that the Member had. Generating these RadPanes is working but after these Radpanes are generated I have to Inject a View into it.Here comes the haredest part which I felt to achieve.I will Explain clearly.


Lets say MainView is the view that has to be injected into the RadPane every time when the RadPane created dynamically.

In MainView we have two ContentControls with names : dynamicDataRegion, dynamicNavigatorRegion as below

<ContentControl x:Name="dynamicNavigatorContent " Grid.Column="0" Grid.Row="2" />
<ContentControl x:Name="dynamicDataContent" Grid.Column="1" Grid.Row="2" />

So for every RadPane these two regions has to be created dynamically and Inject the view accordingly.

For this I have used the below code
foreach (var order in OrderListDetails)
{
//Naming the dynamicRegions
string dynamicDataRegion = review.OrderId.ToString();
string dynamicNavigatorRegion = (review.OrderId+"A").ToString();
//Instance of RadPane
RadPane radPaneItem = new RadPane();
//Getting the OrderData
//This will have all the deatils
//get the Details related for the OrderId
     CurrentOrder.GetOrder(order.OrderId);
//Creating an Instance of MainView
     var coreView = ContextManager.Current.MEFContainer.GetExportedValue<MainView>();
            ((MainViewModel)coreView.DataContext).GetMember();
            //Creating and Adding and Navigating
Microsoft.Practices.Prism.Regions.RegionManager.SetRegionName(coreView.dynamicDataContent, dynamicDataRegion);
Microsoft.Practices.Prism.Regions.RegionManager.SetRegionManager(coreView.dynamicDataContent,ContextManager.Current.RegionManager);
DataCollectionDesktopContextManager.Current.RegionManager.RequestNavigate(dynamicDataRegion, ViewNames.DataView);

Upto here It is working fine.This DataView is getting injected dyanamically I am happy for that but when I am trying to do the same for that second view too whic is not working for me.Can anyone help me please on this.Below is the code I have used to inject the Secondview which is NavigationView(which is a TreeView)
            //Creating and Adding and Navigating
Microsoft.Practices.Prism.Regions.RegionManager.SetRegionName(coreView.dynamicNavigatorContent , dynamicNavigatorRegion);
Microsoft.Practices.Prism.Regions.RegionManager.SetRegionManager(coreView.dynamicNavigatorContent , ContextManager.Current.RegionManager);
            ContextManager.Current.RegionManager.RequestNavigate(dynamicNavigatorRegion, ViewNames.AbstractionNavigatorView);
            //assing Mainview to RadPane's Content
            radPaneItem.Content = coreView;
            //Panes is a ObeservableCOllection <RadPane>
            Panes.Add(radPaneItem);
        }
When I do this, I am not able to see the Scond view.Only the First view whic i DataView I seeing.Can any one help me on this please.I have been working on this for a long time.

Thanks!!

Created Unassigned: ViewModelLocator is not in the http://www.codeplex.com/prism namespace [10709]

$
0
0
To use the ViewModelLocator the following namespace needs to be defined:
xmlns:aw="clr-namespace:Microsoft.Practices.Prism.Mvvm;assembly=Microsoft.Practices.Prism.Mvvm.Desktop"

The reason for this is that (I think) there is an error in Microsoft.Practices.Prism.Mvvm.Desktop.dll. There is a namespace definition for Microsoft.Practices.Prism.ViewModel to be included in the prism namespace but it should be Microsoft.Practices.Prism.Mvvm.
[assembly: XmlnsDefinition("http://www.codeplex.com/prism", "Microsoft.Practices.Prism.ViewModel")]

Project License Changed

$
0
0
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: 1. You must give any other recipients of the Work or Derivative Works a copy of this License; and 2. You must cause any modified files to carry prominent notices stating that You changed the files; and 3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and 4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

Source code checked in, #ff6316df3dadd0d24083d51aa1dea922d07fb47e


New Post: Platform License Restriction

$
0
0
Prism.Composition, Prism.Mvvm, Prism.PubSubEvents, Prism.Interactivity, Prism.UnityExtensions, and Prism.MefExtensions now use the Apache 2.0 license. For more details see my blog post.

Blaine Wastell
http://blogs.msdn.com/blaine

Updated Wiki: Home

$
0
0

Welcome to the Prism Community

Announcements

  • Prism for WPF now uses the Apache 2.0 license. See associated blog post.
  • Just released Prism Library 5.0 for WPF. For more information go here.
  • Prism 5.0 now supports Unity 3.5 at http://aka.ms/prism-wpf-code.
  • Prism 4.1: can be found here.



Overview

Prism provides guidance designed to help you more easily design and build rich, flexible, and easy-to-maintain Windows Presentation Foundation (WPF) desktop applications, Silverlight Rich Internet Applications (RIAs), and Windows Phone 7 applications. Using design patterns that embody important architectural design principles, such as separation of concerns and loose coupling, Prism helps you to design and build applications using loosely coupled components that can evolve independently but that can be easily and seamlessly integrated into the overall application. These types of applications are known as composite applications.

Prism includes reference implementations, QuickStarts, reusable library code (the Prism Library), and extensive documentation. This version of Prism targets the Microsoft .NET Framework 4.0 and Silverlight 4 and includes new guidance around the Model-View-ViewModel (MVVM) pattern, navigation, and the Managed Extensibility Framework (MEF). Because Prism is built on the .NET Framework 4.0 (which includes WPF) and Silverlight 4, familiarity with these technologies is useful for evaluating and adopting Prism.

Intended Audience

Prism is intended for software developers building WPF or Silverlight applications that typically feature multiple screens, rich user interaction and data visualization, and that embody significant presentation and business logic. These applications typically interact with a number of back-end systems and services and, using a layered architecture, may be physically deployed across multiple tiers. It is expected that the application will evolve significantly over its lifetime in response to new requirements and business opportunities. In short, these applications are "built to last" and "built for change." Applications that do not demand these characteristics may not benefit from using Prism.

It should be noted that while Prism is not difficult to learn, developers must be ready and willing to embrace patterns and practices that may be new to them. Management understanding and commitment is crucial, and the project deadline must accommodate an investment of time up front for learning these patterns and practices.

Getting Started

Additional Links

  • The patterns & practices road-map can be found here.
  • The scope for Prism for Windows Runtime project can be found here.

Previous Releases

  • Prism 2.1 targeting Visual Studio 2008, WPF and Silverlight 3, named Composite Application Guidance on MSDN.
  • To learn about upgrading from previous versions of Prism, go here.

Updated Wiki: Home

$
0
0

Welcome to the Prism Community

Announcements

  • Prism for WPF now uses the Apache 2.0 license. See associated blog post.
  • Prism.Mvvm and Prism.PubSubEvents now support Windows Phone 8.1. See associated blog post.
  • Just released Prism Library 5.0 for WPF. For more information go here.
  • Prism 5.0 now supports Unity 3.5 at http://aka.ms/prism-wpf-code.
  • Prism 4.1: can be found here.



Overview

Prism provides guidance designed to help you more easily design and build rich, flexible, and easy-to-maintain Windows Presentation Foundation (WPF) desktop applications, Silverlight Rich Internet Applications (RIAs), and Windows Phone 7 applications. Using design patterns that embody important architectural design principles, such as separation of concerns and loose coupling, Prism helps you to design and build applications using loosely coupled components that can evolve independently but that can be easily and seamlessly integrated into the overall application. These types of applications are known as composite applications.

Prism includes reference implementations, QuickStarts, reusable library code (the Prism Library), and extensive documentation. This version of Prism targets the Microsoft .NET Framework 4.0 and Silverlight 4 and includes new guidance around the Model-View-ViewModel (MVVM) pattern, navigation, and the Managed Extensibility Framework (MEF). Because Prism is built on the .NET Framework 4.0 (which includes WPF) and Silverlight 4, familiarity with these technologies is useful for evaluating and adopting Prism.

Intended Audience

Prism is intended for software developers building WPF or Silverlight applications that typically feature multiple screens, rich user interaction and data visualization, and that embody significant presentation and business logic. These applications typically interact with a number of back-end systems and services and, using a layered architecture, may be physically deployed across multiple tiers. It is expected that the application will evolve significantly over its lifetime in response to new requirements and business opportunities. In short, these applications are "built to last" and "built for change." Applications that do not demand these characteristics may not benefit from using Prism.

It should be noted that while Prism is not difficult to learn, developers must be ready and willing to embrace patterns and practices that may be new to them. Management understanding and commitment is crucial, and the project deadline must accommodate an investment of time up front for learning these patterns and practices.

Getting Started

Additional Links

  • The patterns & practices road-map can be found here.
  • The scope for Prism for Windows Runtime project can be found here.

Previous Releases

  • Prism 2.1 targeting Visual Studio 2008, WPF and Silverlight 3, named Composite Application Guidance on MSDN.
  • To learn about upgrading from previous versions of Prism, go here.

Updated Wiki: Home

$
0
0

Welcome to the Prism Community

Announcements

  • Prism for WPF now uses the Apache 2.0 license. See associated blog post.
  • Prism.Mvvm and Prism.PubSubEvents now support Windows Phone 8.1 and Universal Apps. See associated blog post.
  • Just released Prism Library 5.0 for WPF. For more information go here.
  • Prism 5.0 now supports Unity 3.5 at http://aka.ms/prism-wpf-code.
  • Prism 4.1: can be found here.



Overview

Prism provides guidance designed to help you more easily design and build rich, flexible, and easy-to-maintain Windows Presentation Foundation (WPF) desktop applications, Silverlight Rich Internet Applications (RIAs), and Windows Phone 7 applications. Using design patterns that embody important architectural design principles, such as separation of concerns and loose coupling, Prism helps you to design and build applications using loosely coupled components that can evolve independently but that can be easily and seamlessly integrated into the overall application. These types of applications are known as composite applications.

Prism includes reference implementations, QuickStarts, reusable library code (the Prism Library), and extensive documentation. This version of Prism targets the Microsoft .NET Framework 4.0 and Silverlight 4 and includes new guidance around the Model-View-ViewModel (MVVM) pattern, navigation, and the Managed Extensibility Framework (MEF). Because Prism is built on the .NET Framework 4.0 (which includes WPF) and Silverlight 4, familiarity with these technologies is useful for evaluating and adopting Prism.

Intended Audience

Prism is intended for software developers building WPF or Silverlight applications that typically feature multiple screens, rich user interaction and data visualization, and that embody significant presentation and business logic. These applications typically interact with a number of back-end systems and services and, using a layered architecture, may be physically deployed across multiple tiers. It is expected that the application will evolve significantly over its lifetime in response to new requirements and business opportunities. In short, these applications are "built to last" and "built for change." Applications that do not demand these characteristics may not benefit from using Prism.

It should be noted that while Prism is not difficult to learn, developers must be ready and willing to embrace patterns and practices that may be new to them. Management understanding and commitment is crucial, and the project deadline must accommodate an investment of time up front for learning these patterns and practices.

Getting Started

Additional Links

  • The patterns & practices road-map can be found here.
  • The scope for Prism for Windows Runtime project can be found here.

Previous Releases

  • Prism 2.1 targeting Visual Studio 2008, WPF and Silverlight 3, named Composite Application Guidance on MSDN.
  • To learn about upgrading from previous versions of Prism, go here.

New Post: Platform License Restriction

New Post: Custom Command Behavior

$
0
0
@frantic0: import the following namespace in your class:
using Microsoft.Practices.Prism.Interactivity;

Created Unassigned: Navigation Problem [10710]

$
0
0
Hi,
i´m a rookie in Prism and i have the following Problem: I had made a shell with one region (MainRegion) with a dockpanel.
I had made 2 Modules, Module A and Module B.
Both Modules have only different labels inside.
Module A had also a button which had to trigger the navigation.
In Both Module.cs file are the registration (in the container) from my views.
I see the View from Module A in my shell, but when i want to navigate to the next module then changes nothing.....

Module A
```
public partial class ModuleA: UserControl
{
private IRegionManager regionmanager;

public ModuleA(IRegionManager regionmanager)
{
InitializeComponent();
this.regionmanager = regionmanager;
}

private void Button_Click(object sender, RoutedEventArgs e)
{
regionmanager.RequestNavigate("MainRegion", new Uri("ModuleB", UriKind.Relative));
}

}
```
Module B
```
public class CustomerModule:IModule
{

private IRegionManager regionmanager;
private IUnityContainer container;
public CustomerModule(IRegionManager regionmanager, IUnityContainer container)
{
this.regionmanager = regionmanager;
this.container = container;
}

public void Initialize()
{
regionmanager.AddToRegion("MainRegion", typeof(ModuleB));
container.RegisterType<object, ModuleB>("ModuleB");
}
}
```

Can anybody help me?

Thx
Brian

New Post: PRISM 5 InteractionRequests: get a new instance of the popup window

$
0
0
I am using InteractionRequests with a PopupWindowAction:
<prism:InteractionRequestTrigger SourceObject="{Binding DialogRequest, Mode=OneWay}">
        <prism:PopupWindowAction CenterOverAssociatedObject="True" IsModal="True">
            <prism:PopupWindowAction.WindowContent>
                <local:AgreementDetailView ></local:AgreementDetailView>
            </prism:PopupWindowAction.WindowContent>
        </prism:PopupWindowAction>
    </prism:InteractionRequestTrigger>
Seems the "AgreementDetailView" would be initiated when the main view loaded, then this instance will be used repeatedly whenever a popup is called.

I am wondering if it's possible to get a new instance of the "AgreementDetailView" when a popup is called, and when closed the instance will be discarded.

Thanks.

New Post: Best approach to start multi window/shell application

$
0
0
Hello

I need to rewrite old WPF application to new WPF PRISM project that will gonna have similar functionality as old, but it will have advantages of composite approach thanks to PRISM. I want to ask for best approach to start doing this.

Old application has a starter window (let's call it launcher ) Which that launcher you can start other new windows (diferent projects for each department with diferent functionalities), each separate project that start from launcher can run simultaneously. And in that projects we have other programs on a ribbon tabs (in prism we could name that tabs as modules).

What would be best approach to start PRISM application? I am thinking of this option:

One separate shells for launcher that start new shells (windows) for each program and in that programs we load modules.

I am not sure if that approach is a correct way.
Also since I am new to PRISM, I am not sure if you can comunicate between shells, i might need to comunicate bettwen shells.
Also I cant find way to start new shell window with new regionManager from delegate command.

If anyone can help me pick right decision. I would be grateful.
Sorry for my poor english.
Hal.

Reviewed: Prism 5.0 for .NET 4.5 (8 31, 2014)

$
0
0
Rated 3 Stars (out of 5) - aaaaaaaaaaaaaaaaaaaaaaaa

New Post: The problem when adding Microsoft.Practices.Prism.dll

$
0
0
Dear Gurus!
I'm trying to create a new PRISM project in WPF. But when I'm adding reference to Mirosoft.Practices.Prism.dll In empty WPF project I get an error:
Cannot resolve dependency to assembly 'System.Windows, Version=5.0.5.0, 
Culture=neutral, PublicKeyToken=7cec85d7bea7798e' because it has not been preloaded. 
When using the ReflectionOnly APIs, dependent assemblies must be pre-loaded or 
loaded on demand through the ReflectionOnlyAssemblyResolve event.'
The same error occurs when I try to use a template PRISM WPF 4.0 shell. I've been using PRISM with Silverlight for a long time without problems. How to fix the problem?

New Post: The problem when adding Microsoft.Practices.Prism.dll

$
0
0
After replacing prism libraries from Silverlight to WPF type - problem solved. Sorry!
Viewing all 1878 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>