Skip to main content

Does SharePoint 2010 run on Vista?

This ought to be a simple Yes/No question. Either it runs on Vista or it doesn't. If it doesn't, that's just in line with what we have with SharePoint 2007. You need a server OS to run it. The twist is SharePoint 2010 is 64-bit only. So to even evaluate it (which you certainly ought to before you recommend it over the 2007 version), you need Windows 2008 64-bit server with Hyper-V. Yikes!

Anyway, prior to this week I had accepted this fact and also that I'll probably not get an evaluation copy anytime soon (since I don't have the server OS or Hyper-V). Anyway, I found out this week that the RTM version of SharePoint actually supports Windows Vista and Windows 7. Imagine my joy. So today, I tried to install it on my 64-bit Vista laptop and the instructions I found are on this page: http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx

Take a minute to open that link and just peruse the instructions. I'll wait....You back? Can you believe that? Microsoft really expects people to jump through all those hoops just to install SharePoint 2010 on Windows 7/Vista? Wow! How hard would it be for them to create a OS specific installer? Instead they want us to extract the installer, change a config file, install 5-6 separate components, turn on a bunch of features in IIS and then run the setup file.

BTW, I went through the steps, install all those components and the end result? The freaking installer is asking for a product key and there isn't one for the trial (not beta) software. What a waste of time.

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…