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.

Sign up for GitHub

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

Jump to bottom

ical.net should be easier to use with normal framework applications #392

Closed
rianjs opened this issue May 24, 2018 · 1 comment
Closed

ical.net should be easier to use with normal framework applications #392

rianjs opened this issue May 24, 2018 · 1 comment

Comments

@rianjs
Copy link
Owner

rianjs commented May 24, 2018 •
edited
Loading

Technically this isn't ical.net's fault -- it's an issue with .NET Standard, but... Consuming v4 in a WPF application is really terrible:

Could not load file or assembly 'System.Reflection.TypeExtensions, Version=4.0.0.0 or one of its dependencies. The located assembly's manifest definition does not match the assembly reference

...even though System.Reflection.TypeExtensions is listed as a dependency in the nuspec file.

Terrible. Maybe this can be better.
rianjs pushed a commit that referenced this issue May 24, 2018
Target net46 #392
354ea55
rianjs pushed a commit that referenced this issue May 24, 2018
Play nicer with normal Framework applications #392
5d2529b
rianjs pushed a commit that referenced this issue May 24, 2018
Play nicer with normal Framework applications #392
7448176
@rianjs
Copy link
Owner Author

rianjs commented May 24, 2018

https://www.nuget.org/packages/Ical.Net/4.1.4

@rianjs rianjs closed this as completed May 24, 2018
@rianjs rianjs mentioned this issue May 24, 2018
Closed
rianjs pushed a commit that referenced this issue May 29, 2018
Target net45, avoid a few superfluous collection materializations. #392
46e5af8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rianjs