search

PrismLibrary / Prism

Prism is a framework for building loosely coupled, maintainable, and testable XAML applications in WPF, Xamarin Forms, and Uno / Win UI Applications..
Other
6.35k stars 1.64k forks source link

[BUG] Nuget error "Part URI cannot start with two forward slashes" when install Prism.Container.Abstractions 9.0.106.9543 #3253

Closed nagneo closed 1 week ago

nagneo commented 1 month ago

Description

In Visual Studio 2015, Error is occurred in nuget package manager when I installed Prism.Container.Abstractions. I can not see the installed nuget package list in my project like below captured images.

https://github.com/NuGet/NuGetGallery/issues/8950

스크린샷 2024-09-12 121159 스크린샷 2024-09-12 121133

Steps to Reproduce

  1. Create WPF Project in Visual Studio 2015.
  2. Install Prism.Core latest version 9.0.537
  3. Check the list of nuget package manger
  4. Click Show errors in output. "Part URI cannot start with two forward slashes."

Platform with bug

WPF

Affected platforms

Windows

Did you find any workaround?

No response

Relevant log output

No response

brianlagunas commented 1 month ago

Does your project build? The output window seems to indicate that it does.

Does it happen if you switch to using PackageReferences instead of the old packages.config?

nagneo commented 1 month ago

Yes, the build succeeded for this project, but the code isn’t actually using Prism.Container.Abstractions—it's just imported. Do I need to do anything additional to ensure that it’s been imported correctly?

I’m unable to install Prism.Unity because of the following error: “An error occurred while retrieving package metadata for 'Prism.Container.Abstractions.9.0.107' from source 'D:*\TestApplication\packages'.”

Visual Studio 2015 doesn’t support the PackageReferences option, which is only supported in VS2017 and later. In Visual Studio 2022, however, there are no build or NuGet package errors; everything works fine.

In my real project, where I’m testing the migration to Prism 9 in VS2015, I’m encountering a build error similar to the one in GitHub Issue #3235.

Should I consider upgrading to Visual Studio 2022 to successfully migrate to Prism 9?

dansiegel commented 1 month ago

Personally I would suggest that you use VS2022 out of good practice. There is no way that we can or will test older versions of Visual Studio. If you have some weird hard requirements that force you to use an older version I would suggest opening a ticket with Microsoft.