ACDC wroteKnowing the steps required to move to 64-bit is one thing, but doing it every time you get AwareIM update, is another thing. Try to convince a client (That you're suppose to turn over the app to them) that they have to go and do these steps every time we get an update, blows their mind:
When you build a runtime exe and turn it over to a client for installation, the runtime should contain the same configuration as your development environment. So if you have the 64Bit JDK installed in your dev system it should be already in place for the customer in the runtime - there should no further configuration needed by the customer
At least that's the way I understand it
When I said "Turning over", I meant turning over the code, the development assets to client's IT dept. and not just a Runtime EXE. This way, once the core of the system is designed and developed by a consultant, he/she turn over what he has done (say in 6 months) and the IT team takes over to finish the final product to go to production.
One of the elements that most IT managers look and evaluate on, is the process and steps required, every time they need to update production server.
When you have 64-bit, SSL, Custom Folders, Memory settings, Azure/AWS platform and using a few plugins, with the current manual settings, it get convoluted and it's very error prone.
Due to demand, MS has built a lot of automation into Visual Studio, because they found most of the production problems were related to incorrect settings by different people. And I'm proposing that what Aware should focus to automate these repeated tasks.
