Removed obsolete SmartObjects as data source #31
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
axunonb
added a commit
that referenced
this pull request
Oct 28, 2022
axunonb
added a commit
that referenced
this pull request
Jan 14, 2023
axunonb
added a commit
that referenced
this pull request
Jan 14, 2023
axunonb
added a commit
that referenced
this pull request
Jan 14, 2023
axunonb
added a commit
that referenced
this pull request
Mar 24, 2023
axunonb
added a commit
that referenced
this pull request
Jun 22, 2023
axunonb
added a commit
that referenced
this pull request
Jun 29, 2023
* Update of SmartFormat.NET to v3.2.1 with at least the same extensions enabled as in prior MailMergeLib 5.x versions * Add NET6.0 as a target framework, reducing number of dependencies * Update YAXLib to v4.1.0 * Update AngeSharp to v1.0.4 * Update Microsoft.NET.Test.Sdk to v17.6.3" * Unit test run with net462, netcoreapp3.1 and net6.0 * Disable unit tests console output * After installation is completed, the above "Heads up" message is displayed * Add Sandcastle Help File Builder project folder * Resolves #23 * Enable Nullable Reference Types (NRT) (#30) * Removed obsolete SmartObjects as data source (#31) * Change setup for SMTP Integration tests (#32) * New method to get a free TCP port * SslProtocols: let operating system select the best * Improved Sender integration tests * Fix: SmtpSever trying to use an unpermitted port (#33) * Add method trying to bind an available port * Removed console message for CanBindPort(int port) * Update MailSmartFormatter to load at least the same SmartFormat extensions as before * MailMergeMessage: A new MailSmartFormatter instance is created after properties of SmartFormatterConfig are changed. This is because SmartFormatter does not allow for changes to the settings, after the instance is created * Run unit test for linux under netstandard2.1 * Code refactoring from NET6.0 analytics * Update readme and license files * SmartFormatterConfig change retains existing SmartSettings * Disable warnings for unused private variables in MessageConfig * Add Sandcastle Help File Builder project folder No breaking MailMergeLib API changes from version 5.9.10 However SmartFormat v3 brings breaking changes compared to v2 (e.g. for formatter names, where name "template" changed to "t" and others)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SmartObjectsSourcehas already been replaced byValueTupleSourcein a previous version ofSmartFormat.