< Back to Start

Deploy even when your solution is not ready

welw✉️ 20260924

Consider the following environment: Development machine connected to dev network. Factory environment connected to factory network. Client wants solution on factory network.

You build an app and tested it locally. Client did not approve first revision, so you prepared another.

You deploy to factory server and as expected: nothing works. You did not bundle a static build because saving 5 seconds on CI is worth it and you assume .NET runtime installed on their computers. Finally, you think that database connection via SAP SQL and ODBC would work.

So you ask your system administrator to install all necessary software. Due to hierarchical structure of organization it takes more than a day.

You ask the client to run the app and nothing happens. You try copying from network share to desktop, because you suspect permissions problems. No: nothing.

After a while you get a screenshot from Windows Event Viewer reporting application crash and stack trace: Missing ODBC data source. Of course, you did not install it at client’s computer.

Next time you wish to deploy an application, ask your client for early deployment. This will start all machinery necessary necessary to get your solution deployed, like for example opening tickets, waiting for IT admin to install software and see how your program crashes in client environment.