Archive

Archive for the ‘Uncategorized’ Category

Anker ToughShell & GlassGaurd For iPhone6s Black Review

December 31, 2015 Leave a comment

Anker recent addition to its range of products is Anker ToughShell & GlassGaurd. It is a combo of a Screen Protector and Case. You get whole bunch of tools to install the Screen Protector, installation of Shell is pretty easy. Just you push the phone inside to the case. Please go through their manual for accurate installation steps.

IMG_7867.JPG

Feel : Touch was awesome, Matte at the back & edges are guarded with a flexible material that absorbs shock during the drops. You will see all the Four edges has extra material to help protect the phone.

IMG_7861.JPG

Size : Size was perfectly crafted to fit iPhone 6s. I was able to add the case with no effort. It just slides in. Also it did not make phone bulkier. Hardly couple of millimeters around each side.(Measurements are not very accurate but use this as a range).

 

Material :  Super Strong, I feel I can trust this will guard you phone against any fall. Very important characteristic of a case. You will see all the Four edges has extra material to help protect the phone.

Weight: I hardly notice any difference in phones weight after adding this case.

Bezel : This is very important for me. I used to keep the phone facing down during my meetings.I used to do it very carefully so It wont cause any damaged to the screen. Having a raised Bezel helps with this. Check out my Picture where I kept a pencil. You could see Jenga doesn’t touch the screen.

IMG_1944

Ports :This case has Port opening for Power connector, Headphone Jack & Camera. Cut is so perfect. Lightning connector & head phone Jack fits in so easily. What I love about this case is it has a wider port so Anker’s Lightning cable also could fit. If you have used Anker’s cable you will know their lightning port is bigger to Apple’s. Camera has raised edge too, it is suppose to help you with glare. Have not really tested it.

Price :  For this price you are getting a combo. Totally cool.

Buttons are covered, you may have to use little extra force to add volume & lock because of material .You will get used to it after a day or two. Also Silent button on left is little hard to reach. But you get used to it.

Quick Video about the Product.

This review is based on a sample offered to me for test and evaluation, and I am offering a review that is fair and honest.

Advertisements
Categories: Uncategorized

Anker PowerCore+ 26800 is a PowerHouse

November 24, 2015 Leave a comment

This is my experience with Anker PowerCore+ 26800  a Portable Charger from Anker (Company Founded by Googlers, they have a stack of Amazing products) I am proud owner of 4 such products, all my cables and Charging solutions are Anker based.26800 is not a random number but 26800mAh that is provided by  this device.

Anker PowerCore+ 26800  is not one product but a Combo. Combo of Anker Quick Charge 2.0 18W USB Turbo USB Wall Charger and 26800mAh External Battery.

I already own Anker Astro E4 13000mAh Classic Portable Charger  for some time now. Which I really love and is a constant companion for me in vacations. Best part of this is multiple rounds of charge which is very helpful. This version PowerCore+ 26800 is a Power House. It is quite heavy @ 590 gms or 20.8 oz. As per the Product Description it is supposed to Charge iPhone 6 ten times, well worth the weight. I have not tested the number of charges yet. Will update the review once I test it.

Feel: Outer Cover is made of aluminum with Matte Finish. Edges are Laser cut looks very neat. LED indicator is arranged circularly. So Black Matte finish + Circular LED is a killer look.

Number of Charges: PowerCore+ 26800 is the world’s highest capacity portable charger with Quick Charge 2.0 technology. It charges the iPhone 6 ten times, the Galaxy S6 over seven times or the MacBook (2015) five times. I will test these specifications and let you know. Also you will charge PowerCore+ to full charge in 9 Hours with charged provided.

Power IQ Technology: It is an Anker’s technology that detects and adapts to your device’s unique Charging requirement. So it charges your device in a fastest and safest way possible.

Quick Charge Technology: In simple words Quick Charge 2.0 is an Innovative Fast Charge Technology from Company called Qualcomm who manufactures Snapdragon™ processors. Quick Charge technology charges your device faster compared to conventional charging adapters. As per QualComm official web page it takes about 30 mins for a device to reach from 0 to 60%. Qualcomm certificates these adapter, Green Color Logo in both PowerCore device & Charger means it is officially certified.  If you want know more about the Quick Charge read last section of my review.

IMG_7720

Three in one: You are getting a cock tail of technologies. Anker’s PowerIQ Technology in all Ports + Qualcomm’s Quick Charge 2.0 in One Port & Quick Charge 2.0 Charger that can be used with Wall adapter.

  1. Worlds Highest Capacity Portable Charger.
  2. Portable Charger with QuickCharge 2.0 Port.
  3. Wall Charger with QuickCharge 2.0 Enabled.

