Just doing it would require full regression testing, would it not? I don’t suppose there is a simple way to check if any non compliant old DLLs are used?
On Tue, 19 Feb 2019 at 14:23, Greg Keogh <gfke...@gmail.com> wrote: > > My question is what should I consider if I want to change to 64 bit? Can >> anything break? >> > > I'd just turn off the 32-bit flag in the pool, run it and see what > happens. If it's calling some weird old native API then you should find out > soon enough. > > Strangely enough, I'm in the reverse situation, trying to downgrade to > 32-bit. I have a Web Api in Azure that's calling a 64-bit Borland DLL, so > the minimum plan for 64-bit is ~$80/month, whereas for 32-bit it's > ~$20/month. Lord knows why it's quadruple price for 64-bit. I tried to > build and test in VS2017 with the 32-bit DLL and everything failed and > crashed in every way possible. You think that would be easy, but I'm still > trying to figure it out > > *Greg K* > >> -- Thanks Tom
