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?
Related
I am currently building guidelines and standards for my team. We build two types of applications:
Business Web Applications using Java + MVC2 (EJB3, Struts and JSP) for transactions, scalability and persistence.
Light Web Applications using Java + Struts and JSP for small applications like surveys, small forms, etc. Basically, it's like MVC2 without the model part of it.
I am looking for the right pattern or practice name for the Light Web Applications. I guess "View-Controller" could do the trick but I am trying to find a diagram that would illustrator that "pattern" properly.
Any idea?
I'm looking for a decent codebase that demonstrates how to use nHibernate as the persistance layer in an asp.net mvc3 project.
The two key pieces of understanding that I am looking to develop are
How to deal with ISession and
ISessionFactory.
How to implement the repository pattern without leaking any details of its nHibernate implemenation.
I'm aware of Sharp Architecture and reading through that now - Its interesting but I'm more keen on finding a straight-forward web app to pick apart than another framework to learn.
Thanks in advance.
I put together a project that offers an example of how to do this using nhibernate and asp.net mvc 2. The repository and nhibernate implementations will be almost the same. Probably the biggest change will be the ioc / dependency injection piece. Take a look. It should provide a solid starting point. Here is the URL.
http://gpsnerd.codeplex.com
Let me know if you have questions.
Bob
Take a look at https://bitbucket.org/FunnelWeb/dev
FunnelWeb is a blog engine based on ASP.NET MVC and NHibernate.
It is opensource and used by many bloggers/develoeprs
We are in the conceptual phase to create a relatively medium size enterprise business product application using Silver light 4.0, Entity Framework and WCF.
1. Is it adivceable to use Silverlight 4.0 for this enterprise business application development or should we go in for MVC.NET / ASP.NET?
2. We have planned to use REST based WCF service. How complex would it be to write the information back to the REST WCF service?
I appreciate and welcome your advice / suggestion. If you need any further details do let me know, i will be happy to share.
Thanks in advance.
If ASP.NET (MVC) and Silverlight are my only choices, I'd take Silverlight.
If you were to choose ASP.NET (alone), remember that MVC isn't your only option. While MVC 2 is the hot ticket on the block, so to speak, WebForms is still being advanced and actively developed and supported by Microsoft.
Also, if you're going to be using Silverlight, you'll be using web pages anyway (at least one) and it's certainly conceivable (possibly desirable) to compartmentalize it such that you can use both.
Having said that, I would honestly recommend WPF over Silverlight for enterprise development unless it's absolutely necessary for it to be cross-platform. It's what it was built for and allows you to completely unleash the capabilities of the OS, not the least of which being that it opens up every security option WCF offers.
As for your question about how easy it is to write information back to a REST WCF service, I suppose the answer to that is relative to how good a developer you are. :) Honestly, it's pretty easy though. Specifically, I'd look into WCF RIA services for that sort of thing.
For Line-of-business apps i will prefer Silverlight. but if you are going for SL4 them i think you should also consider this:
http://christopherdeweese.com/blog2/post/using-silverlight-4-to-browse-netflixs-odata-catalog
Microsoft recently introduced OData as an alternate to WCF. I haven't played much with OData but its easy to work on REST based services but full control over it. I think you should further investigate your options and consider OData as well.
Regards.
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.
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