There are many solutions/products that PayPal provides for websites to integrate with PayPal payment. I would like to know what's the simplest or easiest solution to integrate PayPal into ASP.NET MVC web applications. Which solution I should use? It would be helpful if someone who had the done this before can share his or her experience. Thanks.
Recently I implemented a PayPal 'Buy Now' button in a ASP.NET MVC Razor view. In the end the button is just a HTML form that is posted to the PayPal website. However, it took me some time to find out which hidden form fields were required, and which optional fields I could also use to further configure the payment process. I have published my experiences on my blog: http://buildingwebapps.blogspot.com/2012/01/single-item-paypal-buttons-and.html. There you will also find the source code for an MVC Html helper method that makes rendering single-item PayPal buttons less work.
Integrating PayPal with MVC is not your issue. Integrating your ecommerce checkout process is the hard part. PayPal has a very nice pre-packaged assembly you just need to reference and your basically done.
My main point is that your technology stack isn't what you should be focusing on here. Instead learn the PayPal API and how it fits into your existing codebase.
Related
In Wordpress, I can enable wp_comments to show the commenting system.
I want to write code so that whenever I write comments in HTML markup, it calls my comments written codes.
How can I achieve this in ASP.NET MVC or ASP.NET web forms?
There are several ways to add comments to your ASP.NET MVC 3 web project.
1. Develop a comments section within your application
If you wish to create bespoke commenting functionality for your site, this article gives you a clear walk-through on how you can achieve this.
2. Integrate third party comment service into your website
Alternatively, you could use a third party service like DISQUS and integrate it into your app. Here's a link outlining how to do this.
There's no 'out of the box' commenting system for ASP.NET. Also, you can't really compare the ASP.NET MVC Framework with Wordpress as they are completely different.
Since you have specific functionality (outputting HTML markup), I'd recommend option #1.
Does anyone have any example code for integrating with WorldPay using MVC3? Specifically posting the XML order to WorldPay. I have googled all the way but couldnt find the relevant information .
WorldPay uses a pretty simple REST API. Their developer documentation, which I think contains C# examples, should be all you need.
MVC doesn't change how you'd interact with them. The code would be the same with a Silverlight or Windows Forms application.
I am tasked with making a custom ecommerce app that will populate purchase options from a table and keep track of orders, call paypal, etc. It will be pretty much like 'select options', 'enter payment info', 'confirm payment', 'setup account (now that payment is done)'. Another team here at the office is using MVC for a new project which this project will eventually be working with. The question is if an eCommerce app makes more sense to use ASP.NET MVC or regular Forms based? (will use SSL if that makes any difference)
I'd go with MVC, personally. Both options are viable, to tell the truth. I just prefer the MVC model, it's lightweight, customizable, I know exactly what's happening (no server controls, yay!), have full control over the markup, integrating 3rd party libraries like jQuery is a breeze (even for Ajax - I used jQuery's Ajax with WebForms, but it was not as pleasant as in MVC). I don't know whether you tried MVC already, if yes - then you know how it works, if not - this might be a good opportunity for you to learn something new and fun.
An important factor in your decision should be support for 3rd party controls. Are there any that you would like to use for your application? Perhaps an out of the box solution such as a shopping cart? Note that MVC is relatively new and does not know the concept of server controls, so most of the existing solutions won't work or will require some hacks (it shiver me timbers when I think about putting WebForms stuff into MVC...). However with the concept of models, controllers and views it's fairly easy to develop your own solution. Have you done layered architecture in WebForms? If yes, then you'll feel at home, only everything will fill more at the right place. :)
Good luck!
Not only should you use ASP.NET MVC, you should have a look at Rob Connery's storefront application weblog series as a guide for some of your decision making. He goes through some of the technical/architectural decisions in an open series.
I'm curious to know if any basic CMS code has been written for ASP.NET MVC.
The reason I ask is, I'm making a data-driven website for a client, and I've already spent a significant amount of time building it from the ground-up in MVC, but now the client wants content management facilities.
Basically they want to be able to add/edit/remove articles and have revision control.
It would be great if I could somehow 'bolt on' the content management without having to start again from scratch, developing it under an existing CMS.
Should I build the article management and revision control myself, or should I re-use some existing package?
N2 does what you describe - "bolts on" to existing ASP.NET solutions (including MVC).
Also, kooboo is interesting http://www.kooboo.com
(I know this question is old, but it still comes high up for the relevant search terms.)
Today I discovered Meek, http://www.adventuretechgroup.com/labs-meek/, and it was very simple and unobtrusive to add to my MVC project, which I believe is what the original poster would have wanted - bolting on CMS as a feature rather than having it take over your entire site.
Piranha CMS is well suited to bolting on to an existing application. The author of it describes why and how here. To quote straight from that source:
"Our focus is content management and to have a transparent and lightweight API for developers. Piranha CMS has almost no components or helpers that render any HTML at all, it simply provides a database, a manager interface and a routing mechanism for retrieving the correct data for the current request.
In the case of you having an existing website you could actually bypass the routing completely, add one page at a time in the manager interface and then manually load the Page model in you existing page. This would allow you to keep your original application exactly the same but manage the content form the manager interface."
If you are still looking, I've published my new open source CMS here:
MVCwCMS
I'm actively working on it so I will push more updates soon.
Here is also a quick summary as to how Telerik Sitefinity does it:
http://www.sitefinity.com/mvc-cms
in brief - allows you to plug in standard system.web.mvc.controller classes as widgets, lets you use the API for anything including model binding, standard Razor for a view engine etc.
There is also Oxite which I believe is more of a blog engine.
Heve a look at AtomicCms it's a free open source content management system based on ASP.NET MVC 1.0
http://atomiccms.codeplex.com
Check for Orchard ;-)
It is based on asp.net mvc.
I need to provide a window on an ASP.NET MVC web page where registered users of the site can group chat live.
Can anyone recommend a component or control that can provide real-time group chat that I can embed on an ASP.NET MVC page?
I am willing to use free or commercial components, as well as a web service.
I looked into a few web 2.0 approaches, like:
Campfire - problem is, it takes you to a separate site, and I can't embed the chat window (at least that's what they said when I contacted support)
Meebo - requires that users have Meebo accounts (I think)
What's unique here is that I need to enable site users to chat live with each other - not with a central support person (like LivePerson, or the Meebo widget).
All you really need is an action to post new messages to, an action to poll for updates, and a div to place the items.
You can accomplish all of this pretty easily with ajax and those two actions on a ChatController in ASP.NET MVC.
+1 for Campfire though, it's a really well polished tool.
There's an unofficial developer API for Campfire called Tinder.
I saw that that 37 Signals was promoting it on their website here, so it's probably pretty good.