Everyone had a great time in Boise this week with developers from the United Kingdom and all over the United States. WPF is alive and well and being used in corporate development along with Prism!
Contents
C# early version of Ocean.
- Data Binding
- M-V-VM
- Commands in M-V-VM
- Dialogs in M-V-VM
- Data Validation
- M-V-VM Tips & Tricks
- Unit Testing & Moq
- Introduction to Prism
- Unity and Dependency Injection
- Shell and Bootstrapping
- Modules
- Regions
- Events
- Navigation
Download
The download includes PowerPoint decks for most of the sessions and source for all sessions. Also included is an Extras folder with goodies.
Please READ THE READ ME.
You can download the code and decks from my Sky Drive here.
Have a great day,
Just a grain of sand on the worlds beaches.
Code Project VB.NET Article Award Dec 2008
Thank you so much for coming and doing this in Boise, Karl!
Indeed! Thank you, Karl, for a great 3 days.
Who ever missed this event should be kicking themselves right now. Relevant content, great people, and many years of experience crammed into 3 days. Awesome!
Karl.
Thank you very much.
Great stuff.
As I see there is some missing code in the CookMe solution.
For example for configuration regions and IResolver.
Taras,
Yes, the CookMe solution is incomplete. This is a project some of worked on in the breakout room, but couldn’t finiish because some had to leave early.
Cheers,
Karl
Hi Karl
With your guidance to choose and use WPF couple of years back… successfully enjoying dev. in this field. Also following Josh Smith and your site regularly for effective development. Thanks Karl.
Currently moving towards Prism with Unity. Was wondering is there anyway to persist data across session in application?
Basically we need to persist login user – irrespective of modules registered and views are displays across several regions. Should Controller/Servier/RegionContext be used?
Thanks in Advance
ursri
ursri,
Not sure of the question.
Persisting data or state across sessions is straightforward in .NET applications with several options for where and how to save this data.
Are you trying to persist the entire state of the application, down to forms visible, records opened, etc?
Karl
Karl,
Thanks for response. The application is desktop based with MVVM-Prism framework.
I need to maintain variables/property like login user across the application session. Something similar to application/session variables in web app.
How best such kind of variables to be made accessible to module/region/view/viewmodel through out application and where to define?
Should property be in Controller/Service as part of RegionContext?
Thanks & Regards
ursri
ursri,
There are many ways to expose global informaiton across your application. It all depends on your requirements and consumers of the information. If only view models consume this information, I would inject a service in the constructor. If the information is used in XAML files, I would expose a class using an application resource.
I would not use RegionContext for this unless you have a very good reason since this is not strongly typed.
Karl
Thank you Karl.
The global might be used by both XAML and view model. For. eg:, viewmodel uses current login user for session tracking while status bar displays login user details.
How would this scenario be best tackled? as Service injection or to expose a class using an application resource?
Please suggest.
Thanks & Regards
ursri
ursri,
I would inject the object into he view models. For status bar information, I would use EventAggregator to publish status bar messages and have the Shell listen for the event and render the inforamtion like I did in the above download.
Karl
Thank you Karl. I shall follow the guidelines.
Regards
ursri
Your welcome.
Best,
Karl
[...] from: Boise Prism, Unity, WPF, MVVM Code and Decks :archives, asp-net-mvc, binding, demonstrations, m-v-vm, object-loading, prism, silverlight, [...]