Describe the bug
When working with the Perl Hosting integration, two resources installing the same package in their respective local libs would collide on aspire startup because the ResourceInstaller names collide.
Regression
No response
Steps to reproduce
1. Create a new apphost.
2. Add the perl hosting integration
3. Add a script and use .WithPackage("Some::Module");
4. Add another script or api using .WithPackage("Some::Module");
5. aspire run
6. Error on resource installer name collision.
Expected behavior
That they be constructed such that they have unique names to avoid the collision. This is how the Python integration does it with their installers.
Screenshots
No response
IDE and version
VS Code
IDE version
No response
Nuget packages
CommunityToolkit.Aspire.Hosting.Perl (unversioned, because it's currently not released even in Preview)
Additional context
No response
Help us help you
Yes, I'd like to be assigned to work on this item
Describe the bug
When working with the Perl Hosting integration, two resources installing the same package in their respective local libs would collide on aspire startup because the ResourceInstaller names collide.
Regression
No response
Steps to reproduce
Expected behavior
That they be constructed such that they have unique names to avoid the collision. This is how the Python integration does it with their installers.
Screenshots
No response
IDE and version
VS Code
IDE version
No response
Nuget packages
Additional context
No response
Help us help you
Yes, I'd like to be assigned to work on this item