Anker’s Magic: Best feature is Qualcomm’s Quick Charge 2.0 in a Power bank. Out of 3 ports one with a Green Logo is Quick Charge Enabled. Based on the Qualcomm website Anker is one of the two providers providing this option. Other one doesn’t seems to be a promising provider. That makes Anker as one of the exclusive provider. Ability to charge on the move + charge faster is awesome combination. Enabling Quick Charge 2.0 in a Power Bank is a brilliant idea I would say. You can always manage to find a Quick Charge 2.0 enabled Adapter when you are at home or at work. Having a Quick Charge 2.0 enabled power bank which lets you Charge your device on the move is the most convenient thing and Highlight of PowerCore+.

Ease of Use: To begin charge connect your device and click on the power wheel. PowerCore+ automatically switches off once the device is fully charged or device is disconnected. Quick Charge adapter lights turn green when charging and Blue with it is just plugged and not connected to Power Core+.

Note to Samsung / Snapdragon Processor based device Owners: You gain most advantage out of this because your device can be charged in the fastest time. Make sure you use the Quick Charge 2.0 Enabled port and Company provided / Anker’s Cable to charge the device. You can also Charge your device directly connecting to Quick Charge 2.0 enabled Adapter.

Note to Apple Users: Unfortunately Apple’s devices are not powered by Snapdragon processors so like me you won’t be able to utilize Quick Charge 2.0. This does not mean you cannot use the device. You can still charge your device and utilize PowerIQ this helps you charge the device much faster than other cables.

Quick Charge Technology EXPLAINED:

Charging involves three parts.

  1. Your Device: Typically smartphone or tablet. (This needs to have Snapdragon processor to utilize Quick Charge Technology).
  2. Power Source (Power bank/ Wall Adapter): This is typically your Adapter or a power bank. (Qualcomm certified).
  3. Cable: Cable that connects Power source & device.

IMG_7723

To fully utilize Quick Charge 2.0 technology your device should have a Snapdragon processor (list of current devices with Snapdragon processor). Quick charge 2.0 enabled Adapter. If you don’t have one of these then with PowerCore you will still gain PowerIQ that help to charge faster. As per QualComm website by no means it affects life-cycle of battery or your device.

Here is a 90 Second Video

This review is based on a sample offered to me for test and evaluation, and I am offering a review that is fair and honest.

SharePoint 2013 business data web parts missing

March 26, 2015 Leave a comment

Like you I was puzzled because Business Data Web Part was Missing in our SharePoint 2013 Farm. We did all that is required for these web parts to show.

  1. Our Farm License is Enterprise License
  2. SharePoint Server Enterprise Site Collection features” is activated at the Site Collection level
  3. We even tried activating Enterprise Site Collection Feature from Central Administration Central Administration > Operation > Upgrade and Migration > Enable Enterprise Features.
  4. Though we got a Category “Business Data” Only Indicator web part was listed there.
  5. We again tried to activate BizAppsSiteTemplate   Enable-SPFeature “4248E21F-A816-4c88-8CAB-79D82201DA7B” -URL http://<your-site&gt;
  6. Still no luck.

After activating SharePoint Server Enterprise Site Collection Features , I could see .webpart and dwp files in Web Part Gallery.

So I guessed the issue is no about the missing Feature but some Sort of security filtering. A quick look at the WebPartAdder class in reflector confirmed my theory (Web Part list is rendered based on Licencing), Though we have enterprise licencing, I remember we added a new set of Licencing to our Farm for our Office Web Apps Installation.

So I turned to powershell and ran this command, which listed all Licenses we have

PS C:\Users> Get-SPUserLicense

License
——-
Enterprise
Standard
Project
OfficeWebAppsEdit

Then when I ran Get-SPUserLicenseMapping, I figured OfficeWebAppsEdit was set to the Farm for Domain Users, I guess this happened when we were configuring Office Web Apps. Sp I tried adding Enterprise License to all Domain Users using following command. Which fixed the issues.

$a = New-SPUserLicensing -SecurityGroup “Domain Users” -license Enterprise

Add-SPUserLicenseMapping -mapping $a

Hope this helps someone.

Categories: Uncategorized

New Release

February 18, 2013 Leave a comment

Yes, on eighteenth October of two thousand nine, my wife and me blessed with a baby girl. We had named her Diya. Last two weeks was very though as they both had few complication after birth, and by god grace it all went well now. So not to mention now I have an added responsibility.Definitely it is a different feeling to be a dad. Here is how she looks.

