Website Change Log

-- Nov. 2nd
Updated the Code From Class page with the Get Rhythm and Reflexes projects from recent lectures.

-- Oct. 19th
Updated the Code From Class page with the Tic Tac Toe project from lecture.
The notes on Time Events was updated to reflect changes in Visual Studios 2017 and 2019's agreement with how cross-thread Timers were treated.

-- Oct. 7th
Updated the Code From Class page with the Mouse Event/Drawing Graphics introductory project.

-- Oct. 6th
Updated the Assignment 3's Comments text file, as it was pointed out that two of the records included an extra, unassociated value, which could cause issues depending on how the strings are parsed and processed.

-- Sept. 30th
Updated the Code From Class page with our Flash Cards application, which doubles as the study guide for the Midterm.

-- Sept. 28th
Updated the Code From Class page with the finalized version of the Dark Themed Calculator application. It occurred to me later that the solution to the decimal point problem could be to simply alter an internal variable with updated values and converting that into the results TextBox, rather than doing it the other way around.

Additionally, the LINQ demo from today's lecture has been made available.

-- Sept. 16th
Updated the Code From Class page with the initial implementation of our Dark Themed Calculator application

-- Sept. 14th
Updated the Code From Class page with today's first Form demo. You can re-create this by cut 'n pasting the two files into a Windows Form (.NET Framework) application on your end.

-- Sept. 7th
Updated the Code From Class page with last lecture's class implementation example.

-- Sept. 2nd
Corrected the attribute names for the User input file described in Assignment 1 from the incorrect "upVotes" and "downVotes" names to the correct "postScore" and "commentScore", respectively.

-- August 31st
Updated the notes on Data Types and Keywords page to remove the example where "string?" and "Nullable<string>" are used. As was pointed out when a student to tried this, C# doesn't allow it, as string variables can, by default, accept null values. Which makes sense, as they are "reference type" variables. So attempting to double-qualify as nullable is actually redundant! This also afforded an opportunity to showcase one of the coolest numbers in math: e.

-- August 27th
Updated the Code From Class page with yesterday's short code examples.

Fall 2021 Change Log

Spring 2020 Change Log

Fall 2019 Change Log

Spring 2019 Change Log

Fall 2018 Change Log

Website Change Log