These are my disappointment factors:
- Source code uses Hungarian notation.
- In store front website source code they persists almost every value in the session in the session.
- They don’t use strong typed entities. I only noticed 3 or 4 object to used to get data
- Heavy used of data sets instead of objects
- Not a flexible architecture. Business rules and data access is all in the App_Code folder. If you have more than one interface that needs to access the shopping cart to process order or retrieve order orders you can’t accomplish it without serious re-factoring and extracting the source code to reusable components.
I am sure I can find other reasons but I will stop here. This was the reason I decided not to use it in my application. Towards the end of the project I was so happy that I did not use this out of the shelf solution that encouraged me to write this article.
I am not writing this post to drive off their business, but to express my believe and make them be aware of what a user is thinking about their product. By the way the version that I used was 2.5+.
You can find more reviews here at
http://www.411asp.net/func/review?id=6449910&rid=&proc=anony
we used it and it causes tons of errors. We'll likely have to rewrite two of our stores.
ReplyDeleteYou were smarter than i...
Yes we made a right choice. The project is now done. There were many times when I sit down and said "Thank God I didn't use Aivea eShop".
ReplyDeleteWe run eShop generating over 2K orders per day. We moved to eShop from XCart.
ReplyDeleteHi Perez and Fregas,
ReplyDeleteI work in eShop Support and we have been able to resolve 100% of the issues till now.
None of the customers who has contacted us are dissatisfied. THe way we code is quite rational and effective to us, but we have made many improvements in line with the current trends.
Please do not hesistate to contact us and we would be able to assist you best.
With regards,
Pradeep Bhaskar
Paris Hilton thinks www.chatandshop.com is hot
ReplyDelete