Posted by (JavaScript must be enabled to view this email address) on Wed 22 Apr 2009
Apple - Used by creative and design conscious people as it has a much easier on the eye interface.
Microsoft - Used by companies as it gives administrative users control over the network with a much more manageable overhead.
Never the two shall meet….until today that is. Having to use undocumented calls was bad enough; having to use undocumented calls from a Microsoft.Net platform to a python/bsd Apple platform was even worse! There was no way for us to code as you would by referring to an SDK instead we had to code by exception. Using a code, compile, exception, re-code cycle which took us far longer than we wanted, or anticipated. Thankfully by using the http://www.xml-rpc.net/ XmlRPC assemblies we were able to get it working. I have to admit, this was actually a lot of fun despite it making me want to tear what little hair I have out.
The result?
A web part which allows a user to view authenticated RSS feeds from an Apple Podcast Producer server within Microsoft Office Sharepoint Server 2007 without ever having to navigate away from the site.
Rather than make the users have to enter the RSS feeds which they have access to manually, we decided to make it automatic, all the users need to do is provide their “Mac Open directory” credentials for the web part to authenticate with and the rest is done for you!
Whats more, as you probably dont have a mac server published on the wide open internet, the webpart also introduces a proxy function which will fetch content without having to publish the podcast producer computer to all and sundry.
Posted by (JavaScript must be enabled to view this email address) on Tue 07 Apr 2009
Ok…so you have a perfectly good development machine and need to develop web parts or other Microsoft SharePoint items. Microsoft have released Visual Studio extensions for WSS but we all know “you dont develop on a server”. So you are left with two options, run a virtual machine - which when you bog down with SQL, SharePoint and Visual Studio will run slower than a sloth thats fallen asleep or try to trick the visual studio extensions to work on your pc.
Its actually a lot easier than you think to get the VSe’s working on your pc than you think.
Disclaimer: this involved working on your registry. If you dont feel comfortable editing your registry walk away now and get yourself a virtual machine.
- Open Regedit as an administrator.
- navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0] - if any of these keys dont exist then you will have to create them.
- Add a string value “Sharepoint”=”Installed”
Run the VSeWSS available from http://www.microsoft.com/downloads/details.aspx?FamilyID=7BF65B28-06E2-4E87-9BAD-086E32185E68&displaylang=en
You will notice that we have now tricked the VSeWSS to thinking you have WSS installed on your pc.
Now…to make things even easier, download and install WSS deploy from http://wssdeploy.codeplex.com/ which will allow you to code and deploy more easily from your desktop without having to play around copying files, installing to GAC, carry out IISResets etc.
Happy Coding.
Posted by (JavaScript must be enabled to view this email address) on Mon 06 Apr 2009
Today I was creating a development environment to mirror one of our client’s production MOSS installations and had to update our Development version of SharePoint to match the production version.
I found that the current SharePoint hotfixes from Microsoft don’t come via the update site but a useful blog pointed me to the right place:
Each hotfix for MOSS has to be registered for and Microsoft send a download link to your email with a password - the good news is that the mail is sent pretty much instantaneously :0-)
Anyway, I got to chatting with my colleague and we decided it would be a good idea to post a whole load of useful download links for installations and here they are:
Frameworks
1.1: http://Framework 1.1
2.0: http://Framework 2.0
3.0: http://Framework 3.0
3.5: http://Framework 3.5
You’ll also need the service packs:
Service Packs
1.1: http://.Net Framework 1.1 Service Pack
2.0: http://.Net Framework 2.0 Service Pack
3.0: http://.Net Framework 3.0 Service Pack
Enjoy :0-)
Page 1 of 1 pages