Henry He has been doing software development for more than a decade. He hold a Computer Science Master degree from NJIT. As a technology practitioner, he is always excited by all the new technologies. He believe learning is a lifelong process. He spent a lot of his spare time reading books, taking classes, attending seminars, and participating Hackathons. After years of learning, He realized the best way of learning is using and sharing. He think hard to see how to use new technologies at work. He conducted a lot of presentations to share his thoughts with colleagues. He gave many public presentations at user groups and code camps to exchange knowledge and ideas with smart people in the industry. He contributed articles at tech website to let people learn from his experiences and mistakes. Right now, he is working at Medidata as a Lead Application Engineer.
Docker is a tool that can package an application and its dependencies in a virtual container to run on any server. This helps enable flexibility and portability on where the application can run. ASP.NET Core is an open source, cross platform, performant, and scalable web application framework. The modularity and lightweight nature of .NET Core makes it perfect for containers. Today, I am going to give a brief introduction of Docker and show everybody how to run an ASP.NET Core 2.0 Application in Docker containers.
In my presentation, I am going to briefly talk about: what is react, why do we need react, and how a react application looks like.
Are you tired of manual installs and updates? Have you run into problems caused by incompatible libraries? Do you need to notify your colleagues for every single new release of your library? If the answer is YES, then consider about package managers. A package manager is a collection of software tools that automates the process of installing, upgrading, configuring, and removing computer programs for a computer’s operating system in a consistent manner. A package manager deals with packages, distributions of software and data in archive files. Packages contain metadata, such as the software’s name, description of its purpose, version number, vendor, checksum, and a list of dependencies necessary for the software to run properly. Upon installation, metadata is stored in a local package database. Package managers typically maintain a database of software dependencies and version information to prevent software mismatches and missing prerequisites. This session will give you a brief overview of some common used package managers.
.NET Framework was released 14 years ago to create a universal programming layer that gives developers the choice to use any programming language. The Framework was designed with a cross-platform concept in mind, but Microsoft only implemented it for its own platforms. Mono, the open source and cross-platform implementation of .NET Framework, was created by Novell (originally by Ximian), but it is not very popular. Two years ago, Microsoft decided to further open source .NET and make it officially available on different platforms. This was the start of .NET Core. The .NET Core 1.0 was released in June. Let’s take a look at .NET Core 1.0 and ASP.NET Core 1.0 to see the features. What I am going to present here is solely based on my own study, research, and experiments on .NET Core 1.0 and ASP.NET Core 1.0.
Have you experienced application hang, crash, or memory leak in production environment? Other than bang your head against the wall or yell at Microsoft technical support people over the phone, what else you can do? Yes, you can try WinDbg. WinDbg is a multipurpose debugger for Windows. It’s a part of Microsoft Debugging Tool for Windows. It can be used to debug user mode application, driver, and the operating system in kernel mode. This session will give you a brief overview of WinDbg and present you how to use WinDbg troubleshoot application problems in production environment.