Skip to content

Remove incompatible reflection api's to possibly allow for single file deployments #1699

@TraGicCode

Description

@TraGicCode

Describe the feature.

I'm trying to perform a single-file build in modern .NET to simplify the executable I ship, using the following command:

dotnet publish "./MyConsole.csproj" \
    --configuration Release \
    --runtime linux-musl-x64 \
    --self-contained true \
    --output /app/publish \
    --no-restore \
    -p:PublishSingleFile=true

Unfortunately, NServiceBus.RabbitMQ is using reflection APIs that are incompatible with single-file deployment, specifically:

Assembly.Location
Source link

See the official documentation here: Single-file API incompatibility

While I’m not certain this will unblock the entire scenario—since other parts of this NuGet package or even the main NServiceBus package might use additional incompatible APIs—resolving this particular issue seems like a step in the right direction. I would like to propose this as a feature request to make NServiceBus.RabbitMQ compatible with single-file deployments.

Additional Context

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions