- Determine office 32 or 64 bit install#
- Determine office 32 or 64 bit code#
- Determine office 32 or 64 bit Pc#
- Determine office 32 or 64 bit professional#
- Determine office 32 or 64 bit windows#
Determine office 32 or 64 bit windows#
If you have Windows XP, there are two methods to determine whether you are running a 32-bit or a 64-bit version.
Determine office 32 or 64 bit Pc#
When System Summary is selected in the navigation pane, the operating system is displayed as follows:įor a 64-bit version operating system: X64-based PC appears for the System Type under Item.įor a 32-bit version operating system: X86-based PC appears for the System Type under Item. The operating system is displayed as follows:įor a 64-bit version operating system: 64-bit Operating System appears for the System type under System.įor a 32-bit version operating system: 32-bit Operating System appears for the System type under System.Ĭlick Start, type system in the search box, and then click System Information in the Programs list. Method 1: View System window in Control PanelĬlick Start, type system in the search box, and then click System in the Control Panel list. If you have Windows Vista or Windows 7, there are two methods to determine whether you are running a 32-bit or a 64-bit version. For more information about system requirements, see Lync Online and Online Meeting Add-in for Microsoft Lync 2010 System Requirements.
Determine office 32 or 64 bit professional#
The minimum operating system requirements for Lync 2010 is Window 7, Windows Vista, or Windows XP Professional with Service Pack 3 (SP3).
Determine office 32 or 64 bit install#
I’m guessing it would return the architecture of the emulated OS.When you install Microsoft Lync 2010 communications software, depending on your computer’s operating system you will need to choose between a 32-bit version or a 64-bit version installer. If you’re running your assembly from within an emulator, I don’t know if this returns the architecture of the emulated OS or the host OS.The OSArchitecture property of the Win32_OperatingSystem WMI class is said to not be present for Windows XP, so it probably doesn’t. I don’t know if this works under Windows XP 64-bit.
This method *will* return “64-bit” if your OS is 64-bit and your assembly was compiled using the target CPU “x86”. So, if you’re looking for a simple function that will reliably return whether or not the OS your assembly is running in is 32-bit or 64-bit, use this. You’ll need to add a reference to System.Management to your assembly for this method to work.
Determine office 32 or 64 bit code#
This code was written in VS.NET 2005 (.NET 2.0). If osClass IsNot Nothing Then osClass.Dispose() See above MSDN link for more information.įor Each mgo As In osClass.GetInstancesįor Each prop As In mgo.Properties ' NOTE: I'm not 100% sure if this detects 64-bit versions of XP. If the property is not found, the OS is assumed to be 32-bit. ' Loop thru all properties of the single instance of the Win32_OperatingSystem class and look for the property which will tell us if ' Get the singleton Win32_OperatingSystem WMI class so we can access properties about the OS. Public Function GetOSArchitecture() As Stringĭim osClass As = Nothingĭim result As String = "32-bit" ' Default to 32-bit for OSes which don't support the OSArchitecture property of the Win32_OperatingSystem WMI class. ''' Requires a reference to System.Management. ''' If an error occurs, the result will be an empty string. ''' Returns a string describing whether the OS is 32-bit or 64-bit. Here is a method you can use in your VB.NET assemblies to determine whether or not the assembly is executing in a 32-bit or 64-bit OS: ''' I couldn’t find any proper code example for what I needed, so I came up with one myself. WMI is a Windows OS infrastructure which provides information about the OS and available resources (RAM, hard drives, database servers, etc.). That’s just not right.Ī third recommendation had to do with searching for the existence of particular environment variables, but those, too, are editable by the user and not guaranteed to exist.Ī fourth recommendation I came across involved using Windows Management Instrumentation. Not only does that mean accessing the slooooooow hard drive, but it’s also accessing data that the user can modify himself. Others recommended searching the file system for the existence of a “C:\Program Files (x86)” folder. If you compile your assembly with the target CPU “x86”, for example, IntPtr.Size will always be 4 bytes, regardless of the OS architecture.
This works fine…but only if your application is compiled for “An圜PU” as the target CPU. Many people recommended I simply check the length of an IntPtr: If IntPtr.Size = 8 Then I did a lot of searching on the web, but found the results quite lacking.
Stupidly, neither the My.Computer.Info nor the System.Environment classes contain details on whether or not the OS is 32 or 64 bit, though they contain other information describing the OS.
At work I recently had to find a way to determine whether an application was running on a 32-bit or a 64-bit version of Windows.
0 kommentar(er)
