Fix framework moniker in project files #31

Closed
opened 2021-09-25 14:04:05 +00:00 by danieljsummers · 1 comment
danieljsummers commented 2021-09-25 14:04:05 +00:00 (Migrated from github.com)

#27 updated to .NET 6; however, I missed updating the target framework in the project files. The net effect is that it's being built by .NET 6, and run on .NET 6, but targeting .NET 5 behavior and APIs. Change that.

Also, while changing the project files, switch the deployment to publish a single file, rather than all the DLLs together; this will simplify deployment.

#27 updated to .NET 6; however, I missed updating the target framework in the project files. The net effect is that it's being built by .NET 6, and run on .NET 6, but targeting .NET 5 behavior and APIs. Change that. Also, while changing the project files, switch the deployment to publish a single file, rather than all the DLLs together; this will simplify deployment.
danieljsummers commented 2021-09-25 15:33:21 +00:00 (Migrated from github.com)

Fixed in 2.2.1

Fixed in 2.2.1
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: bit-badger/jobs-jobs-jobs#31
No description provided.