Latest Posts
Showing posts with label JSON. Show all posts
Showing posts with label JSON. Show all posts
Tuesday, August 2, 2016
Now that we have most of our static contents taken care of for our application, meaning we did everything we could without a database. It's time to create our database. But before we can do that we need a place to store our connection string to the database. Usually we just store the connection string in the web.config file in our web application. However, since ASP.NET Core is trying to break free from the old way of doing things, there's a new way to store configuration information which is more flexible the old web.config way. As usual it also requires more work.
Thursday, July 14, 2016
As I have mentioned before ASP.NET Core decouples the application from the infrastructure as much as possible. Therefore, you have to tell it exactly what you want in your project. In this blog post we are going to tell ASP.NET that we want to serve static html files in our application.
Here are the steps to serve static files in our ASP.NET Core application.
1. Open the "NorthwindCafe.Web" project, then click on the "Startup.cs" file in the project. You will see the following markup in the Configure method
2. Go into the Configure method, remove the existing code and type in the following code
Here are the steps to serve static files in our ASP.NET Core application.
1. Open the "NorthwindCafe.Web" project, then click on the "Startup.cs" file in the project. You will see the following markup in the Configure method
public void Configure(IApplicationBuilder app) { app.Run(async (context) => { await context.Response.WriteAsync("Hello World!"); }); }
2. Go into the Configure method, remove the existing code and type in the following code
public void Configure(IApplicationBuilder app) { app.UseStaticFiles(); }
Wednesday, July 13, 2016
In this blog post we are going to add the jQuery, AngularJS, and bootstrap libraries to our ASP.NET Core application. Normally we will use NuGet to bring in these libraries but ASP.NET Core gives you the option to use bower to configure the dependencies that you will need on the client-side.
Here are the steps to import the client-side dependencies into our project:
1. First let's make bower.json part of the "NorthwindCafe.Web" project, click on the "Show All Files" icon in solution explorer, then right click on the bower.json file, and then choose "Show in Solution Explorer"
2. Open the bower.json file the markup should look like this
Here are the steps to import the client-side dependencies into our project:
1. First let's make bower.json part of the "NorthwindCafe.Web" project, click on the "Show All Files" icon in solution explorer, then right click on the bower.json file, and then choose "Show in Solution Explorer"
2. Open the bower.json file the markup should look like this
{ "name": "asp.net", "private": true, "dependencies": { } }
Tuesday, July 12, 2016
Technology has moved at a breakneck speed, after working with ASP.NET Core for a while, I realized that my ASP.NET MVC blog articles have become outdated. Don't get me wrong, MVC is still a very big part of ASP.NET Core, but that's the thing it's just a part of it. ASP.NET Core has decoupled the infrastructure from the application. You can deploy your web app on Docker imagine that! No longer is IIS your primary means of hosting your ASP.NET application.
However, with this new freedom comes added complexity. No longer can you just drag and drop components into your design surface. Those days are long gone. This post ist meant to ease your way into ASP.NET Core. I will using the release candidate version two of ASP.NET Core for this post and other subsequent posts. Don't be surprise if I update the version midstream because the product is still pre-release. I will be using Visual Studio 2015 for my development. You can use the command line interface and notepad to develop your ASP.NET Core application. But, I think that borders on insanity.
However, with this new freedom comes added complexity. No longer can you just drag and drop components into your design surface. Those days are long gone. This post ist meant to ease your way into ASP.NET Core. I will using the release candidate version two of ASP.NET Core for this post and other subsequent posts. Don't be surprise if I update the version midstream because the product is still pre-release. I will be using Visual Studio 2015 for my development. You can use the command line interface and notepad to develop your ASP.NET Core application. But, I think that borders on insanity.
Friday, April 3, 2015
JSON is becoming the standard way to exchange data in a relatively short amount of time. The reason is because JSON is easier to work with than XML.
JSON Object:
JSON Object:
- JSON object is made up of name/value pairs
Single Object:
{ "firstName" : "John"}
Subscribe to:
Posts (Atom)
Search This Blog
Tags
Web Development
Linux
Javascript
DATA
CentOS
ASPNET
SQL Server
Cloud Computing
ASP.NET Core
ASP.NET MVC
SQL
Virtualization
AWS
Database
ADO.NET
AngularJS
C#
CSS
EC2
Iaas
System Administrator
Azure
Computer Programming
JQuery
Coding
ASP.NET MVC 5
Entity Framework Core
Web Design
Infrastructure
Networking
Visual Studio
Errors
T-SQL
Ubuntu
Stored Procedures
ACME Bank
Bootstrap
Computer Networking
Entity Framework
Load Balancer
MongoDB
NoSQL
Node.js
Oracle
VirtualBox
Container
Docker
Fedora
Java
Source Control
git
ExpressJS
MySQL
NuGet
Blogger
Blogging
Bower.js
Data Science
JSON
JavaEE
Web Api
DBMS
DevOps
HTML5
MVC
SPA
Storage
github
AJAX
Big Data
Design Pattern
Eclipse IDE
Elastic IP
GIMP
Graphics Design
Heroku
Linux Mint
Postman
R
SSL
Security
Visual Studio Code
ASP.NET MVC 4
CLI
Linux Commands
Powershell
Python
Server
Software Development
Subnets
Telerik
VPC
Windows Server 2016
angular-seed
font-awesome
log4net
servlets
tomcat
AWS CloudWatch
Active Directory
Angular
Blockchain
Collections
Compatibility
Cryptocurrency
DIgital Life
DNS
Downloads
Google Blogger
Google Chrome
Google Fonts
Hadoop
IAM
KnockoutJS
LINQ
Linux Performance
Logging
Mobile-First
Open Source
Prototype
R Programming
Responsive
Route 53
S3
SELinux
Software
Unix
View
Web Forms
WildFly
XML
cshtml
githu