Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am in the need of looking for a .net shopping cart, I am a .net developer not PHP and I need that the shopping cart solution be extendible.
In the past I have used Magento, and its probably the best solution out there, but I dont want just to learn another programming language.
Is there any as good as magento but done in .NET??
Some requirements I need:
MultiStore in one single database.
Ability to create themes.
Complex shopping cart discount rules as in Magento
As far as I know, there are only two written in .NET, and one of them is geared towards MVC.
ASP.NET MVC
http://merchanttribe.com/
http://www.nopcommerce.com - Version 3.0 and above is now MVC
ASP.NET
http://www.nopcommerce.com/ - Version 2.9 and below is web forms
dashcommerce http://dashcommerce.org/ is also a good option
has evolved from the old Commerce Starter Kit
Another one is OpenNetCommerce from which dashCommerce derived and went commercial. nopCommerce haven't tested lately, but it used to have issues with the speed.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm a fellow winform/wpf dev. Everything seems to move into the web atm.
Well I've got php and html5/css3 experience, but asp.net seems not that straight forward.
With the upcoming asp.net vNext I'm confused which technology to choose. To get into it,
I've decided to do a simple ass-hat youtube online converter.
On the one side people claim to choose always the best and latest ones, but on the other side
they are not.
Does it even matter? Is vNext that different from what we got today?
I'm sorry to ask such a "simple" question, but in the past no one told me to choose wpf.. you can imagine what happened :)
I'm a huge fan of telerik. Is telerik the to go suite for asp.net?
ASP.NET vNext is still in preview. For someone new to ASP.NET I would recommend looking at Get Started with ASP.NET. For a "standard" website I would recommend ASP.NET MVC, and for a SPA-like application using e.g. AngularJS I would recommend ASP.NET Web API.
I would recommend going with a stable version choose the latest ASP.NET MVC 5 , you can always find simple and informative tutorials on ASP.NET MVC, and yes , telerik is one among the best 3rd part controls, which you can easily integrate with asp.net mvc.
If you are going for more pure web development, you can choose asp.net web api to host service as http and consume them using jquery ajax and several other clients
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am a C# .NET developer, and the tools I use to build a web application are:
SQL Server
Entity Framework
.NET Web API
ASP.NET MVC
HTML/CSS/jQuery
I have been reading up on AngularJS, NodeJS, MongoDB, and ExpressJS, and it certainly seems like with these "Javascript-ish" technologies, you can build a full blown web application.
My question is where does this leave me with my knowledge of the .NET stack? I want to start embracing these newer technologies, and build my next website with them, however, I am confused as to whether I should completely do away with the .NET stack, or if I should complement these newer technologies with the power of the .NET stack where it might make sense. Here are some of my thoughts:
MongoDB could replace SQL Server and Entity Framework
AngularJS can pretty much replace ASP.NET MVC (since both are MVC patterns, having both would be redundant, I think)
But when it comes to building an API layer, would NodeJS completely replace ASP.NET Web API? or could I use them together? What would make the most sense (generally speaking)? Considering that NoSQL databases like MongoDB have javascript-like syntaxes, do we even need server side APIs? Couldn't the client (theoretically) directly talk to the DB?
And where does ExpressJS fit in?
I am hoping someone can help to clarify how these technologies fit in with each other. Pretty sure that a lot of .NET developers looking to explore these newer technologies have the same questions.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'd like to start working on a web-based ASP.net application to assist me with some DBA-type tasks.
I am looking for resources, books, tutorials that might show me how to get started in writing a GUI front end for a web-based application using ASP.Net and C#?
I'll need to use whichever option (MVC or Web Forms) that supports:
dynamic charts, graphs, dash boards and metrics to present data graphically
dynamic menus and options driven by database to prevent rebuilding every time a new option is added
What are ASP.NET & C# best practices for web-based application?
I think the best place to start is the ASP.NET website.
I found the NerdDinner tutorial pretty helpful to learn ASP.NET MVC, if you're looking for a walkthrough.
http://nerddinnerbook.s3.amazonaws.com/Intro.htm
Plural Sight has been an excellent resource for me.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I'm about to embark on a new Document Management System/Knowledge-base system using ASP.Net and I'm wondering what are the best practices and design issues I need to consider before starting up. I am a learning software engineer and I would like to develop my software engineering skills with this project.
Assuming you want to do this as a personal project to learn ASP.Net, I'd suggest using an N-Tier architecture or ASP.Net MVC.
Assuming this is a work project, I'd say: Why re-invent the wheel? Investigate SharePoint or a CMS system to see if they already do what you need.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I`m learning programming languages. And I decide that I need to lear a new web framework. I have 2 candidates: Django or ASP.NET MVC 2.
Can you say me the difference between them and what is so interesting?
Try both, then decide.
Well, I'm using both and found both to be state of the art, easy to learn, fast and easy to install.
Maybe don't look at it from a technical standpoint but from the context. ASP.NET needs a Windows Server, ASP.NET and an IIS installed. You have the license for that? Django on the other hand is open source runs on cheap but fast linux machines and provides you with the Python Language and it's vast easy to install moduls.
If you don't know Python or C# maybe Django is the better way to go. Djangos Documentation is great and has a great tutorial, which is yet to be found on the ASP.NET MVC side.
Well, the conclusion is: Try both :) And if you're gonna use ASP.NET MVC, watch the Nerddinner Sessions (PDC) by Scott Hanselman and Phil Haack.
I would create a small app to try each for a day or two and then choose.
I can't speak for Django, but here are some Asp.Net MVC benefits
Tight integration with other Microsoft technologies
Uses jquery out of the box
Choice of several server-side languages
Very flexible (choice of unit test framework, view engine, model architecture etc)
and a potential negative
Might take extra work getting it running on anything other than Windows
What reasons lead you to choose those
two frameworks?
What reasons lead you to choose those
two languages?
If you don't like the answers, then keep looking. Otherwise...
Do you want to be on a
non-Microsoft web stack? Go Django.
Do you want to interface with lots of other
Microsoft web stack technologies? Go
MVC.
Do you want complied language speed? Go C#.
Do you want interpreted language portability? Go Python.