Do you work from home but your company has an annoying screen lock policy that forces you to log in again if you've been away for a while? Here's an easy VBS script that will run and most companies won't block it from running.

set wsc = CreateObject( Wscript.Shell")

Do 

WScript.Sleep(60*1000)

wsc.SendKeys("{NUMLOCK}")

Loop

Save this as ScrnLock.vbs on your desktop folder. You can even set it to run on startup.

<system.webServer><security><requestFiltering>
<denyUrlSequences>   <add sequence="ggkit.com" /> </denyUrlSequences> 
      </requestFiltering></security>

</system.webServer>
</configuration>

There isn't very good documentation on this issue but usually it means you do not have the proper .NET Core SDK installed. In my case it was the latest for Visual Studio 2019.

Download it from here  https://dotnet.microsoft.com/download/dotnet/thank-you/sdk-3.1.411-windows-x64-installer

Also, often you may find that the CORE hosting bundlle is the issue, even though it may be installed. Simply run the installer and choose to "Repair"

There are a number of very nice logging frameworks like Serilog, Log4net, ELMAH, NLog, and others. Almost without exception, they require fancy configuration setups because they were designed to log stuff in several different ways.  For beginning developers and even for some of us seasoned pros, set up and usage can be daunting. All I want is to be able to write a message, stack trace, and date of occurrence to my database Logs table and that's it. So I came up with KISSEDEL: Keep It Simple Stupid Easy Database Exception Logger. You can plug this into any app that uses a database and be going in five minutes!

First let's create a table in SQL Server:

 USE [DBName]
GO

    SET ANSI_NULLS ON
    GO

    SET QUOTED_IDENTIFIER ON
GO

CREATE TABLE[dbo].[Logs]
    (
   [Id][int] IDENTITY(1,1) NOT NULL,
   [Date] [datetime]     NOT NULL,
  [Message] [varchar] (4000) NOT NULL,
   [Exception] [varchar] (2000) NOT NULL,
CONSTRAINT[PK_Log] PRIMARY KEY CLUSTERED
   [Id] ASC)
WITH(PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON[PRIMARY]
) ON[PRIMARY]
GO

Next configure your connection string in app.Config or web.config:

<connectionStrings>
<add name ="con" connectionString="Data Source=.;Initial Catalog=YOURDATBASE;Trusted_Connection=true"/>
</connectionStrings>

The only other thing we need is a class to handle logging:

using System;
using System.IO;
using System.Configuration;
using System.Data.SqlClient;
using System.Data;
using System.Diagnostics;

public static class Logger

{

    public static void Log(Exception ex)

    {

        string constr = ConfigurationManager.ConnectionStrings["con"].ToString();

        SqlConnection con;

        con = new SqlConnection(constr);

        con.Open();

        SqlCommand com = new SqlCommand("Log", con);

        com.CommandType = CommandType.StoredProcedure;

        com.Parameters.AddWithValue("@Date", DateTime.Now);

        com.Parameters.AddWithValue("@Message", ex.Message.ToString());

        com.Parameters.AddWithValue("@Exception", ex.StackTrace.ToString());

        com.ExecuteNonQuery();

        con.Close();

    }

}

Finally, we want a stored proc to make the inserts:

USE [YOURDB]
GO

SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

CREATE Proc [dbo].[Log]
@Date DateTime,
@Message varchar(500),
@Exception varchar(8000)
AS
insert into logs(Date, Message, Exception)
VALUES (@date,@message, @exception)

That's all there is to it. If you want to log something "Informational", just create a new Exception object and put the information in its Message property.

usage:

 try
                {
                  // your work here

                }

                catch (Exception ex)

                {

                    Logger.Log(ex);

                } 

 Have fun!