Also consider any ODBC calls to databases for which there are only 32 bit
drivers. I've had this problem with MYOB drivers for example.
On Tue, 19 Feb 2019 at 13:42, Greg Keogh wrote:
>
> Just doing it would require full regression testing, would it not?
>> I don’t suppose there is a simple
> 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?
>
Okay, too big to easily test. If it was mine, I suppose I'd first run
searches for [DllImport] attributes and similar things in the
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 wrote:
>
> My question is what should I consider if I want to change to 64 bit? Can
>> anything
> 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
.NET Framework 1.1 was x86 only if IRC.
From: ozdotnet-boun...@ozdotnet.com On Behalf
Of Tom P
Sent: Tuesday, February 19, 2019 2:04 PM
To: ozDotNet
Subject: Legacy Asp.net application change from 32bit to 64bit
Hi folks
I’ve inherited a legacy web application, written originally in .net 1.1
Hi folks
I’ve inherited a legacy web application, written originally in .net 1.1 and
upgraded several times, it’s a mess and very large. The minimal
documentation states the IIS application pool is to be set to 32 bit. I’m
not sure of the reasons and none of the previous developers are around any
