Viktor Hofer comments

Results 314 comments of


                                            Viktor Hofer

VMR packages should publish to the RepoOrigin's channel respective feed

cc @mmitche

VMR packages should publish to the RepoOrigin's channel respective feed

I think it's the opposite. With the current design, packages don't get published to the expected feeds and people will need to understand how the VMR publishing works.

Dotnet test integration

Episode IV.V - A New Snack 🤣🤣🤣

[automated] Merge branch 'release/9.0.2xx' => 'main'

Maybe this happens because of the pinned dependency? https://github.com/dotnet/sdk/blob/4c6814f597b91a06c6d1816aa533b9d9914c4be8/eng/Version.Details.xml#L632

[automated] Merge branch 'release/9.0.2xx' => 'main'

I pushed a commit that will hopefully fix this.

[main] Update dependencies from dotnet/arcade

@nohwnd / @Evangelink can you please take a look at this PR and try to get it in? We need this for dependency flow into the VMR.

Downgrade TFMs to NetMinimum and NetFrameworkMinimum

VMR validation PR: https://github.com/dotnet/dotnet/pull/1369

What is the expected path for ResolvePackageFileConflicts to work with repositories that build their own platforms

cc @natemcmaster in case you are hitting this too in aspnetcore

What is the expected path for ResolvePackageFileConflicts to work with repositories that build their own platforms

The reference assemblies are resolved correctly, the higher version is taken. I was talking about the copy local items here, the runtime assemblies that are coming in from referencing packages...

What is the expected path for ResolvePackageFileConflicts to work with repositories that build their own platforms

I was talking with @ericstj about this offline and he suggested to include our runtime directory which contains our live build assemblies in `_RuntimeAssetsForConflictResolution` so that they are passed into...