Skip to content

Refactor Bridge so BridgeResourceFolder is not provided by BridgeClient #334

Closed
@roncain

Description

Today the BridgeResourceFolder is sent to the Bridge by the BridgeClient, and this is how the Bridge accesses its IResources. But this solution cannot work for x-plat because the Bridge resources cannot be built by Linux or OSX. Moreover, it means we would need a general solution to have Linux and Windows machines share a folder, just for this scenario. The solution is to let Bridge.exe default to a BridgeResourceFolder it has already built and to remove the code from BridgeClient to specify it. Therefore, the BridgeResourceFolder is declared wherever the Bridge is started, not where it is used by the client.

It also means the DELETE verb to config should not alter the BridgeResourceFolder, but instead should simply release all the resources and AppDomains

Metadata

Assignees

Labels

infrastructureIssues related to the build, packaging, testing or related areas.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions