We are trying to build an application in asp.net 5 which is built on .net core.
What are the in-memory caching options available to us. We tried creating a POC using Redis (open source caching server), but it was unsuccessful as we could not get it to work with .net core.
What are the different options we can consider?
We want the application to be platform independent and hence we have selected asp.net 5.
My question may seem noobish ;) but even we have not invested sufficient time in understanding the new asp.net 5 due to a very strict deadline.
Any suggestion would be welcome.
Which Redis client have you used? StackExchange.Redis has DNXCore 5.0 support
Currently, Im in the evaluation process between MVC CMS , I like the clean way in coding of the UMBRACO 7.0.x , with the many W3C standard which implemented there.
Recently , I found that Drupal has new release 8.0 , which has new architecture supporting MVC.
As I'm totally new to Drupal world , I would appreciate any feedback about Drupal 8.x Release From different views such as :
The learning curve and first setup and configuration..
agility & Customization
extensibility with plugins
performance & scalability
security
Community support
Any extra view points would be also appreciated...
I'm not a guru of Drupal.
But I can say about Umbraco -
The best community - our.umbraco.org
Latest technologies - Angular, MVC.
A lot of free plugins = http://our.umbraco.org/projects
Documentation - http://our.umbraco.org/documentation
24 days course - http://24days.in/umbraco/2013/
Umbraco Cloud - new way of developing web-sites with Umbraco - https://umbraco.com/cloud
Fully customizable.
Free learn Umbraco course - https://github.com/kgiszewski/LearnUmbraco7
I'm not guru of Umbraco. But I can say a lot about Drupal 8.x which I use for the last 8 years now.
First of all here is an overview of the new 8.x capabilities which are really amazing and move Drupal to the new age.
On individual topics now here are some helpful links.
The learning curve. It may be longer than usual but it deserves the
time. See
https://www.acquia.com/blog/conquering-the-drupal-learning-curve/25/06/2015/3285296
First setup and configuration. Easy enough for a developer. Give it a try here: https://simplytest.me/project/drupal/8.2.3.
Agility & Customization: By far the best fieldable and fully customized framework. You can create fields for displays, add user permissions, show results from the db and many more and all these through a UI.
Extensibility with plugins: https://www.drupal.org/8/platform (3rd party libraries), https://www.drupal.org/8/standards, https://www.drupal.org/project/project_module and an issue queue for each contrib module (eg https://www.drupal.org/project/issues/pathauto?status=All).
Performance & scalability: http://buytaert.net/making-drupal-8-fly
Security: https://www.drupal.org/security and https://www.drupal.org/security-team. By far the most secure open source framework.
Community support. https://www.drupal.org/community (By far the most promising and helpful software community on the web.)
Don't forget to check the licenses (not only for core but also for plugins), the OS supported and some additional resources such as:
umbraco vs. Drupal comparison
Comparison of the usage of Drupal vs. Umbraco for websites
I know that most GWT based application now is being implemented using the MVP pattern, however I still want to know which MVC framework is the most mature and can be used for production-grade web application built with GWT.
Searching the web I can't seem to find a MVC framework anything comparable to Mvp4gwt and GwtPlatform in the MVP frameworks, in terms of user base and activities in the code.
If you must shoot yourself in the foot, these are the only two MVC frameworks for GWT that I've heard of:
http://code.google.com/p/gwt-mvc/
http://code.google.com/p/gwittir/
Neither of these have had a release in over two years. Probably due to lack of community interest, and because MVP is better in every conceivable way. Using MVC with GWT is like installing square tires on a Ferrari.
You could use JetPad-Mappers, a minimalistic MVC framework developed at JetBrains and used in several (currently unreleased) products.
https://github.com/JetBrains/jetpad-mapper
Disclaimer, I am involved in development of this framework.
I want to write a web site using ASP.NET MVC 3.0 and Microsoft technologies. I'm studying it now, and enjoying it.
The web site is experimental, and will be used by me and my son in house, but of course I will want to grow it and let other people use it. It will be in Hebrew.
What other technologies do I need to study? One I'm sure of is C# 4.0 (and LINQ). But I'm not sure about ASP.Net 4.0 - Do I also need to study it? How about Html 5? Javascript? Entity framework? Ajax?
Well here's my $0.02 worth of advice. I guess if your are going to expand this site at some point in the future you would have to add Enfity Framework 4 as well in terms of how you do your data access and JQuery since it comes out of the box with your MVC projects. Since you are developing it now you might as well add HTML5 to the list. With respect to ASP.NET 4 you might not need to if you're only doing this for your site. It's a pity that there aren't any mvc3 books our yet but you could either refer to blogs for newer material or if you don't mind use MVC2 books to help you along with u
I've been programming for over 15 years and started with .NET 5 years ago. We built our framework for windows data-oriented apps and it is a quite stable.
At this point, we are considering to make a new platform. But, I am a little bit confused with all these new technologies. We considered CAB and SmartClient technologies but there are also WPF, WinForms and Silverlight options in there.
It sounds like you just need a quick overview of the technologies you have outlined there.
WPF: Windows Presentation Foundation - a new graphical rendering system for building interfaces based on the XAML markup language.
WinForms: Windows Forms Applications - Visual Studio's classical drag-drop GUI.
Silverlight: a Web Application framework - usually used with WPF, very similar features
ASP.NET & MVC: ASP.NET is the web application framework used in conjunction with C# and VB.NET used and MVC stands for Model-View-Controller - a design pattern that has actually been around for ~30 years
Without knowing the true intricacies of your framework, what you need it to do, what limitations you have - I can't say X would be better than Y - especially seeing as WinForms and WPF is used for desktop applications, and Silverlight, ASP is used for web applications - unless you're thinking of linking these in with each other? You haven't given enough information in your question.
However, the best for investing in the following 5 years? The most recent and still in development technologies are WPF, Silverlight and the ASP.NET MVC - but nobody has a crystal ball to say whether these will still be alive, kicking, and technologically advanced in 5 years time.
We built our framework for windows data-oriented apps and it is a quite stable. At this point, we are considering to make a new platform.
For your specs, all choices might be very good :)
I know that, but what you think is the best for investing in the following, let's say, 5+ years?
If you have a choice ( meaning if you are just displaying data without all the fanciful animation, movie and game like stuff), use ASP.NET MVC.
I always advocate web applications over desktop ones, because web apps are hosted in a single place, and so they won't produce upgrade nightmare.
In terms of which one has the brightest future, well, none of us have crystal ball and we don't know what Microsoft will throw at us in a few years time. But you should orient your apps around your business, not around fashion. If you really ask me out of the so many, which one will still remain standing 5 years later, I would say ASP.NET MVC, because ASP.NET is a mature technology, and MVC is a tried-and-true design pattern that has been used by open source and non-MIcrosoft companies. The fact that it is widely accepted makes it less likely to fade out of fashion.
If you want to continue with creating desktop applications, then your two major choices are WinForms or WPF. WPF is the "hot" technology right now, but there are a few things to consider before choosing it.
WPF requires .Net 3.5 (maybe it's 3.0, but whatever). This is significant because many corporate customers are still using .Net 2.0, and may not authorize upgrading to 3.5 for some time (my former company still has some clients that haven't authorized moving from .Net 1.1 to 2.0 yet). Also, the installer for .Net 2.0 is 23 MB while the installer for .Net 3.5 is close to 200 MB, and the 3.5 installer appears to be buggy, failing occasionally with a helpful "SETUP Error" message.
Developing with WPF requires Visual Studio 2008. If you're currently using an older version, you'll have to upgrade.
This isn't completely true, but for the most part what WPF brings to the table is a much snazzier user interface. In my experience, corporate customers who are paying big bucks for custom software do not care in the slightest how the application looks - they only care that it functions well and that it ultimately saves them money.
Finally, if you already have experience developing desktop applications for Windows, then you will feel right at home going the WinForms route. Also, because of the Mono project, a WinForms app can (theoretically) work on other platforms like Mac, Linux and the iPhone, whereas this is not yet possible for WPF (I might be wrong about this, and I will happily correct myself if someone points it out).
I'm actually sort of torn about this advice, because I think WPF is very cool and powerful, and it may take off and become the only viable way of developing for Windows very soon. It is a risk, however.
Thank you all for answers !
We tested all platforms and we have at least one project finished using MVC, WPF, Silverlight, WinForms...
The main problem with WPF and Silverligth is missing of native ReportVIewer controls since we have a lot of reports (RDL) created.
Personally, I think also that MVC is best structured framework.
I really have positive thinking of MONO. But, I would rather decrease the price of the project so the clients can buy WINDOWS but to handle bugs in Mono-Linux option.
We decided to follow the Microsoft way.
I'm thinking of some kind hibrid framework (Webservice - SQL SERVER- ADO .NET Entity Framework) to be on hosted on server and hibrid CAB-SMARTCLIENT to be usen on clients.
I really miss the times where only one tool and technology was available like Levi's 501 :)