tags:

views:

194

answers:

0
+1  Q: 

HttpBrowserCapabilities doesn't detect 64-bit Windows, what's the built-in alternative without parsing user agent string?

The two available detection options for Windows in System.WebHttpBrowserCapabilities are:

Win16 Overloaded.
Win32 Overloaded.

If 64-bit isn't testable, the Win* properties seem rather useless. Besides parsing the user agent string, what's often used in place of these properties (maybe combinations of them)?

related questions

Subsonic Vs NHibernate
How to check For File Lock in C# ?
Is nAnt still supported and suitable for .net 3.5/VS2008?
Limit size of Queue<T> in .NET?
Viewstate invalid when using Safari
Free OCR library
Unhandled Exception Handler in .NET 1.1
Localising date format descriptors
Get a new object instance from a Type in C#
VFP .NET OLEdb provider does not work in Win 64-Bits. Help
.NET Testing Framework Advice
Embedded Database for .net that can run off a network
Automatically update version number
Homegrown consumption of web services
How do you migrate a large app from VB6 to VB .net ?
.NET Migrations Engine
Adding Scripting functionality to .NET applications
SQLite and XSD
Floating Point Number parsing: Is there a Catch All algorithm?
How do I programmatically create a PDF in my .NET application?
How do I sync the SVN revision number with my ASP.NET web site?
XSD DataSets and ignoring foreign keys
Anatomy of a "Memory Leak"
Reliable Timer in a Console Application
How do I calculate relative time?