.NET Framework Developer Center >
.NET Development Forums
>
64-Bit .NET Framework Development.
>
32 and 64 bit ready code .NET
32 and 64 bit ready code .NET
- Hi is there any automated testing tools that checks the code for 32 and specially migrating to 64bit code, and windows 7 ready?I am thinking mostly about API calls and functions.Best regards, Patrik
Answers
- I think it was fairly clear, he's looking for automated tools that check code for 32->64 bit and windows 7 migration problems.
I don't know about tools, but here's what I'd do to check out code:
1. P/Invoke signatures. Try doing a code search for 'DllImport'. Specifically, look for ints that should be IntPtrs.
2. Custom control drawing (Windows Forms). I don't know a whole lot about this one but I've seen a lot of problems.
3. Security... try running the app/test suite as a user instead of an admin and see what happens...- Marked As Answer bypatti_nyl Monday, November 16, 2009 8:29 AM
All Replies
- Hi,
Could you clarify your question? are you wondering how to migrate your application from 32-bit to 64-bit?
Thanks,
Eric
Please remember to mark helpful replies as answers and unmark them if they provide no help. - I think it was fairly clear, he's looking for automated tools that check code for 32->64 bit and windows 7 migration problems.
I don't know about tools, but here's what I'd do to check out code:
1. P/Invoke signatures. Try doing a code search for 'DllImport'. Specifically, look for ints that should be IntPtrs.
2. Custom control drawing (Windows Forms). I don't know a whole lot about this one but I've seen a lot of problems.
3. Security... try running the app/test suite as a user instead of an admin and see what happens...- Marked As Answer bypatti_nyl Monday, November 16, 2009 8:29 AM
- Yes, what I was looking for was an automated tool checking my 32bit code if it is 64bit ready!I have seen some blogs and tutorials telling about C99 standard, and P/Invoke problems that should be taken into consideration when implementing.Actually we now have a custom control in .NET 2.0 that is behaving totally different on a 64bit platform (w7 x64).The control is not using any native objects, so I am excluding invoke to native problems.Are there any other typical design problems that I could investigate?thanks, Patrik


