![]() ![]() Developing with.NET: Universal 32- and 64-bit driversBy following the recommendations of the ASCOM Initiative and using either C# or Visual Basic.NET languages, you will be able to create a universal driver that will run under 32- and 64-bit environment with no extra effort on your part. Thus, if your driver is 32-bit, that will probably be sufficient for now, but do look forward as large format cameras are driving some applications to 64 bit. Most astronomy software is 32-bit, and most of the drivers out there are also 32-bit. Furthermore, a driver must register itself for COM in the subsystem (32- or 64-bit) for which it was developed. In other words, a 32-bit application cannot use a 64-bit driver, and vice versa. What is important to driver writers, though, is that the implementation of COM (see ) is separate for 32- and 64-bit applications and drivers. It's beyond the scope of this article to give general information on the 32- and 64-bit subsystems in Windows. This is a technical miracle from Microsoft.The ASCOM architecture supports both 32- and 64-bit environments, however there is a great deal of confusion and old wives' tales surrounding this area. They are unaware that they are running on a 64-bit system. Most astronomy applications (except camera controllers for large format cameras) run under the 32-bit subsystem, and use 32-bit drivers. Developing for 32- and 64-bitsRunning on a 64-bit Windows operating system does not mean all applications and ASCOM drivers are 64-bit. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |