Contents tagged with Windows 7
Back home after a few days in Berlin for the European SharePoint Conference 2011. It was a great conference with good speakers and really nice attendees. It was three days full of sessions, expert panels, shoot-outs and SharePoint fun! Thanks to everyone who was there (especially those who came to my sessions :-) and the team behind the conference! And as always it great to meet up with the SharePoint MVP's, MCM's and now even MCA's!
During the attendee dinner the conference team announced the dates for the next European SharePoint Conference, which is set to the first week in December 2012. This one will not be in Berlin, but more likely in Barcelona, Paris or Copenhagen (Barcelona is the one everyone cheered for, so my guess is that the other two are out of question :-)
For this conference I did two development presentations. I've done similar sessions before but this time I changed them into be even more based on best practices and experiences from the field, since we're quite a bit into the product cycle. I got good feedback on it and in some of the sessions I attended I noticed the same approach from the speakers. For you who either didn't attend my sessions or didn't have time to write down all the code samples in your notebooks - you can find the presentations on the conference web site and you can find the code samples here:
I'm planning (note planning - no promises) on doing a couple of follow up posts on specifics in the demos.
Today Microsoft released a bunch of external Search connectors for their search products such as SharePoint Server, FAST and Search Server or for clients such as Windows 7. The external search connectors are based on the OpenSearch specification, so it's quite easy to integrate with whatever product you like.
These are the new released connectors:
- Business Week
- Encyclopedia Britannica
- Google Blog Search
- Google News
- MSDN Search
- TechNet Search
- The Register
- Yahoo Images
- Yahoo News
Using the connectors in Windows 7
To use the connectors in Windows 7 all you have to do is download the OSDX file and click on it. It will bring up a dialog as below - and after that you are good to go and search using Explorer.
Adding connectors to SharePoint
To add the connector to SharePoint Server or Search Server then download the FLD file (Federated Location Definition). After that go to Central Administration and select to manage the Search service application. In the Search Service application choose Federated Locations in the menu on the left hand side. Then click on the Import Location button and use the Browse button to find the FLD file you downloaded. Once you're done click on the Done button unless you want to change the definition manually or enter any credentials.
To see the results from the federated location you need to modify your Search Center. Just edit the results page and add the Federated Results Web Part (from the Search category). Then choose to Edit the Web Part properties through the Web Part menu. In the drop down choose the federated location that you would like to use.
Save the page and try it out. It just as simple as this.
It's Friday and thought that I should share some small tips on how to make your SharePoint demonstration experience better. I assume that you have a quite powerful laptop with virtual machines running SharePoint.
I used to do my demos directly in the virtual machine, in full screen mode. This requires that I have all the necessary client components installed such as Office, SharePoint Designer, the Windows Server Desktop Experience feature enabled etc. All this of course take resources such as memory and CPU from the virtual machine. Also Internet Explorer consumes CPU cycles and if you're using Firefox in the demo you get another memory hog in your virtual machine.
A better approach is to use you local workstation as the client, In my case I have Windows 7 and VMWare running (yea, I like to promote them...) the virtual machines. This allows me to show a more realistic case when doing demos.
The first tip here is how to configure the network for the virtual machines. I normally have one AD server and one SharePoint server which are connected using a separate network, so that I can use static IP addresses. Then I have a secondary network on the SharePoint VM which is host-only with known IPs, that is I can access the VM from the client using a browser or an Office application. I also have a third network on the VM which is connected to the Internet. I only enable this third NIC if I need to access web services and such from my VM.
Then I add entries to the hosts (...\system32\drivers\etc\hosts) file with the IP numbers from the host-guest network so that I can use domain names instead of IP-numbers.
I never have the host and clients on the same domain. My laptop is connected to my company's domain and the VMs all use their own directories. To get rid of annoying authentication prompts I use the Windows Vista/Windows 7 feature to store credentials - the Credential Manager.
The Credential Manager allows you to save Windows credentials for a specific Internet or network address. Just add the name of the server, which you added to the hosts file, and then your default user username and password. Voila! You can now directly from your client/host browse to your virtual server using a good looking URL and without any authentication prompts.
Firefox, Safari and other obscure browser does not use this credential manager and I use them to log in as other users.
If you don't do this and log on to your server from the web browser you will be asked for the credentials every time you open an Office document from the server or when you open the site using SharePoint Designer.
If you use these small tips you will have a much better experience when doing demos, developing or configuring your SharePoint virtual machines.
Have a nice weekend!
I thought I should share my experience on working with SharePoint 2010 development on Windows 7. My previous posts on installing SharePoint 2007 on Vista and Windows 7 are posts that are quite popular. The downside with the “old” SharePoint version is that it was not officially supported to install it on a client machine, but SharePoint 2010 is supported for installation on Windows 7 and Windows Vista SP1 for development purposes.
There are many opinions on having SharePoint 2010 installed on your client OS. Some thinks it is despicable, but I think it is great and I’ve used local installations for years now. It’s perfect for rapid development, testing and demos. In seconds you can spin up a site and show some basic stuff for a client. Of course I use virtualization when testing my final bits etc.
Benefits and drawbacks
Having a local installation have several benefits:
- You are running on the metal – i.e. no virtualization layer
- If you don’t have more than 4GB RAM then virtualization will be really slow
- Visual Studio 2010 heavily uses WPF which requires a lot of your GPU. The virtualization layer will degrade the WPF performance
- You don’t need to spin up and shut down VMs
- Saves you a lot of disk space – one VM requires at least 20GB
Of course there are drawbacks. I would never go from developing on a local installation to production. Always test your code on a server OS!
SharePoint Foundation 2010 on Windows 7
I have installed SharePoint Foundation 2010 on my Windows 7 machine. I did not go for a full SharePoint Server installation. Most of the development can be done towards SPF and it makes a minimal impact on my client OS. But perhaps I go for a full SPS 2010 install once we have the final bits of it in June.
MSDN contains instructions on how to install SharePoint 2010 on a client OS, you need to extract the setup files and make some changes to the setup configuration file. With SQL Server Development Edition installed on my machine I installed a Server Farm, i.e. not the Standalone configuration. I also used domain accounts when I installed it, which required me to be connected to the domain during installation.
After the installation I’ve changed all SharePoint Services and SQL Services to be manually started to save some boot time. Emmanuel Bergerat has a great post on how to create Stop and Go scripts with PowerShell so that you quickly can start and stop all services. Starting these services and warming up my sites takes about 2-3 seconds on my machine equipped with an SSD (best gadget buy of 2010!)
Visual Studio 2010 RC and Team Foundation 2010 Basic
I use Visual Studio 2010 in combination with a Team Foundation Server 2010 Basic installation on my local machine. Using a local install of TFS is something I really recommend – never loose any of your local projects or files.
Visual Studio uses the GPU a lot so you will certainly have a better experience running without a virtualization layer. F5 debugging is no pain, it just takes a second to compile, package, deploy and start Internet Explorer.
If you have not tried to install SharePoint Foundation 2010 on your Windows 7 then stop reading right now and do it! It will increase your productivity immediately. The experience is awesome and together with RC of Visual Studio 2010 it’s just amazing.
The year of 2009 is about to close and it’s time for me to summarize this year, as I’ve done for the last few years (2006, 2007 and 2008). This year has been one of the most inspiring and exciting years for me in a very long time. I have been doing so much fun stuff this year.
The most significant change has been starting to work for my new employer Connecta (after nine years at basically the same employer). I needed some new challenges and I now work with some really talented people from whom I learn and share so much. As you readers know, it’s all about SharePoint for me and I have done some awesome projects this year that I’m proud of and really looking forward to some SharePoint 2010 gigs. I also finally got my MCT certification and already scheduled a number of courses for next year, looking forward to meet some aspiring SharePoint students!
Another really cool thing is that just a few weeks ago I signed a contract with Manning Publications about writing a book on SharePoint 2010, first chapter is due in a few days. This is something that I wanted to do for some time; it’s hard work but it makes me get even better – and that’s why I’m in the game. More details on the book in an upcoming post…
I continued to blog about things that I’ve found interesting – not as much as I had hoped for. I’ll try to get better next year, even though focus will be on the book for the first few months. But if I take a look at the statistics it looks like it has been a great year – thank you all new followers. The most popular post this year has been:
- Running SharePoint on Windows 7 – one of the first things I did on Windows 7
- Creating SharePoint 2010 workflows with Visio 2010 – awesomeness in a box
- SharePoint Service Pack 2 known, found and experienced problems – there are always problems
- Web Part Properties - part 2 - Editor Parts – great response on this series
- Web Part Properties - part 3 - the .webpart file – a runner up…
I’ve made a big commitment to the SharePoint community this year – and I like it, I like it a lot! It has been so fun and rewarding commenting, tweeting and meeting with the incredible SharePoint community. Can’t imagine any other community that has so much fun together! Unfortunately I missed the highlight conference in Las Vegas and the chance to listen and meet the rest of you, due to the change of employer. I hope I can make it for another year.
Here in Sweden we started the SharePointCommunity.se site to gather all SharePoint interested people and the Swedish SharePoint User Group under one umbrella and we have reached close to 500 members. The User Group here in Sweden have had some great meetings and presentations with a great number of people. Thank you again to all speakers and participants. Next year will be awesome!
I’ve been fortunate to have had a few presentations for the Swedish SharePoint User Group (in February two sessions and one in September) but the most fun presentations I’ve had was the one in Copenhagen at the first European SharePoint Saturday and the one at the Swedish SharePoint and Exchange Forum. It was awesome meeting all these cool people I only have had 140 characters discussions with. One of my first assignments with my new employer was a SharePoint 2010 seminar which we presented on a huge cinema screen in an almost full theatre – just loved it! I hope I will get more opportunities in 2010 do some more SharePoint love!
As always I fiddle around with SharePoint as much as I can and I finished version 2 of ChartPart, which you can find on Codeplex. ChartPart v 1 had about 10.000 downloads and version 2 has had close to 3.000 now (and 4.000 in beta). Together with Keith Dahlby I got the SharePoint Extensions Library out – and I’ve received very good feedback on it. Two other projects also ended up on Codeplex; Windows Live ID Authentication for SharePoint and TweetPart. I will try to get these updated to support SharePoint 2010 to 100%.
Last years predictions
Last year I did some predictions, as I’ve done now for a couple of years. I guessed that 2009 will be a year of constant betas – and man I was right. Windows 7 betas, Office 2010 betas and SharePoint 2010 betas has been making my days wonderful/peculiar this year. I predicted that Office 14 would hit the streets – now we now that we won’t get the final bits until mid 2010. I was right about Internet Explorer 8 and Windows 7. I also predicted that Microsoft would go for more open source projects and I think they very well have lived up to that – just take a look at Codeplex where Microsoft have released a great amount of awesome projects.
Predictions for 2010
What about 2010 then? We all now that Microsoft is focusing everything on Office 2010 and SharePoint 2010 and they will continue grow even stronger. But I think that during the later parts of 2010 Microsoft will have something extraordinary coming in Windows Mobile 7. They must have, otherwise it’s game over for sure for Windows Mobile.
Another thing we will see starting emerge from Redmond is a new Internet Explorer, it’s loosing market shares, so I expect some major improvements in standards compatibility and of course some new creative thinking.
Thank you and a happy new year
That’s all folks. The last year of this decade is over and it’s time to grab the bull by it’s horn and face a new one…
I still have to use Visual Studio 2003 to support some old good applications including SharePoint 2003 apps. So I have used a Windows XP virtual machine to run it, but now I can fire up Visual Studio 2003 directly from my Start menu in Windows 7. As most of you know, you can't install VS2003 on a Vista or Windows 7 machine, and I don't even want it there either.
It's also great for having Internet Explorer 6, 7 and 8 on the same machine!
Here are some pictures of the Windows XP Mode features.
Visual Studio 2003 running on Windows 7 using Windows XP mode
The published Windows XP applications in the Windows 7 start menu.
The Windows XP notification icons appear in the Windows 7 notification area. Note the Windows Update and Windows Security Alert icons. I thought this was really cool.
The day has come when Microsoft officially started to talk about the next version of Office 2010 clients and SharePoint Server 2010 (no longer Office SharePoint Server). We have since some time known that SharePoint 2010 will be supported only on a 64-bit platform, just as Exchange 2007.
The new stuff revealed yesterday (as preliminary) are that not only is 64-bit required, it will only be supported on the Windows Server 2008 64-bit platform (including R2) and it will require that you have SQL Server 2008 on a 64-bit platform. There are some other interesting facts that you should check out also in the post (and on about 1.000 other blog posts), but this post is not just about these news.
The interesting parts of this announcement is that now is the time to learn the 64-bit platform for real and especially Windows Server 2008 R2 and SQL Server 2008, not everything is the same; registry hives, file system, settings, know when to use int (Int32) or Int64 etc etc. You can start now, it's no time to wait! Make a decision to only install your new SharePoint installations on the required SharePoint 2010 hardware, make sure that you have that in your development environments and on your virtual machines. Yes, it will in many cases cost you a bit in new hardware.
I think that this is the time when 64-bit really will kill the 32-bit era.
As a bonus I can tell you one thing that I didn't know was achievable. My main laptop runs 32-bit Windows 7 and not 64-bit due to that it does not have the 64-bit driver support for the peripherals and I usually use(d) Virtual PC to virtualize my development servers. Downside with Virtual PC is that you guest machines can only be 32-bit and I don't want to have a Hyper-V laptop in 64-bit mode so I thought that I had to get me a new laptop (which is due for later). I was preparing for the worst of having a dual boot. Fortunately I did a test using VMWare Workstation today and found out that as long as you have a 64-bit capable hardware (which I have) you can host 64-bit guests on a 32-bit host OS. Did you know that, I did not! So I will spend this evening preparing my new development VM's. If you are in the same situation as me, stuck with a 32-bit OS for some time, head on over to VMWare and run the 64-bit compatibility checker and then dump Virtual PC and get VMWare Workstation.
Welcome to the 64-bit world!
Here is a tip for you Codeplex users out there.
If you are using the Visual Studio and the Team Foundation source control then you are prompted for username and password every time you open up a project. This dialog does not contain any functionality to store the username and password. If you are often opening projects and/or switching projects entering usernames and passwords can get annoying.
The Credentials Manager is found in the Control Panel, just search for it. To add a username and password all you have to do is click on Add a Windows credential and then enter the name of the Codeplex TFS server (tfsXX.codeplex.com) and then you username and password. Click Ok and then fire up your Codeplex solution in Visual Studio and you are ready to get back to coding!
Until next time...
The more I use/test Windows 7, the more I get confident that this release will get Microsoft back on track. Windows Vista introduced a lot of new and interesting stuff, but was not that polished as one could expect. Service Pack 1 of Vista did take it up one notch, but not far enough.
As the statistics nerd I am I like to know exactly what my laptop is doing, how much memory is used, which program accesses disk etc. Vista have a quite good Resource Monitor application and of course the Task Manager (even though I use Process Explorer quite a bit). Windows 7 contains some really good updates to these built-in applications.
The most hated part of the Task Manager in Vista was that you had to go trough the UAC consent procedure to see the processes from all users. But in Windows 7 (beta), the default settings of UAC are such that you only have to click the button and wait for Task Manager to start with higher privileges - no need to wait for a UAC prompt. Except for some minor changes on the Performance Tab, there are no news.
The Resource Monitor of Windows Vista was a typical Microsoft version 1 product - it started, did a little and gave a lot to long for. In Windows 7 this application has grown into a really interesting feature.
You can monitor your CPU, Disk, Memory and Network usage using tables and graphs in real time. Using the filtering option you can select a process and see exactly which resources it is using, such as memory, CPU, handles etc. For example you can check exactly which files or registry handles a process is consuming or which network addresses it is talking to.
This screenshot is filtering on the sqlserver.exe process.
The Event Viewer is the same in 7 and Vista. Only new things I noticed is that Windows 7 has a lot more Application and Service logs. I thought I check out the Diagnostics-Performance log to see some stats - but no luck. Nothing is logged here, guess this logging is omitted in the beta, and even if there was data there we are not allowed to discuss measures of Windows 7 according to the EULA.
The Performance Monitor (perfmon.exe) is the same as in Vista, at least what I have seen.
The Reliability Monitor, maybe not known to everyone, is an application that every day grades your Windows installation on a scale from 1 to 10, 10 being the perfect machine. My Vista has a top score of 8.58 and a lowest score of 1.00, it didn’t even start at 10. My score varies a lot, probably because I often install and uninstall betas. Windows 7 have a slightly updated user interface which allows you to scale your history chart and save your history data. The new Reliability Monitor also integrated the Problem Reports and Solutions application from Windows Vista, which makes the application a lot better.
There are a lot of improvements to Windows 7 in all areas, and I like it - I like it a lot. I really hope that everyone helps out on this beta period and reports any issues, so we all help out making a great new OS. I have reported a few already and will certainly report more once I start to use it for real.
Windows 7 beta was released into the wild today (or tomorrow if you’re not an MSDN subscriber) and I’m seriously considering running it on my main development machine. But to be able to do this I have one main requirement and that is that I can run SharePoint on it, just as I can on Vista. So after installing the beta bits on a Virtual PC I had to give it a try.
I installed the IIS on the Windows 7 virtual pc and then tried, without any hopes, to install WSS 3.0 the normal way. Dead end, as expected:
Then I took the Vista way and installed it using the tool created by Bamboo Solutions. The setup started fine and I choose to do a Basic install.
When the Configuration Wizard started I received this error message, looks like it did not install the SQL Server 2005 Embedded Edition during the install.
I download SQL Server 2008 Express (clicking next 1.000 times) and ran the SharePoint on Vista installation again this time using the Advanced mode (after an uninstall).
This time it worked better.
Installation took a few minutes and then I had Windows SharePoint Services 3.0 SP1 running on my Windows 7 beta installation.
Everything worked as expected! Sweet!
I have to do some more testing with some other applications, if all turns out well then I will for sure reinstall my machine (needs a reinstall anyways, and why not have fun…).
But, I have found some minor UI in Windows 7 bugs that I will report, as soon as Microsoft get their Windows 7 license key request app working.
And by the way; Windows 7 runs so smooth as a Virtual PC, using only 1 GB of RAM!
Of course this is not a supported scenario, but my daily work is way smoother using this and I have had no problems with it so far.