Since my wife's phone died, had to get a new phone and I used this opportunity to try out a Windows Phone 7 (Samsung Omnia) so that I could try my hand at developing some apps.
The last time I tried out a Windows Phone or rather Windows Mobile was a few years ago and deploying an app was a breeze. So, started off with the same expectation.
Did some reading and figured out that I needed the Windows Phone SDK, Zune (to connect the phone to Windows).
Connected the phone and Zune started up but realised that my live id had limitations and got the following error "The location setting for your Windows Live ID doesn't match the setting for your computer (United States)." Changing regional settings and locale did not help. There is a codeplex tool to fix this - http://localizune.codeplex.com/.
Now, decided to test some apps and realized you actually need to pay $99 even if you just want to test out some apps on your phone! So, gone are the days when you could actually write code and hit F5 to deploy it to your mobile. Once you have registed with App Hub (by paying $99), you need to register the phone.
Launched the Windows Phone Developer Registration tool and get another error message "Unable to connect to phone. Please check that the Zune software is running and that Zune's sync partnership with your phone has been established". After spending almost 2 hours did the customary reinstall (of Zune) and was able to register the phone.
Now the phone is ready to accept custom applications!
Saturday, February 25, 2012
Thursday, June 16, 2011
Sharing phone's internet connection with laptop
This one is probably easy but it was tricky for me since I had to connect to the internet using my phone's GPRS connection as my broadband modem had gone bust. I say tricky because I had no access to the internet and hence no search engines and the browser on the phone is not friendly. This explanation is for a Windows 6.1 Mobile and Windows 7 Pro combination
So, here we go
Pair the phone with the laptop / desktop
On the phone click on start --> programs --> Internet Sharing.
Then choose Bluetooth Pan for the PC Connection. Choose the network connection which connects your phone to the Internet and click Connect
Now click on the bluetooth icon on the status bar and choose Join a Personal Area Network.
Highlight the Phone on the bluetooth devices list. From the top menu choose "Connect Using --> Access Point".
Happy Browsing!
So, here we go
Pair the phone with the laptop / desktop
On the phone click on start --> programs --> Internet Sharing.
Then choose Bluetooth Pan for the PC Connection. Choose the network connection which connects your phone to the Internet and click Connect
Now click on the bluetooth icon on the status bar and choose Join a Personal Area Network.
Highlight the Phone on the bluetooth devices list. From the top menu choose "Connect Using --> Access Point".
Happy Browsing!
Audience targeting vs Permissions in SharePoint
Can audience targeting be used for permissions i.e., control what the users sees? I have seen most folks get this wrong. Audience targeting cannot be used for permissions and here is the reason.
Audience target is used to target content to a particular audience but it does not prevent the user from navigating to the content.
Audience target can be used to customize the content on the page based on the audience profile but if the user knows the path to the content they can still navigate to it and view it unless it is controlled with permissions
Audience target is used to target content to a particular audience but it does not prevent the user from navigating to the content.
Audience target can be used to customize the content on the page based on the audience profile but if the user knows the path to the content they can still navigate to it and view it unless it is controlled with permissions
Sunday, November 7, 2010
SharePoint setup on a cross-domain one way trust environment
Its been quite a while since I have written something technical. Either too busy or did not find anything challenging enough. Well, here is one that was fairly challening considering I am not a SharePoint Administrator.
Requirement: The client had two domains - A and B. There is a one way trust between A and B such that B understands everything in A. The SharePoint instance is on B i.e., Users of A can logon to B but not vice versa.
The following solutions were possible -
1) Setup claims authentication using ADFS. Probably the best approach but not sure how the credentials in B would get validated since the trust is from A to B.
2) Imports users of A into B and keep them in sync using Microsoft ForeFront Identity Manager (FIM). This would have cost implications as FIM is not free.
3) Use AppFabric Access Control. This is relatively new and not played around with it yet.
4) Have NTLM authorization right through by using the ForeFront Identity Manager service available out of the box. This is not the best approach because of possible double hop issues later on but we decided to go ahead with this as currently authorization at the DB level was not a requirement and service accounts could be used to authentication into the DB.
Having decided on Approach 4 we decided to try this out on a VM setup. We created 2 domains A and B, created the one way trust and ensured that once user from A was added to B, he was able to logon and users of B should be able to logon to A.
Once this was done, we had to install the ForeFront Identity Manager service and then run the Profiler Service in SharePoint. This imported the users from A into B. We then added a user in A on one of the sites in B. So, things looked hunky dory until this point. But when we tried to logon to the site with the credentials of the User in A a blank page was displayed and the event logged had a security exception - Bad username/password. After a bit of thought, it was clear that the credentials were not getting validated. Reason - the service account was not able to validate the username/password from domain A! We resolved the issue by using the credentials of User in A for the service account of the Profiler service in SharePoint. Possibly not the best approach but since we have SharePoint on Domain B, I guess there is no other way out!
Comments/suggestions welcome and appreciated.
Requirement: The client had two domains - A and B. There is a one way trust between A and B such that B understands everything in A. The SharePoint instance is on B i.e., Users of A can logon to B but not vice versa.
The following solutions were possible -
1) Setup claims authentication using ADFS. Probably the best approach but not sure how the credentials in B would get validated since the trust is from A to B.
2) Imports users of A into B and keep them in sync using Microsoft ForeFront Identity Manager (FIM). This would have cost implications as FIM is not free.
3) Use AppFabric Access Control. This is relatively new and not played around with it yet.
4) Have NTLM authorization right through by using the ForeFront Identity Manager service available out of the box. This is not the best approach because of possible double hop issues later on but we decided to go ahead with this as currently authorization at the DB level was not a requirement and service accounts could be used to authentication into the DB.
Having decided on Approach 4 we decided to try this out on a VM setup. We created 2 domains A and B, created the one way trust and ensured that once user from A was added to B, he was able to logon and users of B should be able to logon to A.
Once this was done, we had to install the ForeFront Identity Manager service and then run the Profiler Service in SharePoint. This imported the users from A into B. We then added a user in A on one of the sites in B. So, things looked hunky dory until this point. But when we tried to logon to the site with the credentials of the User in A a blank page was displayed and the event logged had a security exception - Bad username/password. After a bit of thought, it was clear that the credentials were not getting validated. Reason - the service account was not able to validate the username/password from domain A! We resolved the issue by using the credentials of User in A for the service account of the Profiler service in SharePoint. Possibly not the best approach but since we have SharePoint on Domain B, I guess there is no other way out!
Comments/suggestions welcome and appreciated.
Wednesday, May 26, 2010
Cycling to work - a start!
This is somethng I had been contemplating for a quite sometime now but had been discouraged by well wishers as I had to commute almost 20km one way to work and with a laptop to carry it seemed impractical. Now with just about 5km to get to work I decided to give it a shot.
First thing was to get a bicycle so did a lot of googling and finally decided to visit the bicycle store and decide. Me being me it was quite likely that I would use the bicycle for a few days and then leave it to rust so decided to take it easy and bought a entry level 21 gear bicycle (Hero Octane). The reviews for this were not great but even then after sitting on it I thought it was comfortable. Bought the bicycle and it was pouring but decided to ride it back from commercial street. With the enthusiasm of a new bicycle managed to get him with a little bit of sweat. I did not stop pedalling which was quite funny as you will realise later in the post
Day 1: Left home nice and early and it seemed like hard work to get to office. I was sweating even though I wanted to take it easy. On the way back home climbing up the ramp on Gear 1 was easy but then later I saw some construction workers overtaking me with utmost ease with their old non-geared classic bikes - hmmm!!! Obviously, having paid quite a bit for 21 gears I was disappointed, got down and checked the air the convential style - by pressing the tyre with the thumb. That must be it. So, went back home, got myself a new footpump and filled in air.
Day 2: Much more easier I thought till I saw some construction workers in the evening who overtook me with ease! Went back home and tried rotating the front wheels. The disk brakes were holding them a little bit and the wheels wouldn't rotate with ease! Took an hour to finally align the disk brakes and get the wheels moving freely. Tried the back wheel and the brake pads where literally stuck to the wheels! One would have thought the guy @ the store would check all these things before delivering the bike. He takes 30 mins to check everything before delivering the bike!
Day 3: Definitely much easier this time. It was a breeze getting to the office and back. Hope to keep it going for sometime now.
Update: Its almost 6 months now and I have 2 bicycles - a Mongoose (MTB) and a RoadBike and good bikes make a difference. I have covered almost 1800kms including lot of century rides! It takes just 15 mins to reach office. That's almost 50% of what I took on day1 when I started cycling. I will probably blog on the long cycling trips separately and planning for TFN!
First thing was to get a bicycle so did a lot of googling and finally decided to visit the bicycle store and decide. Me being me it was quite likely that I would use the bicycle for a few days and then leave it to rust so decided to take it easy and bought a entry level 21 gear bicycle (Hero Octane). The reviews for this were not great but even then after sitting on it I thought it was comfortable. Bought the bicycle and it was pouring but decided to ride it back from commercial street. With the enthusiasm of a new bicycle managed to get him with a little bit of sweat. I did not stop pedalling which was quite funny as you will realise later in the post
Day 1: Left home nice and early and it seemed like hard work to get to office. I was sweating even though I wanted to take it easy. On the way back home climbing up the ramp on Gear 1 was easy but then later I saw some construction workers overtaking me with utmost ease with their old non-geared classic bikes - hmmm!!! Obviously, having paid quite a bit for 21 gears I was disappointed, got down and checked the air the convential style - by pressing the tyre with the thumb. That must be it. So, went back home, got myself a new footpump and filled in air.
Day 2: Much more easier I thought till I saw some construction workers in the evening who overtook me with ease! Went back home and tried rotating the front wheels. The disk brakes were holding them a little bit and the wheels wouldn't rotate with ease! Took an hour to finally align the disk brakes and get the wheels moving freely. Tried the back wheel and the brake pads where literally stuck to the wheels! One would have thought the guy @ the store would check all these things before delivering the bike. He takes 30 mins to check everything before delivering the bike!
Day 3: Definitely much easier this time. It was a breeze getting to the office and back. Hope to keep it going for sometime now.
Update: Its almost 6 months now and I have 2 bicycles - a Mongoose (MTB) and a RoadBike and good bikes make a difference. I have covered almost 1800kms including lot of century rides! It takes just 15 mins to reach office. That's almost 50% of what I took on day1 when I started cycling. I will probably blog on the long cycling trips separately and planning for TFN!
Subscribe to:
Posts (Atom)