Hey guys IM Looking at Implementing MVVM in Silverlight. Kind of new to Silverlight and I'm Definately new to MVVM Pattern.
I get it all But I want A set of small Prism VB.Net MVVM exmaples if that makes sense.
Anyone have anything
You can use prism if you like. I prefer MEF and MVVM Light. The two together are like prism, but less overhead.
The microsoft examples are a great place to start.
http://www.microsoft.com/en-us/download/details.aspx?id=16800
Related
I am looking for some advice on how to quickly create UI for Silverlight pages. I come from WinForms/WebForms background and as a developer, i could quickly place some controls and get going with coding. I find that it takes much longer to do this is Silverlight.
Looking for some ideas.
Properly learn XAML, sorry. This book is pretty good, it will tell you everything from XAML to WCF RIA Services to access your data. Hope this helps.
I have used MVVMLight before in a few projects. Has anyone who has used Prism before know of any significant benefits over MVVMLight. Or do they pretty much have the same features?
Prism is made primarily for extensibility with some components that can be used to implement MVVM designs. Personally I think that Prism is too heavy for simple SL applications.
Check out this earlier post on the subject: MVVM Light + Unity or Prism?
We are using Prism and is an excellent framework for composition and modularity. However, I haven't seen a good story around Blendability with Prism composition. When you have a code that has Regions, how do you generally support blendability with it?
I saw an interesting blog post which takes an approach of creating design time bootstrapper, module catalog, container to support this.
What is your experience with this? Is PnP team coming up with a better story around it? (ie maybe embed design time bootstrapper, designer time region managers inside Prism)?
I am trying to get this working for a modular Silverlight application using Ninject. I can try to follow above link and make it work, but I wanted to see if someone has better ideas around it?
The series you provided in your link is very thorough (especially if you're using MEF (parts 3 and 4)). I'd stick with that to get the blendability you're looking for.
These 2 links are useful for ur purpose:
http://blogs.southworks.net/gmaliandi/
http://msdn.microsoft.com/en-us/library/ff921098%28PandP.40%29.aspx
What are the improvements in vb.net compared to vb6 that make developing such an application easier?
I can think of a few:
ADO.NET is better than ADO for data access (and more options such as the Entity Framework, data repository blocks, LINqtoSQL)
better ability to structure your code for ease of maintenance because of better support for object oriented programming
better testability
overall a much better IDE
better handling of XML
richer set of interface choices: silverlight, WPF, WinForms, WebForms, ASP.NET MVC,
Web Client Software Factory
ASP.NET allows you to divide your interface code from your business logic much better by moving the logic into the code-behind file: better separation of concerns leades to easier and cheaper maintenance costs
WinForms has a much richer set of controls allowing you to build apps that are much easier for your users
better integration wilth other Microsoft products such as Sharepoint
This is by no means an exhaustive list. But it's at least a good starting point.
I switched to VB.Net because of LINQ. Everything else was a nice bonus. ^^
The ability to use the farking scroll wheel on my mouse in the IDE!
Sorry, had to vent on that one since I've recently been stuck in VB6 for maintenance on a legacy app.
Can you point me to good non-Windows looking GUIs choices for VB.NET? I'm needing free but with licenses that allow closed proprietary code. Thank you.
From your previous question:
I'll definitely want an attractive looking GUI. And nothing "Windows" looking.
Generally speaking, this is bad. Windows apps should look like windows apps. Otherwise hell will break loose:
alt text http://forum.computerbild.de/attachments/pc-hardware/realtek-hd-audio-manager-front-panel-problem-1470d1205060406-r.jpg
alt text http://www.techfuels.com/attachments/applications/1262d1207391664-gigabyte-easytune-5-pro-gigabyte-easytune-5-pro.jpg
Consider WPF to get a rich UI framework, though.
Well, for what it's worth, I'd advise against using custom-looking controls for the most part, since you're only confusing users (and thinking of several GUIs that use such a thing I can't really say they look more appealing and are easier or better to use).
If you can use .NET 3 or 3.5 you can use the Windows Presentation Foundation (WPF). By default it looks Windows-like but can very easily be styled to your needs (which is what WPF internally uses anyway for trying to look like Windows).
It has a very steep learning curve, however. But once you understood the basic concepts it's a very nice framework to work with and pretty easy to integrate custom looks for controls.