Introducing: System.Numeric.BigInteger(blogs.msdn.com)

submitted by erick(230) 5 years, 4 months ago

Have you ever needed a really huge number? So big it just couldn't fit into any other base-type in the framework? Well, no problem anymore, just use the new BigInteger type. You can now have the ability to use integers of any arbitrary size, so they can exponentiate until the cows come home... or memory runs out, whichever comes first :-) read more...

add a comment |category: CLR |Views: 102

tags: Numbers BigInteger another

Introducing Pipes(blogs.msdn.com)

submitted by erick(230) 5 years, 5 months ago

The Orcas October Community Technology Preview (CTP) includes new types that make it easy for developers to use pipes from managed code. Pipes are used for inter-process communication (IPC) between processes running on the same machine, or processes running on any other Windows machine within a network. read more...

1 comment |category: CLR |Views: 5

tags: Pipes Orcas IPC another

Windows keyed events, critical sections, and new Vista synchronization(bluebytesoftware.com)

submitted by erick(230) 5 years, 5 months ago

There’s surprisingly little information out there on Windows keyed events. That’s probably because the feature is hidden inside the OS, not exposed publicly through the Windows SDK, and is used only by a small fraction of kernel- and user-mode OS features. The Windows Internals book makes brief mention of them, but only in passing on page 160. Since keyed events have been revamped markedly for Vista, a quick write up on them felt appropriate. I had the pleasure to chat at length today with the developer who designed and implemented the feature back in Windows XP... read more...

add a comment |category: Architecture |Views: 42

tags: Vista another

Marshal opaque structs as IntPtr instead of Byte[](blogs.msdn.com)

submitted by erick(230) 5 years, 5 months ago

If you have an opaque native structure that you want to pass through managed code, consider using IntPtr, not Byte[], in your marshalling signatures. Opaque means that you don't care about the contents of the buffer. For example, if in C#, you pinvoke to get an opaque native structure that you then hand to some other native API, the pinvoke definitions should use IntPtr instead of Byte[]. read more...

add a comment |category: CLR |Views: 9

tags: IntPtr Byte CLR another

Screw 2.0, I'm Going Straight to 3.0(weblogs.asp.net)

submitted by erick(230) 5 years, 5 months ago

Recently the discussion came up about using .NET 2.0 in some future products. I work on server products, and we've been using 2.0 there for a while. However, there is a bit of concern around deploying the 2.0 framework with our desktop apps. Our software is shipped ESD style and a lot of customers like to download the trial app before making the purchase. If they try to install the app, but can't because they need to be an administrator to install the .NET framework 2.0, we probably just lost out on the sale. I would venture to guess that a significant chunk of our customers fall into the non-administrator group, so this is a big problem. read more...

add a comment |category: Architecture |Views: 0

tags: .NET3.0 another