CODE

Probably one could be old and other new, but both are released on the same day  

QUOTE(dhanesh @ Feb 26 2007, 10:45 AM)
EDIT: I am confused on which version of orca should i download >>THIS<< or >>THIS<< , one is installable bits and the other one is normal. whats the difference ?

There is no difference in the versions between the both files, they are of the same release. They are different only in the way thy are gonna be used. If you use the Installer Bits download, once you download the various parts of the file, you'll extract them to get an Installer that will install the new SDK kit just like any other Windows Installation.

The other is a Virtual Image. Once you download all the files and extract them, you'll get an Virual PC image that can be loaded as a Virtual PC using the VirualPC software which you can get from the sites I've mentioned in the previous post. There is no need to installl this version. So there is no chance of getting your system files corrupted. You can test this software without harming your OS. Microsoft has recently started giving Virtual PC images of all its Softwares that are in Testing so that the testers can test them without harming or losing their data when the Beta software fails.

This post has been edited by livingston: Mar 4 2007, 06:58 PM

My program created from vb.net 2005 which include the cryptography features of to.0 framework does not run in Vista, is there anyone can explain why?

-Redlion

I have seen that for the most part you should have no problems with Vista unless you are trying to perform something “administrator duties.” This involves requesting higher privileges over what you are currently granted. Even at this it will not stop it from working on Vista, it will only show more annoying dialogue boxes asking if you really want to do this. The main goal behind making a Vista compatible program is to only ask the user for elevated privileges once and then handle the rest internally.

If your program only adds numbers together then you shouldn’t worry about Vista compatibility. You should only worry if you are trying to access restricted parts of the file system (c:\program files) or modifying certain registry keys. This can also apply to installing new components or the program itself.

If you use VB.Net 2005, it should be building against dot Net 2.0. Then it should works properly in vista. Dot Net 2.0 is supported out of box in vista. Cryptography might have diff in terms of vista and xp. I've once found out that one particular encryption produce 2 diff output from the same input, in XP sp1 and sp2. So i assume that vista might have drop support for some older type of cryptography engine. Try with a diff one and see if it still works in vista. Or better still, compile in vista.

Two different results from the same ctypto standard, now that’s scary.

Yes, indeed. I was using that to encrypt the license key of my software. It turn out not working, can't get the license key match on one particular client. Later only i found out the difference, as he's still using XP SP1, and most of my other client uses SP2 without problem. I did a test program that tries out all diff type of encryption using the same input to narrow down the right encryption to use for both windows. Now i'm using "RijndaelManaged". So far so good.