Windows Vista - Yet another jargon which created ripples, made people to wait for long and currently causing considerable perturbation among s/w community.I didn't get to work with any of the beta versions for I have no personal system where I can take the risk of changing the OS, but my current project gave me a chance to work with that.
The UI was so cool that I immediately liked it. Itz like this beautiful babe whom u c in high end malls or at ur gym who will sweep u instantly with her hot and sweet face, but in a long run she turns out to be a problem due to high maintenance and the level of individuality u need to shed in order to be with her.
That’s what my experience with vista is after I started working on my current project which is to port our application so that it can be supported in vista!!!
Vista has brought in a sea of changes like earlier microsoft’s products but the readiness with which knowledge up gradation is happening in not swift. Let it be in .Net Framework, or about CLR or about different foundations or in UAC and IC, things are not very clear.
I am not gonna talk about vista. If wanted, u can visit itz wiki or home page. I just want to put my experiences with vista.
As expected, in order to check whether ur product is compatible with vista, microsoft gives u two great tools with which u can find the areas ur product gonna suck in vista and things u need to do to improve it. But I may not recommend them for I don’t have any positive experiences with them. I struggled for three days to get the thing installed and up and the end was not worth the means! The tools are application verifier and Microsoft Application Compatibility Toolkit. It tried retracing the error that app verifier log file threw, but failed ...
For some strange reasons, some of the addins were not getting enabled on our product.After
some head breaking we found out that some of them are due the fact that the dlls are not getting registered during installation. Also I needed to break my head while trying to install visual studio on vista and banged it faster when I came to know that Visual studio 6.0 is not supported but visual basic 6.0 is supported !!.
A couple of changes were needed to be made in our code (remember I said about losing urself to the girl ??)
1. Opening handle to HKLM with all access mode.
2. If u had relied on location of documents and settings folder then u r in for surprise.
3. can’t write any thing into c:\program files, incase u have installed ur product and wanted to generate some files there .
But these were minor ones. The big challenge I am facing is that one of our COM components is not getting raised when called from program.
But if I run this VB component from development environment, it works fine..
Still working on that ...