diya

Diya I know some day you will read this Post and I wanted to let you know that as always I  love you so much.

Categories: Uncategorized

THE LAUNCH !!!

February 15, 2013 Leave a comment

It all started three+ years back a point of time when I was nurtured enough to find the information I wanted through Internet search, be it technical or general some way or the other I land up in a blog. Specifically that time SharePoint 2007 was in beta and there was very limited information over internet on the subject, As I saw most of the blog from the SharePoint Product team I was in a perception that blogs are meant to them, Later which I came to know about Blogspot which allows you to have your personal blog, I started one, but as there were so much to learn in SharePoint and have to spent all of my time in R & D to get the things working for my First ever Web CMS site based on SharePoint 2007, which was almost ready when the SharePoint RTM came out. I didn’t find time to update my blog. Another thing I hate about blog is the Editor I didn’t like the editor provided by the Blogspot as it is so small and was not able to type the content with ease. I didn’t know about the tools (Word 2007 / Live writer ) that will help you to do that with ease. Later I got inspired with WordPress for the rich set of tool it provide and the full screen functionality, which is when I started this.I was kind of used to update the blog at least twice a month.

As I started more blogging, I saw some pain points.Wordpress is pretty good at what they do and one limitation I was so concerned with the WordPress/Blogspot is that I don’t have more control on the template and the layout.I wanted to have more control on the website layout. I wanted to have more space for my content and it should be presentable to the user who is reading it. Soon I decided to have a blog for my own. I wanted it to be flexible enough I ran through couple of options, upgrade my WordPress account, but it wont allow me to change the layout even If I upgrade, also WordPress is running on PHP, I wanted my blog to running in something from Microsoft stack, ASP.NET. I was impressed by the theme used by Reza but then it was based on PHP WordPress. I finally know what my blog should look like but I didn’t know how to search for that template. Later I came across Tim site and it was running on ASP.NET. I mailed him and got the information that he uses Subtext Project as the blog engine. I then found that the theme used by Reza was inove from WordPress. Last weekend I spent whole time to get the theme applied in the Subtext. Next item was to chose a good provider and buy a host name. Lot of options, I was looking at everydns for getting a host name for free and net4 to host my site, but everydns didn’t work for some reason and net4 site is itself slow, It didn’t look good. Finally I got all under ZnetIndia, customer support is so cool and got complete thing wired with in 1 Hour. I had to setup the subtext with IIS 7 as you need to configure the App Pool to run in  the Integrated Classic more else you will end up in httpModule issue.

And after all this here is what it looks like. Thanks for reading it through so far and I would like to have a comment if you have one on my blog. I will be happy to share this site theme, if you want  just leave me a comment. Also I have planned to concentrate only on SharePoint SharePoint SharePoint and bit of .NET & ASP.NET.

Categories: Uncategorized

SPPropertyBag

September 23, 2008 1 comment

SPWeb object of SharePoint exposes a Field called Properties which is of type SPPropertyBag a sub class of StringDictionary. It allows you to store Key value String Data within a web

Below are some quick points that will help you in using it.

  • As Mentioned Before it is a StringDictionary, which can only store String values.
  • You need to call the Update() method of the SPWeb.Properties.Update() to persist the value.
  • Same applies while you are removing a value from it.
  • Below code gives you a quick start.
  • If you want to manage this through UI. Refer this link. It’s a fantastic option you will love.

 

