What should we do when there are multiple frameworks in a project?

nkolev92 / DependencyVisualizer

A tool to help you visualize the dependencies in your .NET project

MIT License

2 stars 1 forks source link

What should we do when there are multiple frameworks in a project? #1

Closed nkolev92 closed 1 year ago

nkolev92 commented 1 year ago

Say you have a multi targeted project:


<Project Sdk="Microsoft.NET.Sdk">

    <PropertyGroup>
        <TargetFrameworks>net6.0;net5.0</TargetFrameworks>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="NuGet.ProjectModel" Version="5.0.0" />
    </ItemGroup>

        <ItemGroup Condition=" '$(TargetFramework)' == 'net5.0' ">
        <PackageReference Include="Newtonsoft.Json" Version="13.0.1" />
    </ItemGroup>
</Project>

What should our tool build?

A few options I can think of:

Multiple separate graphs in the same file?
Multiple graphs in multiple files?
Require the user to specify a framework, example, net5.0 or net6.0 and allow only one?
Do your best to overlap both graphs? This is ideal, but probably super challenging to do early one. There's a Visualization aspect that'd be difficult to figure out too.

nkolev92 commented 1 year ago

cc @heng-liu @peeku1988 Curious what you 2 think.

nkolev92 commented 1 year ago

I've added some APIs to read multiple graphs.

heng-liu commented 1 year ago

My thoughts for now:

Multiple separate graphs in the same file? => not sure if the graph will be too big to be view friendly
Multiple graphs in multiple files? => People will be able to check the difference between graphs for different TFMs. And it's easy to implement.
Require the user to specify a framework, example, net5.0 or net6.0 and allow only one? => People has to run multiple times to get the same experience with the second one.
Do your best to overlap both graphs? This is ideal, but probably super challenging to do early one. There's a Visualization aspect that'd be difficult to figure out too. => not sure if the graph will be messy if there are lots of difference between TFMs. And it sounds challenging.

Those are just my preliminary thoughts. When I finished generating DGML files, we can check the real examples and see which one is better. What do you think?

nkolev92 commented 1 year ago

Let's do multiple files first then and go from there :)

I think multiple graphs in the same files is the best balance between easy to do/helpful, but I very much agree with your concern about the size, so we won't know until we start generating the graphs, so let's do multiple graphs, multiple files now.