| 5 Mar 2025 |
 GGG | The .NET Framework upgrade tool | 21:32:23 |
 6pak | or you mean for the project format | 21:32:24 |
| GGG | It should do this too | 21:32:26 |
| 6pak | looks like it does, but I doubt it will just work with a project of this size | 21:33:56 |
| 6 Mar 2025 |
 lzcunt | Is the migration tool upgrade-assistant? | 20:49:03 |
| lzcunt | I think it's the case, the "convert to SDK-style" uption in upgrade-assistant seems to work | 21:00:47 |
| lzcunt | * I think it's the case, the "convert to SDK-style" option in upgrade-assistant seems to work | 21:00:53 |
| GGG | Yes, that's what I had in mind | 21:10:20 |
| lzcunt | It's still tedious doing it for every project | 21:11:18 |
| GGG | I think it can work on a solution file if you give it one | 21:13:12 |
| lzcunt | Seemingly can't | 21:13:22 |
| lzcunt | It does the .NET version upgrade analysis on the entire solution tho | 21:13:44 |
| lzcunt | but I'm not interested in version upgrades | 21:13:53 |
| 7 Mar 2025 |
| lzcunt | ok so the automated migration broke LOTS of stuff so I'm going to try the latter | 12:35:24 |
| lzcunt | how long should nuget-to-json take at most? | 12:35:49 |
| lzcunt | * how long should nuget-to-json take at most? It's been running for 10 minutes or so | 12:36:01 |
| lzcunt | and is there a package that is built with mono & packages.config so I can take a look at how it's done? | 12:45:06 |
| 6pak | depends on your internet connection, but it should take however long a restore would take for you | 14:33:21 |
| 6pak | 10mins sounds way too high | 14:33:24 |
| 6pak | I doubt there is | 14:33:33 |
| 6pak | you might be able to reuse the nuget-to-json though | 14:35:07 |
| 6pak | just make a regular stdenvNoCC.mkDerivation which uses mono's xbuild in buildPhase and nuget restore in configurePhase and wrap that in addNuGetDeps | 14:36:02 |
| GGG | In reply to @sananatheskenana:matrix.org
how long should nuget-to-json take at most? It's been running for 10 minutes or so How did you run it? It should be pointed to a directory where you checked out all the packages to | 14:59:56 |
| lzcunt | I ran it as `nuget-to-json out` | 15:00:36 |
| lzcunt | I think the issue might be that `nuget restore` fetches the nupkg instead of just the metadata, and in fact the metadata is not in the output only the package is | 15:01:25 |
| lzcunt | In reply to @6pak:matrix.org
just make a regular stdenvNoCC.mkDerivation which uses mono's xbuild in buildPhase and nuget restore in configurePhase and wrap that in addNuGetDeps yep that's the plan | 15:02:03 |
| lzcunt | In reply to @sananatheskenana:matrix.org
I think the issue might be that nuget restore fetches the nupkg instead of just the metadata, and in fact the metadata is not in the output only the package is maybe we could add nuget restore support to nuget-to-json? It'd essentially be using the already fetched nupkg instead of prefetching the url from the metadata | 15:03:15 |
| lzcunt | so basically since there's no metadata in the output directory, nuget-to-json is in an infinite loop i think | 15:05:06 |
| GGG | In reply to @sananatheskenana:matrix.org
I think the issue might be that nuget restore fetches the nupkg instead of just the metadata, and in fact the metadata is not in the output only the package is No, as long as it unpacks the packages into the directory it should be fine | 15:22:31 |
| GGG | Lemme review the source, but I don't remember it depending on any specific metadata on the output directory | 15:23:28 |
