How To Install LAMP stack on Ubuntu 17.04

The LAMP stack is the most common web-server configuration – and for good reason! The LAMP stack is one of the easiest to setup and supports popular software such as WordPress without too much configuration. The acronym LAMP stands for Linux, Apache, MySQL and PHP.  Today we will be installing and configuring a LAMP stack on Ubuntu 17.04 (Zesty Zapus) Requirements: An Ubuntu 17.04 Server (Debian will also work, but Ubuntu is recommended) An SSH Client (You can use PuTTY or SmarTTY on windows) Internet access (You have internet, right?) Before we start, it is assumed that you are running the commands using the root account. If you are a normal user you can either prefix each command with sudo or you can run sudo su to upgrade to a superuser account.   Installing LAMP stack on Ubuntu 17.04 To start off, you need to make sure that your system…

C# How to gather IP addresses from IPConfig

IPConfig offers some great information about our network cards. But, its not very friendly to use when you are programming. You could parse the output using a regular expression, but this is kinda sloppy and sensitive to any future upgrades or textual differences between operating systems. Instead, we can use WMI queries to ask the operating system for information about our network cards. I’ve written a program that does just that. “NetConnectionID” from Win32_NetworkAdapter is the same name you will see in IPConfig “Local Area Connection”, for example. You can relate Win32_NetworkAdapter to Win32_NetworkAdapterConfiguration with the “Index”. This is exactly what I’ve done below. From there, you can query anything you want from the Properties list for the Win32_NetworkAdapter or Win32_NetworkAdapterConfiguration see the links for a full list of properties available.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Management;
using System.Configuration;

namespace ConsoleApplication3
{
    class Program
    {
        static 
person Brian Mackeyaccess_time June 11, 2015launch Read More

Sharing DLLs with multiple programs without versioning issues

Modern day internal .NET applications combine services, console applications, unit tests, winforms and asp.net web applications. These applications often share Assemblies (DLLs). With so many exe’s, updating our applications can be quite a challenge. For one thing, Visual Studio is designed to output a program with one top level exe file. Modern day applications consist of many exe’s. Its far too easy for our applications to get out of synch. If only we could store all our assemblies in a single folder, say “C:\References” and have our applications use the assemblies in that folder. Well we can, but it requires more work than you think. Let’s look into a simple example. [The example is intended to display the core issue with assembly versioning, not give lesson in architecture] We have two programs: Program1.exe and Program2.exe. Both programs reference “C:\References\BusinessLayer.dll”. Two Visual Studio Builds produce: C:\OutputDirectory\Bin\Debug\Program1.exe
C:\OutputDirectory\Bin\Debug\BusinesLayer.dll (v1.0)
AND
C:\OutputDirectory2\Bin\Debug\Program2.exe
C:\OutputDirectory2\Bin\Debug\BusinesLayer.dll…
person Brian Mackeyaccess_time February 24, 2010launch Read More