Click here to Skip to main content
Rate this: bad
good
Please Sign up or sign in to vote.
See more: C# ASP.NET Silverlight
Dear all,
I want to start working on an ERP system and I'm in dire need of your suggestions which tool is better up to the task? Should I choose Asp.net or Silverlight?
Can you also give me some reasons why one would be better than the other?

Thanks in advance!
Posted 29-Apr-11 4:05am
Edited 29-Apr-11 4:11am
v2
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 3

Interest question...
 
Well I'll say it depends on your expertise, experience and budget. Any kind of tool/technology takes a good amount of time to become a master in that. having that said the "Hello world" program can be written in minutes or seconds in any programming language by going through basic tutorials but the problem and challanges start when you start developing a real world application.
 
If you are planning for any tool, you have to pay time to understand the + and - of it. Do a feasibility analysis, a simple example would be if you want to use Silverlight google for "problem silverlight" or "features of silverlight" you'll see lot of people commenting or advocating about silverlight. Then put your business requirement in place and check which falls under existing technology problem area and see if a proper solution is available.
 
If i take another example of WPF client you need to install it on every users machine with every new release if you are targeting it with a thin client then you wont get full benefit, but you will get a faster UI. Again if you're keeping services in one server and hitting it with client then probably you will hit them with SOAP and then you may need to put Authentication code for each request, that too, will make outgoing request bulky.
 
ASP.NET - the web forms are certainly heavy but there are alternatives like use ajax or the new MVC comes with Visual Studio 2010. The MVC can provide you TDD it is much more cleaner and on top of it its open source and the source code is provided from Microsoft.
 
So I'll vote for asp.net MVC.
 

 
Thanks,
Hemant
 
Edit:
Take a balanced approach.
- If user are less then you can go with WPF but if the total user are huge then it will be problematic.
- The good thing about client applications is they are fast and they have less restriction in terms of using desktop resources, but the bad thing is different desktop may raise different types of exception based on there system configuration.
- Ask the business what is the most common work they do and then do some R&D on the technology you want to use.
- The webservices are good but they use XML and that is string, that means if there are lots of binary data transfer between client and server than you have to convert binary data to base64 (i.e. string) and that will be costly. but if such operation is rare, then no issue.
- Create small POC's and test the network traffic if performance is critical. you can use Fiddler, its free and there are free addons available.
 
Thanks,
Hemant
  Permalink  
v2
Comments
Member 3666825 at 3-May-11 2:02am
   
Thanks Hemant sharma...
Hemant-Sharma-81 at 4-May-11 2:24am
   
you are welcome sir.
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 1

None of them. I would not really want to do something which involves large forms as web page or even with Silverlight. My advice would be a WPF client which connects to the server with a webservice (possibly a WCF service).
 
Edit:
Moving the presentation to the client side has some more advantages, besides allowing to use a better user interface. You can buffer data in the client's RAM to minimize the amount of requests over the webservice. Also, the webservice itself is more economic with the available bandwith, as it only downloads data and not any markup, images or design.
  Permalink  
v3
Comments
Member 3666825 at 3-May-11 2:03am
   
thanks
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 4

If you need a dashboard with fancy UI, Silverlight is the better choice.
With HMML5 coming in, you might need to consider that as an option too.
 
It does depend on your expertise as well.
  Permalink  
Comments
Member 3666825 at 3-May-11 2:03am
   
thanks
Rate this: bad
good
Please Sign up or sign in to vote.

Solution 2

If it were me, I'd use Silverlight/RIA Services if a web solution is your only option. Silverlight provides a much richer interface than an asp.net site ever would.
 
HOWEVER, if a desktop solution is possible, I'd probably go that way because that's even better in terms of interface.
 
Either way, using web services is the only way to go for the database side, and I would use WCF for that. Not only that, but if you go with Silverlight, you MUST use a web service to interact with the database because direct access is impossible (you can't add the necessary references to your Silverlight project).
  Permalink  
v3
Comments
Member 3666825 at 3-May-11 2:03am
   
Thanks a lot

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
0 OriginalGriff 520
1 Maciej Los 290
2 Richard MacCutchan 265
3 BillWoodruff 265
4 Suraj Sahoo | Coding Passion 155
0 OriginalGriff 8,764
1 Sergey Alexandrovich Kryukov 7,437
2 DamithSL 5,639
3 Maciej Los 5,279
4 Manas Bhardwaj 4,986


Advertise | Privacy | Mobile
Web02 | 2.8.1411028.1 | Last Updated 1 May 2011
Copyright © CodeProject, 1999-2014
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100