Comments (8)
Oh, that's disappointing and surprising as one of the reasons I went down the dotnet standard route was to simplify dependencies. Doesn't sound like it worked though.
Thanks for the link, I'll take a look.
from succinct.
So according to that link, I need to target both netstandard1.0 and .NET 4.5, and thus create a nuget package with dll's targeting those two. Then .net framework projects use the latter and so do not pull in all the netstandard dependencies!??!? That seems completely broken to me. This only appears to happen if you are using the old-style csproj files s I'm not seeing this in my test-harness.
I can push a v3.0.1 version that does this, but it seems to defeat the purpose of netstandard. So I'll ask around to see if there's a better solution, but will create that new release to tidy things up for you if this really is the only solution.
from succinct.
This only appears to happen if you are using the old-style csproj files
Hm, I'll investigate how to upgrade to the new project file format to see if this helps. Things change quite often now, project.json died even before I had a chance to try it.
from succinct.
Seems that new csproj format doesn't work for WPF projects at this moment.
http://www.natemcmaster.com/blog/2017/03/09/vs2015-to-vs2017-upgrade/
dotnet/project-system#1467
I'll try Paket to see if that helps to keep reference list sane.
from succinct.
Microsoft's @terrajobst has kindly provided more details of what's going on with netstandard at the moment, in this answer to that Stack Overflow question you linked to.
Assuming I'm reading that answer correctly, the current choices are:
- Accept the extra dependencies that a dotnetstandard library pulls into a framework project,
- Target net45 too in the nuget package to prevent those dependencies,
- Handcraft the nuspec file to only pull in the dependencies really required,
- Wait for netstandard 2.0, which will fix many of these issues.
Option 1 isn't good for you. Option 3 sounds hard and as Immo says, it risks being fragile. So option 2, followed by a new release using option 4 when netstandard 2.0 is released seems the best route. So I'll push out a v3.0.1 version that includes net45 shortly.
from succinct.
I've pushed a v3.0.1 version to nuget. Would you mind testing it to see if it solves this issue for you, please? If it's OK, I'll then update the docs to make it "public".
from succinct.
@DavidArno yep, everything is nice. I created a demo project that targets .Net 4.6.1. SuccincT 3.0.1 brings only one package, SuccincT 3.0.0 adds 46 more packages as dependencies into packages.config
.
from succinct.
Excellent. Docs updated to make v3.0.1 "official".
from succinct.
Related Issues (20)
- Generic ValueOrError HOT 3
- A non-exception Value<T> alternative for unions HOT 2
- Maybe.Some(null) does not throw and has a different behavior than Maybe.None() HOT 8
- SuccincT Roadmap HOT 12
- When will version 3.1.1 be published to NuGet? HOT 3
- Remove Maybe type and change Option to be a readonly struct HOT 5
- Checklist for the v4 release HOT 1
- As C# 7 now supports discards, the Ignore function is redundant and should be removed HOT 1
- As C# 7 now supports discards, the Ignore function is redundant and should be removed HOT 1
- Add pattern matching to the Either type HOT 1
- Runtime Exception of type System.IO.FileNotFoundException HOT 4
- Change enum parsers to use Enum generic constraint HOT 1
- Add positional pattern matching support to Option<T> HOT 1
- Add positional pattern matching support to ValueOrError types HOT 1
- Add positional pattern matching support to Success<T> HOT 1
- Add positional pattern matching support to Either<TL,TR> HOT 1
- Add positional pattern matching support to Union types HOT 1
- Investigate adding cons support for async streams
- Remove the use of <T> at the end of Succinc<T>
- Create a new release of SuccincT, targeting .NET 6, with all the redundant features removed HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from succinct.