There was a requirement to have a search text box and a button in landing page and show OOB search result from a single document library.
After doing some analysis on OOB search the following is the code which we came up with.
The technique is use the query string with query items “k=query”, “cs=This List” & “u=list’s absolute url”. Underlined items are the items which change dynamically.
Recently I was planning to checkout SharePoint 2013 and do a test drive. So to get a virtual machine from our internal cloud hosting I was doing analysis on the hardware requirements for SharePoint 2013 preview and the following came as a shock !
24GB RAM for 2013 preview development server as compared to 4GB for 2010 version.
That’s 6 times of 2010 RAM requirements. I am hoping that the requirements will come down once the SharePoint 2013 goes to RTM.
Hardware requirements—web servers, application servers, and single server installations
Installation Scenario
Deployment type and scale
RAM
Processor
Hard disk space
Single server with a built-in database or single server that uses SQL Server
Development or evaluation installation of SharePoint Foundation 2013 Preview
8 GB
64-bit, 4 cores
80 GB for system drive
Single server with a built-in database or single server that uses SQL Server
Development or evaluation installation of SharePoint Server 2013 Preview
24 GB
64-bit, 4 cores
80 GB for system drive
Web server or application server in a three-tier farm
Pilot, user acceptance test, or production deployment of SharePoint Server 2013 Preview
12 GB
64-bit, 4 cores
80 GB for system drive
Hardware requirements—database servers
Component
Minimum requirement
Processor
64-bit, 4 cores for small deployments
64-bit, 8 cores for medium deployments
RAM
8 GB for small deployments
16 GB for medium deployments
For large deployments, see the “Estimate memory requirements” section in Storage and SQL Server capacity planning and configuration (SharePoint Server 2010).
These values are larger than those recommended as the minimum values for SQL Server because of the distribution of data that is required for a SharePoint 2013 Preview environment. For more information about SQL Server system requirements, see Hardware and Software Requirements for Installing SQL Server 2008 R2.
Hard disk
80 GB for system drive
Hard disk space depends on how much content that you have in your deployment. For information about how to estimate the amount of content and other databases for your deployment, see Storage and SQL Server capacity planning and configuration (SharePoint Server 2010).
For one of the SharePoint implementation I was suppose to call the SharePoint 2010 ASMX service within a Custom WCF services hosted in a different server than the SharePoint 2010 host.
So as usual I added the service reference (PS: The add web reference is not available in WCF solution). Then I was getting the following error whenever the ASMX method was hit in the WCF.
"The HTTP request is unauthorized with client authentication scheme ‘Ntlm’. The authentication header received from the server was ‘NTLM’"
After breaking my head for few minutes, decided to hit the Google and got the solution in the source mentioned at the end.
So finally the code which worked is listed below.
EndpointAddress endpoint = new EndpointAddress(new Uri("http://SharePointserver/_vti_bin/InvoiceServices.svc"));
BasicHttpBinding httpBinding = new BasicHttpBinding();
httpBinding.Security.Mode = BasicHttpSecurityMode.TransportCredentialOnly;
httpBinding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Ntlm;
InvoiceServicesClient myClient = new InvoiceServicesClient(httpBinding, endpoint);
myClient.ClientCredentials.Windows.AllowedImpersonationLevel = System.Security.Principal.TokenImpersonationLevel.Impersonation;
//Invoke the service method here…
Mobile devices context have now changed a lot. Being from simple communication device to full blow Personal Information Manager.
Here in the organization I work for, usage of personal mobiles for official communications are not allowed. Primary reason being data security.
So I use my mobile for staying in touch with my friends, keep track of news and events, manage my personal and official task list etc.
I am going to start of a series of post reviewing the apps I use in mobile and how I use them.
Starting off … My Mobile Desktop
Home Screen
I keep tab at 2 things here.
My team’s time across 3 time zones. This is the default dual clock widget which comes with SGSII.
My messenger status. I use IM+ Pro for messenger and stay connected in Microsoft Live, GTalk, Yahoo & Skype.
Dual Battery Widget helps me keep tab on battery level. Till this date this is one of the best looking battery widgets.
Traffic Counter help to monitor the data usage.
Weather & Entertainment Screen
Keeping updated on weather sometime helps to plan on commuting. I use Accuweather widget which comes with SGSII.
Audio FX widget. Helps to change the audio quality with apps like DI FM. But this one doesn’t work with FM Radio App which comes with SGSII.
PowerAMP 4×2 widget.
Birthday Calendar
Agenda Widget coupled with Gmail Calendar which is synced with FaceBook’s Birthday Events iCal URL.
To Do
I keep track of my to do list with the help of Producteev free account service. Till now one of the best online task management service which has apps for all the platforms.
Switches
Finally the switches screen where I utilize Tasker app’s widget to control various tasks.
Mostly I try to keep my widgets as low as possible and try to use dark wallpapers to conserve CPU usage, screen brightness and in turn save battery. On a whole the combination of screens help me keep tabs on information.
The most useful are the Producteev and IM+ Widgets.
Producteev helps to have glance at non completed items and those due today & IM+ Pro helps me keep the count of non responded messages and online status.
In addition to above you can see 2 non-standard SGSII icons on status bar related to following apps.
Found out that the javascript with c# code needs to be out of the tag which has runat=”server”. After checking the code I re-wrote the code into 2 pieces
While I was modifying SharePoint’s master page to put an inline code, I was constantly redirected to SharePoint Error Page “An unexpected error has occurred”.
After spending nearly an hour to get a clue from EventLog and other sources, I found out that by adding the following config codes to web.config of the web application where the site collection resides, we can see the ASP.NET error page with detailed information.