octopusdeploy / icanhasdotnetcore Goto Github PK

This is because it does not get dependencies.

.NET Core 1.1 projects now use a .csproj project format instead of package.json (which has also changed with the last update).

So now there're package.json, csproj v1 and v2 that are used for dependency management with nuget on .NET Core projects.

My project uses Win32 DLL imports, but ICanHas doesn't seem to detect this. Would be nice if they were at least flagged.

hi,
it would be cool, if this tool could use all configured nuget repository instead only use nuget.org

Hi! Not seeing any similar issues or PRs, I'm confident this isn't the right forum for this, but here goes. Can you update the data to note that iTextSharp is replaced by https://www.nuget.org/packages/iTextSharp.LGPLv2.Core/? Currently iTextSharp shows there are no replacements. Alternatively, what's the best way to report issues like this?

Many packages (e.g. FSharp.Data) have a portable PCL (e.g. profile 7 or 259), which, if I'm not mistaken, can be used as .NET Standard components (if I'm not mistaken)? However it appears these packages are being shown as "unsupported" with "no package available", e.g. in the package visualization for https://github.com/Microsoft/visualfsharp/blob/master/packages.config

(Note: It could be that your tool is being very smart and somehow knows that the particular dependency in question is on a net45 component in a package that also has a profile 259 component? However the profile259 component is probably adequate to resolve the dependency)

I just analysed all the packages on my solution and would be nice to be able to somehow save the results and suggestions. At the moment you only provide the graph data which is not that much worth it as I don't know which packages are compatible with .Net standard and which not.

The stats page (https://icanhasdot.net/Stats) has a deadlink (404):

Directs you to:

https://github.com/OctopusDeploy/ICanHasDotnetCore/tree/master/Magic/NugetPackages/Data

which returns a 404.

[Error] Error processing package "Swashbuckle.AspNetCore"
System.ArgumentException: '1.0.0--rc1' is not a valid version string.
Parameter name: version

footer of homepage.

it currently links to https://github.com/OctopusDeploy/ICanHasDotnetCore/Issues which doesn't work. it needs to be https://github.com/OctopusDeploy/ICanHasDotnetCore/issues

If you're willing to publish to the Chocolatey community feed, it would make it easy to install and keep updated.

I believe that it would be super useful to have the data exported into a .csv or a similar format.
For my use case- I am documenting each of the dependencies that are not .Net Core supported and I had to build a table with all of the same information that you provided to me.

https://seq.octopushq.com/#/events/?filter=@Id%20%3D%3D%20%22event-59502953ae8308d3e1082e0100000000%22&show=expanded

Mobile is..... less than stellar

Hi, great repository. I was browsing the code and found the Option class. This look like 'value-safe' implementation fo the Nullable<T> struct. Could you provide some 'story behind'?

Thank you in advice

it would be super cool to have a buildstatus-style badge to indicate compliance.

.net core|compliant
.net core|non-compliant

or similar

http://fsprojects.github.io/Paket/

https://www.nuget.org/packages/structuremap/

The number one package in the unsupported stats is "Microsoft.AspNet.Razor" but this is replaced by the core variant. It would be awesome if this tool accounted for the changes outlined here: https://docs.asp.net/en/latest/migration/rc1-to-rtm.html#namespace-and-package-id-changes

The font is specified as font-weight: 100; and font-family: Roboto, 'Helvetica Neue', sans-serif;. This font weight is very spindly (regular font weight is 400 and bold is 700) and on a system like mine where a font is available for this font weight, the body text is extremely illegible.

They are currently listed as not supported.

Could we put a great big % indicator on the /Stats page? Something like:

34% of the most common dependencies are available on .NET Core

(Calculated by taking the top 1000 most depended-on packages and seeing if they are ported or not?)

Maybe we could even include a countdown - e.g., "At this rate, we estimate that all of the most common packages will be available on .NET Core by July 2018" :)

Calculated by just taking the day .NET Core was released, today's date, and the % ported already.

I'd like to add another output type, Cypher - based on http://opencypher.org

It allows me to run queries against the data, for example, I can import into my DB and then query something like:

MATCH (p:InvestigationTarget)-[:REFERENCES]->(dependency)
RETURN count(dependency)

To get the number of dependencies for a given package.
Importing is straight forward - basically just a CREATE statement, and in keeping with the current GraphViz style approach would just be a StringBuilder

I'm not sure if you're accepting pull requests for this sort of change or not?

https://seq.octopushq.com/#/events/?filter=@Id%20%3D%3D%20%22event-ea294d5cacb208d3cf8d290100000000%22&show=expanded

Thanks for an awesome tool 👍

Just as an FYI, over at octokit.net we have some packages.config files using the packages.ProjectName.json file name format (which AFAIK is a valid/supported thing in terms of nuget/visual studio) which don't appear to be picked up by an ICanHasDotnetCore scan of the repo, unless I'm missing something

eg:
packages.Octokit.Tests.config
packages.Octokit.Tests-NetCore45.config
packages.Octokit.Tests-Portable.config

Projects that use HTML Agility Pack show there's no .net core, though there is this:
https://www.nuget.org/packages/HtmlAgilityPack.NetCore/