I am not political – But I found this Http 404 page to very clever and witty!
Few months back I presented “Usability & Agile Development”.
It’s been a while since I have blogged something here. In fact this year until now, i haven’t blogged anything! Things are going to change and I have decided to combine my personal and programming blog into one…this is like re-branding myself. So here it is..binoot! This will be my all things blog from now on. At work, I have been dealing with lot more than programming for last couple of years, less of programming and more of Agile Team Management. I am planning to write something on that soon…always been interested in Usability aspects of web, that will be another area that I think I will cover here, and of course some .net programming tidbits.
So watch this space, while I make this site a little more interesting!
And I promise I will add some cartoons and caricatures too!
If you were a ReSharper user with Visual Studio 2008 (or 2005 in that case) and you installed Visual Studio 2010 now and want to continue use ReSharper, following is what you do. Naturally since you installed Visual Studio 2010 after your ReSharper install, ReSharper integration will not be there in Visual Studio 2010, and you will need to associate Visual Studio 2010 with ReSharper.
Now open your Visual Studio 2010, ReSharper will ask for license information, enter your user id and license key, and you will notice that ReSharper appears on your menu bar.
You need to keep your fingers crossed when you install any Microsoft products, every version of every product I have used, installer behaviour changes!!! And these softwares are huge in size too… I am talkling about developer products here, like Visual Stuidio, SQL Server, etc. I was trying to install SQL Server 2008 Developer edition in one of my machines today and was hit with the infamous “VSShellInstalledRule”. Ok, I agree its a rule and a dependency, but my point is I had to click through the installer Wizard many steps deep before you get this wrench. Urghhh!!!
This error is complaining that I need to have Visual Studio 2008 SP1 installed. I have Visual Studio 2010 installed in my machine (and also VS 2008), so I am assuming that installer should be smart enough to acknowledge the presence of VS 2010 and live with it. Am I asking for too much here?
15 seconds with Google, I was pointed to the comments section in this blog post where a tip was given how to ignore these rules when setup is run (Thanks Paul)
Basically you do this:
Setup /ACTION=install /SkipRules=VSShellInstalledRule
Until your next installation…peace 🙂
[update] I thought this would fix my issue, it helped me to go ahead with the installation, but ultimately it failed in installing components that requires Visual Studio integration (like integration services). So now my challenge is to make this stupid installer realize that I have a newer version of Visual Studio (2010) or install Visual Studio 2008 SP1 (that takes forever)
sad, I am 😦
[update] So I installed VS 2008 SP1, I had ended up with a messed up installation from previous trials, I removed the installation completely, removed my SQL Server 2005 Management Studio Express (that was another error in the list), tried again. I still got some error saying regarding Reporting Services. This is because it installed RS catalog db, so it wants me to install using a “files only mode”, Google to rescue again..
setup /q /ACTION=install /RSINSTALLMODE=”FilesOnlyMode”
I rest this case now.
Once upon a time there was a WidgetMetadata named ‘ComboBox’, he was stored in an Oracle database behind many layers of abstraction and wanted to grow up and be rendered one day. As the WidgetMetadata matured, a WidgetMetadataObject was created, next came a WidgetBuilder. The WidgetMetadata started noticing changes in himself. All of a sudden his attributes were correctly applied. The WidgetMetadata was very confused, he had many rows of data that weren’t there before…
Thanks Josh… this is exactly what I was looking for 😉
For the record, Josh is one our stalwart developer who is leaving us for better and brighter future. We wish him all the good luck!