0

We have a solution (called, say, Cabbage) that's split up into a WCF-based backend (Cabbage.Backend), and a frontend (Cabbage.Frontend). A problem that crops up somewhat often is that a developer changes the definition of a WCF service in Cabbage.Backend, then updates the service reference in Cabbage.Frontend without first rebuilding Cabbage.Backend. (The services are meant to be tightly coupled this way, the layers are only separated by WCF to let us deploy backend hotfixes quicker.) This regenerates the service client based on a random old build instead of the current state of the source code, the BE dev calls it a day, hilarious merge conflicts occur when the FE dev updates the client himself.

Is there any way to make Visual Studio automatically rebuild the service project / the whole solution before every run of Update Service Reference to avoid this?

4

1 に答える 1

1

ビルド時間が長くなる可能性がある場合は、バックエンドのプロジェクト依存関係をフロントエンド プロジェクトに追加することを検討してください。フロントエンドをビルドすると、バックエンドとそのすべての依存関係もビルドされます。

于 2012-12-14T04:18:25.643 に答える