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-)
Posted by (JavaScript must be enabled to view this email address) on Tue 31 Mar 2009
Today I had an issue with workflows on our CRM server, specifically that none of them would run, so in order to resolve the issue I looked at the trace log and found that we were receiving the following error…
Looking at the CRM Asynchronous Service, I could see that it was running under the correct domain account (CRM Admin), however I discovered that this account needs to belong to a specific group in AD also (PrivUserGroup), so I then performed the following steps…
1. Open Active Directory and Computers (dsa.msc)
2. Find your PrivUserGroup
3. Open group and add your domain account running your CRM services
4. Run iisreset on CRM server.
5. Restart CRM Asynchronous Service.
And hey presto, workflows can then be ran on the server. 