Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

version updated #86

Merged
merged 1 commit into from
Nov 16, 2024
Merged

version updated #86

merged 1 commit into from
Nov 16, 2024

Conversation

asulwer
Copy link
Owner

@asulwer asulwer commented Nov 15, 2024

  1. RulesEngine.cs - UpdateErrorMessage, wrapped block in using statement
  2. removed unused using statements
  3. updated RulesEngine version to include changes from issue #75
  4. targeting NetStandard2.0 AND 2.1

2.  removed unused using statements

3. updated RulesEngine version
@asulwer asulwer changed the title 1. RulesEngine.cs - UpdateErrorMessage, wrapped block in using statement version updated Nov 15, 2024
@asulwer
Copy link
Owner Author

asulwer commented Nov 15, 2024

fyi: if you upgrade to VS 2022 17.12 it 'removes' Net 8 and installs Net 9. project would not build because of the removal of Net 8

@JasonBoggsAtHMSdotCom
Copy link
Collaborator

Out of curiosity, what prompted you to support netstandard2.0? I was going to propose this due to integration requirements with an older app I'm working with, but looks like you already took care of this.

namespace RulesEngine.Models
{
[ExcludeFromCodeCoverage]
public class ImplicitObject
{

#region Implicit Operators
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we not want region blocks?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the region wraps one block of code. in my opinion, it isn't necessary

@asulwer
Copy link
Owner Author

asulwer commented Nov 16, 2024

Out of curiosity, what prompted you to support netstandard2.0? I was going to propose this due to integration requirements with an older app I'm working with, but looks like you already took care of this.

i saw that you had it enabled in your branch. what can it hurt supporting it?

@RenanCarlosPereira
Copy link
Collaborator

All good thanks

@asulwer asulwer merged commit 3636edb into main Nov 16, 2024
3 checks passed
@JasonBoggsAtHMSdotCom
Copy link
Collaborator

Out of curiosity, what prompted you to support netstandard2.0? I was going to propose this due to integration requirements with an older app I'm working with, but looks like you already took care of this.

i saw that you had it enabled in your branch. what can it hurt supporting it?

Works for me. thanks!

@asulwer asulwer deleted the new-version branch November 18, 2024 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants