I created Amazon Filler Items Searching website in last month. I used multiple technologies such as ASP.NET MVC 5, C#, .NET Framework 4.6, Async Task, Ajax, jQuery, Bootstrap etc. All these technologies are popular in current .NET applications development. Actually, Amazon Filler Searching website is a real project because we load formal commercial Amazon web services. You can use it for your real purchasing on Amazon.
Continue reading “An ASP.NET MVC Website Using AngularJS and Running on Azure Cloud Platform”
Since I met another weekend and got spare time, I did not wait long and finished urgent features on Smart Amazon Fillers website: Supporting multiple countries, and fixing pagination issue.
Continue reading “Smart Amazon Fillers Website Supports Both of Canada and USA Now”
I released a simple ASP.NET MVC website using Amazon service 2 days ago. I might call it MyFiller project version 1. In the 1st version, I actually have not finished all features which I wanted. So in past 2 days, I modified something on it. Now I can call it version 2.
Continue reading “The Amazon Filler Items Searching Website is Upgraded”
Update: I have released the version 2. After you read the content below, please also read the new version information. Thanks!
As a practice, and replying for a friend’s request. I just wrote a simple Amazon Filler Item Finding website in this weekend. I put it on Microsoft Azure platform for the demo now.
It is a single web page website currently, but the background it that I used ASP.NET MVC 5, C#, .NET Framework 4.6, Async Task, Ajax, jQuery, Bootstrap etc. on this simple website. It is a single page but there were multiple technologies on it. I will add more feature on it if I get more spare time.
Continue reading “A Simple ASP.NET MVC Amazon Filler Items Searching Website”
Every 1 or 2 months if I did not touch the projects which were about ASP.NET related technologies, I might forget the names and versions. Let me record something here:
ASP.NET 5 is ASP.NET Core 1.0
.NET 5 = .NET Core 1.0
EF 7 = EF Core 1.0
MVC 6 = .NET Core MVC 1.0
Continue reading “ASP.NET Related Names and Versions: MVC, EF, Core…”
If use database in our Web application and publish to Azure platform free tier plan, the database has very limited size so we’d better use other way.
The following is our summary result after we researching solution:
Continue reading “Azure Free Tier Web App Uses Free Database Solution”
We saved passwords in project config file normally when we developed the project, However, it should be different when you deploy your project since most of time you should avoid your customer to touch some system passwords such as the database connection password, some of your API’s passwords such as Google+ API secret codes;
Continue reading “DO NOT Save Password in Web.Config or App.Config Directly”
As a IT guy, a Software Developer, a Microsoft technologies developer (from C++ to .NET ) with over 24 years development history, I still have to face to some awkward (embarrassed ? ) situations such as job interviews. I left school so many years, but some interviews still needed me to give correct answers for some basic computer and programming acknowledges, such as: What is C# ? What features does OO have ? or I was asked for writing code to give a good performance program to implement a scanning or searching case based on stack or queue ….
Continue reading “Experienced Software Developer Still Faces to Code or Basic Acknowledge Test When Interview”
Due to Scott Hanselman’s blog, Current ASP.NET was changed name to ASP.NET Core 1.0.
The main reason is that ASP.NET 5 is NOT a newer version which is to replace traditional ASP.NET (current version is 4.6), also, it is much more different with traditional ASP.NET;
“5 > 4.6 makes it seem like ASP.NET 5 is bigger, better, and replaces ASP.NET 4.6. Not so.”…….”.NET Core isn’t as complete as the full .NET Framework 4.6.”
ASP.NET 5 is now ASP.NET Core 1.0.
.NET Core 5 is now .NET Core 1.0.
Entity Framework 7 is now Entity Framework Core 1.0 or EF Core 1.0 colloquially.
Please read more info from Scott Hanselman’s blog.
We posted simple DNX concept before, the DNX is .NET Execution Environment. By now I have acknowledged DNX was for cross-platform ASP.NET Web applications, also for cross-platform console applications. But I do not know whether DNX support Windows Form applications or WPF applications because the DNX is still on very early stage, not released formal version yet.
DNX has actually 3 editions:
1: DNX for .NET framework, which only supports Windows system;
2: DNX for .NET core, which can be run on Windows, Linux and OS X systems. The .NET core includes a subset of the .NET Framework.
Due to my personal understanding, comparing .NET core with .NET framework, the difference is just simplified think .NET core is a kind of new “.NET framework” which is supporting Windows, Linux, OS X etc. if a .NET application was working on .NET Framework, it needs to be rebuilt on .NET core.
3: DNX for Mono: Mono supports Window, Linux and OS X, but it was not from Microsoft, it is an open source project which was started very early, so it support .NET very well on different platforms.
Here is a ASP.NET official article about choosing the right .NET for you on the server.