My previously working code (dotnet 6.0) that was serialising a complex object, stopped producing Json output at the API controller. The object(s) are defined as:

    public class ReportResultsDTO
    {
        public string ReportTitle { get; set; }
        public List<ReportResultDTO> Results { get; set; } = [];
    }

    public class ReportResultDTO
    {
        public string Title { get; set; }
        public List<Dictionary<string, object>> Data;
    }

Turns out that because System.Net.Text is now used by default (rather than Newtonsoft.Json) it doesn’t handle converting List<Dictionary<string, objectto Json. I tried converting it to a Json string first and outputting that, but the returned string was full of \” characters to escape the string(s).…

Windows event log had this error message:

Application '/LM/W3SVC/7/ROOT' with physical root 'C:\inetpub\wwwroot\scwebgroup.com' hit unexpected managed exception, exception code = '0xe0434352'. Please check the stderr logs for more information.

Go this error message in a dotnet core project. App would run fine in IIS Express and Kestrel but not on IIS proper. After trying many of the suggested solutions on the web, I discovered the issue was being caused by the entry:

<environmentVariable name="APIDISCOVERY_FILEPATH" value="D:\VersaDev.SRS.IdentityServer\VersaDev.SRS.IdentityServer\obj\Debug\net6.0\ApiEndpoints.json" /

in the web.config file. Turns out the failure was down to updating the app to net8.0 which caused a conflict wit this line. Commented out the line and the problem went away.…

I did a ‘database first’ reverse engineering of an existing database to create a model for Entity Framework.

I then tried to use that model to create a migration and subsequent new database on a MariaDB instance running under Windows.

I kept getting an error message “Table ‘__efmigrationshistory’ already exists” whenever I ran “dotnet ef database update”. I suspected the issue was to do with case sensitivity of the table name(s).

Things I tried to resolve the issue:

• Manually rename the table in the database to lower case.
• Change the lower_case_table_names setting to 2 in my.ini (location is set in the windows service settings.

…

Background/Environment

Virtuality

…

By default, Scaffolding a table with an auto-increment field adds:

.ValueGeneratedNever();

To the field in the Model Builder. This will cause an automatic value NOT to be generated. This needs to be removed.

Also, we need to add:

        [DatabaseGenerated(DatabaseGeneratedOption.Identity)]
        public int? TemplateId { get; set; }

To the item – and ensure it is a nullable int. https://docs.microsoft.com/en-us/ef/core/modeling/generated-properties …

Not as easy as you would think, once installed, the service wouldn’t start, then I couldn’t log on (Access Denied) then I couldn’t connect remotely.

• Install and Configure DCOM: https://docs.microsoft.com/en-us/sql/integration-services/service/integration-services-service-ssis-service
• Configure Firewall to allow RPC: http://slavasql.blogspot.com.au/2016/07/ssis-rpc-server-is-unavailable-error.html
• Create SSIS Catalog: https://technet.microsoft.com/en-us/library/gg471509(v=sql.110).aspx
• Run SSIS Package with Powershell: https://docs.microsoft.com/en-us/sql/integration-services/ssis-quickstart-run-powershell

 …

When swapping from the Day view to Week view of a SharePoint calendar, we were getting the following error message: “Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection”.

Tried setting the Information Management Policy Settings to 2 months (was 3) to archive list down to less items (It had about 4800 records, got it down to 4200). [NB: Run Information Management Policy job first, then Expiration Policy]. Problem was not resolved.

We have 2 views of the data, filtered to a different number of items in each.…