Caml Builder 4.0.0.0
I have notice the beautiful page u2u.be doen’t seem to provide this software to query Sharepoint 2007 and Sharepoint 2010 lists. The whole tool is a piece or art, because allows you to create CAML queries plus the real content of a particular list.
Because I keep the latest copy of this software, I decided to share it with, until u2u.be decide (if they do) re-detribute this tool again.
Click here to download CamlBuilderSetupv4.0.0.0.zip
Caml Designer 2010
This tool is new in the market, and it is a wrapper of the famous CAML Builder, It has better functionality an a better user interface.
Click here to download CamlDesigner.zip
Oficial website: http://www.biwug.be/
Enjoy!
Showing posts with label sharepoint 2007. Show all posts
Showing posts with label sharepoint 2007. Show all posts
Thursday, 18 April 2013
Monday, 7 March 2011
How to enable and disable a Feature with PowerShell
In a previous post I showed you how to uninstall a feature with Powershell. That command is going to be quite useful when you have to do some development with workflows and event receivers. Event receivers are quite stable but workflows are a different subject. Even when they are fired, sometimes they don't work in the way you expect.
Event receivers always work like you expect, just because they are a bunch of events already defined, when workflows mix 3.0 .NET WF with 3.5 .NET WF with native sharepoint 2010 modules.
The following commands will save you plenty of work, and I recommend to use them all the time, to be sure that what you are deploying is the right version of your Workflow or Event Receiver.
To enable a feature just type the following command in Powershell (replace nameofyourfeature with the name of the featurae you want to enable. Type the url where your feature lives):
Get-SPFeature | Where-Object {$_.DisplayName -eq 'nameofyourfeature '} | Enable-SPFeature -Identity {$_.Id} -Url http://myserver/sites/docs
To disable the feature just type the following command in Powershell (replace nameofyourfeature with the name of the featurae you want to enable. Type the url where your feature lives):
Get-SPFeature | Where-Object {$_.DisplayName -eq 'nameofyourfeature '} | Disable-SPFeature -Identity {$_.Id} -Url http://myserver/sites/docs
Conclusion: Powershell can beat any user interface in Sharepoint 2010. With Powershell we will be able to reach any issue we have with features. The Web UI still quite weak comparing with the power of this shell.
Event receivers always work like you expect, just because they are a bunch of events already defined, when workflows mix 3.0 .NET WF with 3.5 .NET WF with native sharepoint 2010 modules.
The following commands will save you plenty of work, and I recommend to use them all the time, to be sure that what you are deploying is the right version of your Workflow or Event Receiver.
To enable a feature just type the following command in Powershell (replace nameofyourfeature with the name of the featurae you want to enable. Type the url where your feature lives):
Get-SPFeature | Where-Object {$_.DisplayName -eq 'nameofyourfeature '} | Enable-SPFeature -Identity {$_.Id} -Url http://myserver/sites/docs
To disable the feature just type the following command in Powershell (replace nameofyourfeature with the name of the featurae you want to enable. Type the url where your feature lives):
Get-SPFeature | Where-Object {$_.DisplayName -eq 'nameofyourfeature '} | Disable-SPFeature -Identity {$_.Id} -Url http://myserver/sites/docs
Conclusion: Powershell can beat any user interface in Sharepoint 2010. With Powershell we will be able to reach any issue we have with features. The Web UI still quite weak comparing with the power of this shell.
Tuesday, 1 December 2009
Faulting application w3wp.exe
I have recently created a webservice in .NET 3.5. This web service interrogates native Sharepoint 2007 DLLs and basically , the duty of this web service is to provide extra funcionality for Sharepoint 2007. One of the web methods of this web service is called OverWriteFile(...), and basically overwrites files in SharePoint 2007. Everything was working fine until I start passing long files, at that point IIS went down and the "Event Viewer" in the "Application Log" showed the following message:
.NET Runtime 2.0 Error Reporting
Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e, faulting module kernel32.dll, version 5.2.3790.4480, stamp 49c51f0a, debug? 0, fault address 0x0000bef7.
At the begining I did not know if it was a Sharepint issue, Sql Server (MOSS talks with SQL Server all the time), my web service or IIS. After investigating all the probabilities I realized it was a IIS bug. I checked on Google and I saw two fixes but they did not work:
http://support.microsoft.com/kb/918041/en-us
http://blogs.msdn.com/david.wang/archive/2006/03/16/Have-you-seen-a-WebEngine-dll-crash-with-ASPNet-20.aspx#552794
I finally decided to debug the process w3wp.exe to see where the problem was and reach the bottom of the problem. My surprise came when after the installation of the "debug diagnotics tool" fixed the problem. This little application actually takes full control of IIS avoiding this bug.
So to fix the above problem just go to the Microsoft Link and follow the steps for the "debug diagnotics tool" installation.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;919789
Good luck with the Microsoft bug!
.NET Runtime 2.0 Error Reporting
Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e, faulting module kernel32.dll, version 5.2.3790.4480, stamp 49c51f0a, debug? 0, fault address 0x0000bef7.
At the begining I did not know if it was a Sharepint issue, Sql Server (MOSS talks with SQL Server all the time), my web service or IIS. After investigating all the probabilities I realized it was a IIS bug. I checked on Google and I saw two fixes but they did not work:
http://support.microsoft.com/kb/918041/en-us
http://blogs.msdn.com/david.wang/archive/2006/03/16/Have-you-seen-a-WebEngine-dll-crash-with-ASPNet-20.aspx#552794
I finally decided to debug the process w3wp.exe to see where the problem was and reach the bottom of the problem. My surprise came when after the installation of the "debug diagnotics tool" fixed the problem. This little application actually takes full control of IIS avoiding this bug.
So to fix the above problem just go to the Microsoft Link and follow the steps for the "debug diagnotics tool" installation.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;919789
Good luck with the Microsoft bug!
Subscribe to:
Posts (Atom)