using (SPSite oSite = new
SPSite(http://mysite&#8221;))

{


using (SPWeb oWeb = oSite.RootWeb)

{


//Add a Item to Bag

oWeb.Properties.Add(“SPPropertyBag”,“I can Store a StringValue Here”);


//Be sure to Call the Update Method on Properties


//If you miss this your value wont get Presisted for the Next Run

oWeb.Properties.Update();

 


// To Reterive the Value


String sMyItem = oWeb.Properties[“SPPropertyBag”];

 


//Remove the Value


//Be sure to Call the Update Method on Properties


//If you miss this your value wont get Presisted for the Next Run

oWeb.Properties.Remove(“SPPropertyBag”);

oWeb.Properties.Update();

             }

         }

    

    

Categories: Uncategorized

Deploying InfoPath forms using Features – the Right Way

September 19, 2008 2 comments

Same version of the Post is avaliable in this Link. Formatting Adjusted.

A week back couple of my friends was asking is there a proper way to deploy the InfoPath forms to the server, Way other than File -> Publish – > SharePoint server with or without forms server. I did a quick search and was not lucky, came to a lackadaisical conclusion that there is no other way. But whenever I deploy workflows with InfoPath form I see a new solution that adds itself to the Solution Store. By this I know for sure there is some other way to deploy InfoPath forms. First thing want I wanted was to get the Solution out of SharePoint and see what’s there inside, Again for this there is a tool through which you can do it [I lost the url from where I got it] or hardly 10 lines of code is all what you need.

To my surprise there is indeed a way to do it, well let’s see how. What I got out of that solution is a feature, what’s in it [Image speaks louder than words, image with comments even louder 😉 ]

Feature.xml

#########All usual Stuff ###########

<?xml
version=1.0
encoding=utf-8
standalone=yes?>

<Feature
Id=8ad77502-3602-6e81-c4de-8c7f674c4466

Title=IPDeplotyment

Description=$Resources:ipfscore,XsnFeatureDescription;

Version=1.0.0.0

Scope=Site

DefaultResourceFile=ipfscore

#########Here is the hero who does what we need ###########

ReceiverClass=Microsoft.Office.InfoPath.Server.Administration.XsnFeatureReceiver

ReceiverAssembly=Microsoft.Office.InfoPath.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c

xmlns=http://schemas.microsoft.com/sharepoint/>

<ElementManifests>

<ElementManifest
Location=Elements.xml />

<!– Name of the IP Form

Note:Actual workflow generated feature has a different name–>

<ElementFile
Location=solution.xsn />

</ElementManifests>

<Properties>

<!– The Name of the Feature – Infact after you have deployed the WF to sharepoint there will be a

feature by this name that gets added –>

<Property
Key=FeatureName
Value=FT-01-8ad77502-3602-6e81-c4de-8c7f674c4466 />

<!– This is going to the File name with which you have Publised from IP Client / Added to the Workflow.xml

if you are going to deploy the IP forms that are not coupled with the WF you can safely ignore the below tag–>

<Property
Key=OriginalFileName
Value=IPDeplotyment.xsn />

</Properties>

<ActivationDependencies>

<!– Just to make sure that you have Enterprise feature turned on–>

<ActivationDependency
FeatureId=C88C4FF1-DBF5-4649-AD9F-C6C426EBCBF5 />

</ActivationDependencies>

</Feature>

Element.xml

################### You are Right its again another File Provisioning in to SharePoint Lib #####################

<?xml
version=1.0
encoding=utf-8
standalone=yes?>

<Elements
xmlns=http://schemas.microsoft.com/sharepoint/>

############# Be sure to put the location as FormServerTemplates############

<Module
Name=XSN
Url=FormServerTemplates
RootWebOnly=TRUE>

<File
Url=solution.xsn
Name=IPDeplotyment.xsn
Type=GhostableInLibrary />

</Module>

</Elements>

Well here is the stripped out version of the above file

<?xml
version=1.0
encoding=utf-8
standalone=yes?>

<Feature
Id=8ad77502-3602-6e81-c4de-8c7f674c4466

Title=IPDeplotyment

Description=$Resources:ipfscore,XsnFeatureDescription;

Version=1.0.0.0

Scope=Site

DefaultResourceFile=ipfscore

ReceiverClass=Microsoft.Office.InfoPath.Server.Administration.XsnFeatureReceiver

ReceiverAssembly=Microsoft.Office.InfoPath.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c

xmlns=http://schemas.microsoft.com/sharepoint/>

<ElementManifests>

<ElementManifest
Location=Elements.xml />

<ElementFile
Location=IPDeplotyment.xsn />

</ElementManifests>

<Properties>

<Property
Key=FeatureName
Value=FirstIPFeatureWayDeployment />

</Properties>

<ActivationDependencies>

<ActivationDependency
FeatureId=C88C4FF1-DBF5-4649-AD9F-C6C426EBCBF5 />

</ActivationDependencies>

</Feature>

Element.xml

<?xml
version=1.0
encoding=utf-8
standalone=yes?>

<Elements
xmlns=http://schemas.microsoft.com/sharepoint/>

<Module
Name=XSN
Url=FormServerTemplates
RootWebOnly=TRUE>

<File
Url= IPDeplotyment.xsn
Name=IPDeplotyment.xsn
Type=GhostableInLibrary />

</Module>

</Elements>

Steps in Short:

  • Develop your IP form.
  • Publish it to the network location as how you do to upload to the Central Administration Upload Form Templates.
  • Create one Feature.xml, Element.xml as defined in the article [Sorry how workflow does ;)].
  • Put in the IP form and create a feature out of it.
  • Its all.

Categories: Uncategorized