Activity for naasking
-
naasking posted a comment on discussion Help
Sorry, I just realized I never got back to you on this. I switched away from parsing into the System.Net.Mail.MailMessage data types back in 2018, so the code you're depending on is very out of date and I don't anticipate digging into that again to fix issues. I can only advise upgrading to the newer Sasa releases that depend on MailKit, or even better, to use MailKit directly.
-
I'm currently on vacation and probably won't get to this for another week or so. The Sasa mail parsing api is largely obsolete though, since there are better libraries available. Sasa internally uses MimeKit and MailKit, so I recommend using those directly if you can.
-
Sasa v1.0.0-RC2 Released
-
Thanks Andrew, your change has been merged. I didn't have to add those dependencies to Build\packages.config though. It also revealed a bug maybe indicative of a change in the System.Uri parsing behaviour. I'll push out a new RC soon.
-
Update target frameworks
-
Thanks Andrew! Sorry for the delayed reply, but I didn't receive any kind of notification of your merge request, I just happened to notice it when I visited the home page. I'll have to look into that. Managing the builds has always been the least interesting part which is why I just target .NET standard, but this looks pretty straightforward so I'll definitely look at it sometime this week. I agree that the huge dependency graph is irritating.
-
Sasa v1.0.0-RC1 Released
-
You'll be happy to hear that the latest Sasa release targets .NET standard 1.3, so it should be compatible with most .NET core runtimes.
-
Sasa v1.0.0-RC1 Released
-
You are corect, there was an off by one error. I've pushed a new version to nuget.
-
Just did a fresh checkout, first build failed as expected, second build succeeded....
-
Sorry about that, I pushed the missing file. The other issue seemed to have been...
-
Sorry about that, I pushed the missing file. The other issue seemed to have been...
-
fixed incorrect call to GetDirectories
-
use path probing to find peverify and sqlmetal ...
-
even simpler, just have the framework search fo...
-
minor version increment for new probing behaviour
-
documented a possible micro-optimization
-
added citation in case link breaks again
-
mark non-cls compliant method
-
remove unused level parameter
-
updated sasa version number
-
fixed formatting
-
removed references to .NET 3.5 from sasametal
-
reuse the existing uri parsing code, not the le...
-
added missing config files for the benchmark pr...
-
updated nuspec files to only reference .NET 4.0
-
updated link to union-find paper
-
added missing async struct
-
a typed async wrapper struct for IAsynResult
-
fixed comment errors
-
updated to VS 2015
-
updated version numbers for new release
-
Nuget has Sasa v0.17.1, so please try that as well. Perhaps the runtime you have...
-
-Either types switched to structs with a tag field
-
-project file saved with changed name
-
-added a fast hash array mapped Set<T> type der...
-
-compatibility fix for .NET 3.5
-
-use Func.Create for key equality in Trie, even...
-
-Func.Create now it works in a wider variety of...
-
The proper version should be 0.17.1. I just created a new project, installed Sasa.Net...
-
The proper version should be 0.17.1. I just created a new project, installed Sasa.Net...
-
-fixed sasametal to use new tools lookup path
-
-updated file version numbers
-
-added missing test file
-
Added tag v0.17.1 for changeset 5a6afb5bcfd7
-
Sasa 0.17.1 should be available on nuget within the next half hour.
-
-added better SDK path hack for .NET 3.5
-
-made trie key equality test more efficient whe...
-
-update test to use non-deprecated interface
-
-fixed case where header is quoted but surround...
-
-made ilrewrite more platform agnostic with a b...
-
-upgraded Mono.Cecil dependency
-
-added support for nullable enums
-
-handle FK associations differently from entity...
-
SasaMetal 0.17.0 Updated
-
-updated build number for sasametal fixes
-
Added tag v0.17.0 for changeset f92934672a08
-
-fixed invalid iteration on type-table mapping
-
-updated release version numbers to 0.17.0
-
-added experimental FNV hashing, not yet availa...
-
-minor fix to sasametal to properly handle colu...
-
-updated changelog with missing feature
-
-updated changelog for new release
-
-uploaded 0.17.0 release
-
Sasa 0.17.0 Released
-
-sasametal now supports rewriting columns and F...
-
-fixed sequential enum test
-
-updated nuget build number
-
-sasametal can now output a set of interfaces g...
-
-simplified the unfold flag checking
-
-added a new test for struct dispatch
-
-simplified the flags checking code
-
-typecase must handle enums as a special case
-
-fixed arg index
-
-use a buffer size that's slightly less than a ...
-
-added a simple set of extensions to obtain DB ...
-
-don't attempt to reflect upon null values
-
-ensure that only runtime fields are reference,...
-
-documented the dispatch implementation
-
I'm currently uploading RC6 which adds a flags enum called MailParseOptions which...
-
-fixed documentation
-
-added an extra set of overloads that take a ne...
-
-added missing files
-
I'll see what I can do, but this seems unusually fragile. For one, you can't round-trip...
-
Not at the moment. Is there a meaningful difference between a message with an empty...
-
That is the way Sasa intentionally works right now. Only plain text bodies are parsed...
-
-updated project file
-
-renamed to make it less generic
-
-fixed documentation
-
-updated nuspec copyright and license links to ...
-
-added a new project for useful System.Data ext...
-
-fixed remaining assembly metadata
-
-upgraded RC version
-
-fixed assembly versioning so minor upgrades do...
-
-added a new test case thanks to kostas
-
Yes, -RC2 modifies the subject text so it can be used with MailMessage.
-
I'm wary of modifying input just to conform, but I don't really see a way around...
-
-don't permit newlines in decoded words
-
Are you expecting the MailMessage subject to contain a newline? Because Sasa parses...
1 >
